fix: correct databank architecture to match specification\n\n- Restructure databank/artifacts/ with only human/ and llm/ top-level directories\n- Remove all incorrectly placed domain directories from databank/artifacts/\n- Create proper LLMDatabankTOC.json for chat agent '@' function\n- Implement correct human/llm dual-format structure as specified\n- Remove scaffolding from databank as requested\n- Create proper PMO scaffolding in pmo/artifacts/scaffolding/ with domain templates\n- Update README documentation to reflect corrected architecture\n- Maintain clear separation: humans edit collab/, AI manages artifacts/\n- Ensure LLMDatabankTOC enables efficient navigation for chat agents\n- Correct repository structure diagram to show proper databank/artifacts/ structure\n- Remove all references to incorrectly placed directories\n- Maintain only collab/ as editable directory for humans

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
2025-10-24 12:47:44 -05:00
parent a811335196
commit e3cb3f471e
40 changed files with 369 additions and 1686 deletions

View File

@@ -2,23 +2,63 @@
This directory contains templates for quickly standing up new PMO components.
## Purpose
The scaffolding directory provides templates for quickly creating new PMO components when needed. Each template represents a complete, functional PMO domain that can be quickly customized for specific needs.
## Structure
```
scaffolding/
├── domain-template/ # Template for new PMO domains
│ ├── README.md # Domain overview and purpose
│ ├── dashboard/ # Dashboard components and views
│ ├── projects/ # Project management components
│ ├── reports/ # Reporting components
│ ├── resources/ # Resource management components
│ ├── config/ # Configuration components
── docs/ # Documentation components
│ ├── resources/ # Resource management components
│ ├── config/ # Configuration components
── docs/ # Documentation components
│ └── README.md # Domain overview and purpose
└── README.md # This file
```
## Purpose
## Usage
The scaffolding directory provides templates for quickly creating new PMO components when needed.
To create a new PMO domain:
1. **Copy Template**: `cp -r domain-template/ ../NEW-DOMAIN-NAME/`
2. **Customize README**: Update `README.md` with domain-specific information
3. **Populate Components**: Customize dashboard, projects, reports, resources, config, and docs
4. **Configure**: Set up domain-specific configuration in `config/`
5. **Document**: Create domain-specific documentation in `docs/`
## Templates
Each template provides a starting point for new domains with:
- **Standard directory structure** following PMO conventions
- **Placeholder content** for customization
- **Consistent formatting** and organization
- **Cross-component linking** patterns
- **Domain-specific documentation** templates
## Components
### Dashboard
Templates for creating domain-specific dashboards with standard PMO metrics and KPIs.
### Projects
Project management templates with standard tracking fields and workflow integration.
### Reports
Reporting templates with standard formats and content structures.
### Resources
Resource management templates with standard allocation and tracking mechanisms.
### Config
Configuration templates with standard settings and customization options.
### Docs
Documentation templates with standard formats and content guidelines.
---