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:
@@ -1,22 +0,0 @@
|
||||
# PMO Artifacts Directory
|
||||
|
||||
This directory contains all PMO (Project Management Office) components and data.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
artifacts/
|
||||
├── dashboard/ # PMO dashboard views and reports
|
||||
├── projects/ # Project registry and tracking links
|
||||
├── reports/ # Status reports and analytics
|
||||
├── resources/ # Resource allocation and management
|
||||
├── config/ # PMO configuration and settings
|
||||
├── docs/ # Detailed PMO documentation
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The artifacts directory serves as the central hub for all PMO functionality, providing project management capabilities and tracking.
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Config Directory
|
||||
|
||||
This directory contains PMO configuration and settings.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
config/
|
||||
├── README.md # This file
|
||||
└── (future files) # PMO configuration and settings
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The config directory manages all PMO-specific configurations and settings for consistent operation.
|
||||
|
||||
---
|
||||
@@ -1,33 +0,0 @@
|
||||
# COO (Chief Operating Officer) PMO
|
||||
|
||||
This directory contains all PMO components for the Chief Operating Officer domain.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
coo/
|
||||
├── README.md # This file
|
||||
├── dashboard/ # COO dashboard components and views
|
||||
├── projects/ # COO project management components
|
||||
├── reports/ # COO reporting components
|
||||
├── resources/ # COO resource management components
|
||||
├── config/ # COO configuration components
|
||||
└── docs/ # COO documentation components
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The COO directory serves as the PMO root for all operations-related project management activities.
|
||||
|
||||
## Components
|
||||
|
||||
Each subdirectory contains components specific to the COO domain:
|
||||
|
||||
- **dashboard/** - Dashboards and views for operational metrics
|
||||
- **projects/** - Project tracking and management for operational initiatives
|
||||
- **reports/** - Status reports and analytics for operations
|
||||
- **resources/** - Resource allocation and management for operational teams
|
||||
- **config/** - Configuration settings for COO PMO components
|
||||
- **docs/** - Documentation specific to operations management
|
||||
|
||||
---
|
||||
@@ -1,37 +0,0 @@
|
||||
# CTO (Chief Technology and Product Officer) PMO
|
||||
|
||||
This directory contains all PMO components for the Chief Technology and Product Officer domain.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
cto/
|
||||
├── README.md # This file
|
||||
├── dashboard/ # CTO dashboard components and views
|
||||
├── projects/ # CTO project management components
|
||||
├── reports/ # CTO reporting components
|
||||
├── resources/ # CTO resource management components
|
||||
├── config/ # CTO configuration components
|
||||
├── docs/ # CTO documentation components
|
||||
├── vpengineering/ # VP Engineering project management
|
||||
└── vpproduct/ # VP Product project management
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The CTO directory serves as the PMO root for all technology and product-related project management activities.
|
||||
|
||||
## Components
|
||||
|
||||
Each subdirectory contains components specific to the CTO domain:
|
||||
|
||||
- **dashboard/** - Dashboards and views for technology and product metrics
|
||||
- **projects/** - Project tracking and management for tech/product initiatives
|
||||
- **reports/** - Status reports and analytics for technology and product
|
||||
- **resources/** - Resource allocation and management for tech/product teams
|
||||
- **config/** - Configuration settings for CTO PMO components
|
||||
- **docs/** - Documentation specific to technology and product management
|
||||
- **vpengineering/** - VP Engineering-specific project management
|
||||
- **vpproduct/** - VP Product-specific project management
|
||||
|
||||
---
|
||||
@@ -1,33 +0,0 @@
|
||||
# VP Engineering PMO
|
||||
|
||||
This directory contains project management components specific to the VP Engineering role.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
vpengineering/
|
||||
├── README.md # This file
|
||||
├── dashboard/ # VP Engineering dashboard components
|
||||
├── projects/ # VP Engineering project tracking
|
||||
├── reports/ # VP Engineering status reports
|
||||
├── resources/ # VP Engineering resource management
|
||||
├── config/ # VP Engineering configuration
|
||||
└── docs/ # VP Engineering documentation
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The VP Engineering directory provides project management capabilities specific to engineering operations including software development, security, architecture, DevOps, and testing.
|
||||
|
||||
## Components
|
||||
|
||||
Each subdirectory contains components specific to VP Engineering:
|
||||
|
||||
- **dashboard/** - Engineering metrics and KPIs
|
||||
- **projects/** - Software development project tracking
|
||||
- **reports/** - Engineering status and progress reports
|
||||
- **resources/** - Engineering team and tool resource management
|
||||
- **config/** - Engineering-specific configuration settings
|
||||
- **docs/** - Engineering documentation and guidelines
|
||||
|
||||
---
|
||||
@@ -1,33 +0,0 @@
|
||||
# VP Product PMO
|
||||
|
||||
This directory contains project management components specific to the VP Product role.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
vpproduct/
|
||||
├── README.md # This file
|
||||
├── dashboard/ # VP Product dashboard components
|
||||
├── projects/ # VP Product project tracking
|
||||
├── reports/ # VP Product status reports
|
||||
├── resources/ # VP Product resource management
|
||||
├── config/ # VP Product configuration
|
||||
└── docs/ # VP Product documentation
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The VP Product directory provides project management capabilities specific to product management operations including product strategy, market analysis, customer requirements, and product development coordination.
|
||||
|
||||
## Components
|
||||
|
||||
Each subdirectory contains components specific to VP Product:
|
||||
|
||||
- **dashboard/** - Product metrics and KPIs
|
||||
- **projects/** - Product development project tracking
|
||||
- **reports/** - Product status and progress reports
|
||||
- **resources/** - Product team and market research resource management
|
||||
- **config/** - Product-specific configuration settings
|
||||
- **docs/** - Product documentation and guidelines
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Dashboard Directory
|
||||
|
||||
This directory contains PMO dashboard views and reports.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
dashboard/
|
||||
├── README.md # This file
|
||||
└── (future files) # Dashboard components and reports
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The dashboard directory provides visual representations and reports for project status and key metrics.
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Docs Directory
|
||||
|
||||
This directory contains detailed PMO documentation.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
docs/
|
||||
├── README.md # This file
|
||||
└── (future files) # Detailed PMO documentation
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The docs directory provides comprehensive documentation for all PMO processes, procedures, and guidelines.
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Projects Directory
|
||||
|
||||
This directory contains project registry and tracking links.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
projects/
|
||||
├── README.md # This file
|
||||
└── (future files) # Project registry and tracking information
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The projects directory serves as the central registry for all projects, providing tracking and linking capabilities.
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Reports Directory
|
||||
|
||||
This directory contains status reports and analytics.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
reports/
|
||||
├── README.md # This file
|
||||
└── (future files) # Status reports and analytics
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The reports directory provides comprehensive status reports and analytical insights for projects and resources.
|
||||
|
||||
---
|
||||
@@ -1,17 +0,0 @@
|
||||
# Resources Directory
|
||||
|
||||
This directory contains resource allocation and management information.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
resources/
|
||||
├── README.md # This file
|
||||
└── (future files) # Resource allocation and management
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The resources directory tracks and manages all project resources, including personnel, equipment, and budget allocations.
|
||||
|
||||
---
|
||||
@@ -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.
|
||||
|
||||
---
|
||||
@@ -1,4 +1,4 @@
|
||||
# PMO Domain Template
|
||||
# Domain Template
|
||||
|
||||
This is a template for creating new PMO domains.
|
||||
|
||||
@@ -6,26 +6,34 @@ This is a template for creating new PMO domains.
|
||||
|
||||
This template provides the standard structure for all PMO domains.
|
||||
|
||||
## Structure
|
||||
## Components
|
||||
|
||||
```
|
||||
domain-template/
|
||||
├── 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
|
||||
```
|
||||
### Dashboard
|
||||
Dashboard components and views for this domain.
|
||||
|
||||
### Projects
|
||||
Project management components for this domain.
|
||||
|
||||
### Reports
|
||||
Reporting components for this domain.
|
||||
|
||||
### Resources
|
||||
Resource management components for this domain.
|
||||
|
||||
### Config
|
||||
Configuration components for this domain.
|
||||
|
||||
### Docs
|
||||
Documentation components for this domain.
|
||||
|
||||
## Customization
|
||||
|
||||
To customize this template for a specific PMO domain:
|
||||
To customize this template for a specific domain:
|
||||
|
||||
1. Rename the directory to the domain name
|
||||
2. Update README.md with domain-specific information
|
||||
3. Customize dashboard, projects, reports, resources, config, and docs
|
||||
4. Add domain-specific components as needed
|
||||
1. **Rename Directory**: Change directory name to domain name
|
||||
2. **Update README**: Customize this file with domain-specific information
|
||||
3. **Customize Components**: Modify dashboard, projects, reports, resources, config, and docs
|
||||
4. **Configure**: Set up domain-specific configuration
|
||||
5. **Document**: Create domain-specific documentation
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user