fix: correct databank architecture and implement proper CTO/COO structure\n\n- Remove incorrectly placed human/llm directories from databank root\n- Restructure databank with everything under databank/artifacts/ as requested\n- Implement proper CTO/COO structure under pmo/artifacts/ with complete PMO components\n- Create comprehensive collab/ directory structure for human/AI communication\n- Remove Joplin processing scripts and references as requested\n- Create proper scaffolding directories for quick domain standup\n- Update README documentation to reflect corrected architecture\n- Ensure only collab/ directories are editable by humans\n- AI agents manage databank/artifacts/ based on collab/ communications\n- Create structured intake templates and collaboration workflows\n- Maintain clear separation between readonly databank and read-write PMO\n- Implement proper single source of truth with AI-managed artifacts
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
@@ -1,17 +1,33 @@
|
||||
# COO Directory
|
||||
# COO (Chief Operating Officer) PMO
|
||||
|
||||
This directory contains COO-specific project management information.
|
||||
This directory contains all PMO components for the Chief Operating Officer domain.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
coo/
|
||||
├── README.md # This file
|
||||
└── (future files) # COO-specific project management
|
||||
├── 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 provides project management capabilities specific to the Chief Operating Officer domain.
|
||||
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,18 +1,37 @@
|
||||
# CTO Directory
|
||||
# CTO (Chief Technology and Product Officer) PMO
|
||||
|
||||
This directory contains CTO-specific project management information.
|
||||
This directory contains all PMO components for the Chief Technology and Product Officer domain.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
cto/
|
||||
├── README.md # This file
|
||||
├── vpengineering/ # VP Engineering project management
|
||||
└── vpproduct/ # VP Product project management
|
||||
├── 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 provides project management capabilities specific to the Chief Technology and Product Officer domain.
|
||||
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,17 +1,33 @@
|
||||
# VP Engineering Directory
|
||||
# VP Engineering PMO
|
||||
|
||||
This directory contains VP Engineering project management information.
|
||||
This directory contains project management components specific to the VP Engineering role.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
vpengineering/
|
||||
├── README.md # This file
|
||||
└── (future files) # VP Engineering project management
|
||||
├── 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 the engineering aspects of the CTO role.
|
||||
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,17 +1,33 @@
|
||||
# VP Product Directory
|
||||
# VP Product PMO
|
||||
|
||||
This directory contains VP Product project management information.
|
||||
This directory contains project management components specific to the VP Product role.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
vpproduct/
|
||||
├── README.md # This file
|
||||
└── (future files) # VP Product project management
|
||||
├── 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 the product aspects of the CTO role.
|
||||
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
|
||||
|
||||
---
|
||||
24
pmo/artifacts/scaffolding/README.md
Normal file
24
pmo/artifacts/scaffolding/README.md
Normal file
@@ -0,0 +1,24 @@
|
||||
# PMO Scaffolding Templates
|
||||
|
||||
This directory contains templates for quickly standing up new PMO components.
|
||||
|
||||
## 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
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The scaffolding directory provides templates for quickly creating new PMO components when needed.
|
||||
|
||||
---
|
||||
31
pmo/artifacts/scaffolding/domain-template/README.md
Normal file
31
pmo/artifacts/scaffolding/domain-template/README.md
Normal file
@@ -0,0 +1,31 @@
|
||||
# PMO Domain Template
|
||||
|
||||
This is a template for creating new PMO domains.
|
||||
|
||||
## Purpose
|
||||
|
||||
This template provides the standard structure for all PMO domains.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
## Customization
|
||||
|
||||
To customize this template for a specific PMO 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
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user