docs: update references and plugin configurations

- Update manifest-schema.md with latest schema changes
- Refine CLAUDE.md documentation
- Update MCP-WIKIJS, PLUGIN-PMO, PLUGIN-PROJMAN references
- Fix wikijs_client.py configuration
- Update plugin configs for cmdb-assistant and projman
- Add root .mcp.json for project-level MCP configuration

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2025-12-12 01:25:49 -05:00
parent b53aa7cb23
commit b067802da8
15 changed files with 260 additions and 230 deletions

View File

@@ -25,12 +25,12 @@ The MCP server operates in two modes based on environment variables:
**Project Mode (projman):**
- When `WIKIJS_PROJECT` is present
- Operates within project path: `/hyper-hive-labs/projects/cuisineflow`
- Operates within project path: `/your-org/projects/my-project`
- Used by projman plugin
**Company Mode (pmo):**
- When `WIKIJS_PROJECT` is absent
- Operates on entire namespace: `/hyper-hive-labs`
- Operates on entire namespace: `/your-org`
- Used by projman-pmo plugin
```python
@@ -38,8 +38,8 @@ The MCP server operates in two modes based on environment variables:
def load(self):
# ... load configs ...
self.base_path = os.getenv('WIKIJS_BASE_PATH') # /hyper-hive-labs
self.project_path = os.getenv('WIKIJS_PROJECT') # projects/cuisineflow (optional)
self.base_path = os.getenv('WIKIJS_BASE_PATH') # /your-org
self.project_path = os.getenv('WIKIJS_PROJECT') # projects/my-project (optional)
# Compose full path
if self.project_path:
@@ -66,10 +66,10 @@ def load(self):
### Company-Wide Organization
```
Wiki.js: https://wiki.hyperhivelabs.com
└── /hyper-hive-labs/ # Base path
Wiki.js: https://wiki.your-company.com
└── /your-org/ # Base path
├── projects/ # Project-specific documentation
│ ├── cuisineflow/
│ ├── my-project/
│ │ ├── lessons-learned/
│ │ │ ├── sprints/
│ │ │ │ ├── sprint-01-auth.md
@@ -83,13 +83,13 @@ Wiki.js: https://wiki.hyperhivelabs.com
│ │ ├── architecture/
│ │ ├── api/
│ │ └── deployment/
│ ├── cuisineflow-site/
│ ├── my-project-site/
│ │ ├── lessons-learned/
│ │ └── documentation/
│ ├── intuit-engine/
│ │ ├── lessons-learned/
│ │ └── documentation/
│ └── hhl-site/
│ └── company-site/
│ ├── lessons-learned/
│ └── documentation/
├── company/ # Company-wide documentation
@@ -124,11 +124,11 @@ Wiki.js: https://wiki.hyperhivelabs.com
**Project Mode (projman):**
- Full path = `{WIKIJS_BASE_PATH}/{WIKIJS_PROJECT}`
- Example: `/hyper-hive-labs/projects/cuisineflow`
- Example: `/your-org/projects/my-project`
**Company Mode (pmo):**
- Full path = `{WIKIJS_BASE_PATH}`
- Example: `/hyper-hive-labs`
- Example: `/your-org`
---
@@ -139,14 +139,14 @@ Wiki.js: https://wiki.hyperhivelabs.com
**File:** `~/.config/claude/wikijs.env`
```bash
WIKIJS_API_URL=https://wiki.hyperhivelabs.com/graphql
WIKIJS_API_URL=https://wiki.your-company.com/graphql
WIKIJS_API_TOKEN=your_wikijs_token
WIKIJS_BASE_PATH=/hyper-hive-labs
WIKIJS_BASE_PATH=/your-org
```
**Generating Wiki.js API Token:**
1. Log into Wiki.js: https://wiki.hyperhivelabs.com
1. Log into Wiki.js: https://wiki.your-company.com
2. Navigate to: **User Menu (top-right)****Administration**
3. In the sidebar, go to: **API Access**
4. Click **Create New Token**
@@ -170,9 +170,9 @@ mkdir -p ~/.config/claude
# Create wikijs.env
cat > ~/.config/claude/wikijs.env << EOF
WIKIJS_API_URL=https://wiki.hyperhivelabs.com/graphql
WIKIJS_API_URL=https://wiki.your-company.com/graphql
WIKIJS_API_TOKEN=your_token_here
WIKIJS_BASE_PATH=/hyper-hive-labs
WIKIJS_BASE_PATH=/your-org
EOF
# Secure the file (important!)
@@ -188,13 +188,13 @@ cat ~/.config/claude/wikijs.env
```bash
# Wiki.js project path (relative to base path)
WIKIJS_PROJECT=projects/cuisineflow
WIKIJS_PROJECT=projects/my-project
```
**Setup:**
```bash
# In each project root
echo "WIKIJS_PROJECT=projects/cuisineflow" >> .env
echo "WIKIJS_PROJECT=projects/my-project" >> .env
# Add to .gitignore (if not already)
echo ".env" >> .gitignore
@@ -243,8 +243,8 @@ class WikiJSConfig:
# Extract values
self.api_url = os.getenv('WIKIJS_API_URL')
self.api_token = os.getenv('WIKIJS_API_TOKEN')
self.base_path = os.getenv('WIKIJS_BASE_PATH') # /hyper-hive-labs
self.project_path = os.getenv('WIKIJS_PROJECT') # projects/cuisineflow (optional)
self.base_path = os.getenv('WIKIJS_BASE_PATH') # /your-org
self.project_path = os.getenv('WIKIJS_PROJECT') # projects/my-project (optional)
# Compose full path
if self.project_path:
@@ -691,7 +691,7 @@ class WikiJSClient:
by_project = {}
for result in results:
# Extract project name from path
# e.g., "/hyper-hive-labs/projects/cuisineflow/..." -> "cuisineflow"
# e.g., "/your-org/projects/my-project/..." -> "my-project"
path_parts = result['path'].split('/')
if len(path_parts) >= 4:
project = path_parts[3]
@@ -957,7 +957,7 @@ Agent: Any architectural insights for similar future work?
User: [Response]
Agent: I'll create a lesson in Wiki.js:
Path: /hyper-hive-labs/projects/cuisineflow/lessons-learned/sprints/sprint-16-intuit-engine
Path: /your-org/projects/my-project/lessons-learned/sprints/sprint-16-intuit-engine
Tags detected:
#service-extraction #api #refactoring #claude-code-loops
@@ -965,7 +965,7 @@ Agent: I'll create a lesson in Wiki.js:
Creating page in Wiki.js... ✅
Updating INDEX.md... ✅
View at: https://wiki.hyperhivelabs.com/hyper-hive-labs/projects/cuisineflow/lessons-learned/sprints/sprint-16-intuit-engine
View at: https://wiki.your-company.com/your-org/projects/my-project/lessons-learned/sprints/sprint-16-intuit-engine
```
---
@@ -1011,14 +1011,14 @@ def test_project_config_path_composition(tmp_path, monkeypatch):
system_config.write_text(
"WIKIJS_API_URL=https://wiki.test.com/graphql\n"
"WIKIJS_API_TOKEN=test_token\n"
"WIKIJS_BASE_PATH=/hyper-hive-labs\n"
"WIKIJS_BASE_PATH=/your-org\n"
)
project_dir = tmp_path / 'project'
project_dir.mkdir()
project_config = project_dir / '.env'
project_config.write_text("WIKIJS_PROJECT=projects/cuisineflow\n")
project_config.write_text("WIKIJS_PROJECT=projects/my-project\n")
monkeypatch.setenv('HOME', str(tmp_path))
monkeypatch.chdir(project_dir)
@@ -1026,8 +1026,8 @@ def test_project_config_path_composition(tmp_path, monkeypatch):
config = WikiJSConfig()
result = config.load()
assert result['project_path'] == 'projects/cuisineflow'
assert result['full_path'] == '/hyper-hive-labs/projects/cuisineflow'
assert result['project_path'] == 'projects/my-project'
assert result['full_path'] == '/your-org/projects/my-project'
assert result['mode'] == 'project'
```
@@ -1116,7 +1116,7 @@ pytest tests/test_config.py::test_project_config_path_composition
### Initial Structure Creation
**Status:** Base structure `/hyper-hive-labs` **does not exist** and needs to be created during Phase 1.1b.
**Status:** Base structure `/your-org` **does not exist** and needs to be created during Phase 1.1b.
**Setup Script:** Run this script during Phase 1.1b to create the base structure:
@@ -1134,7 +1134,7 @@ from mcp_server.wikijs_client import WikiJSClient
async def initialize_wiki_structure():
"""Create base Wiki.js structure for Bandit Labs"""
"""Create base Wiki.js structure for Your Organization"""
print("Initializing Wiki.js base structure...")
print("=" * 60)
@@ -1153,17 +1153,17 @@ async def initialize_wiki_structure():
# Base structure to create
base_pages = [
{
'path': 'hyper-hive-labs',
'title': 'Bandit Labs',
'content': '''# Bandit Labs Documentation
'path': 'your-org',
'title': 'Your Organization',
'content': '''# Your Organization Documentation
Welcome to the Bandit Labs knowledge base.
Welcome to the Your Organization knowledge base.
## Organization
- **[Projects](hyper-hive-labs/projects)** - Project-specific documentation and lessons learned
- **[Company](hyper-hive-labs/company)** - Company-wide processes, standards, and tools
- **[Shared](hyper-hive-labs/shared)** - Cross-project architecture patterns and best practices
- **[Projects](your-org/projects)** - Project-specific documentation and lessons learned
- **[Company](your-org/company)** - Company-wide processes, standards, and tools
- **[Shared](your-org/shared)** - Cross-project architecture patterns and best practices
## Purpose
@@ -1176,10 +1176,10 @@ This knowledge base captures:
All content is searchable and tagged for easy discovery across projects.
''',
'tags': ['company', 'index'],
'description': 'Bandit Labs company knowledge base'
'description': 'Your Organization company knowledge base'
},
{
'path': 'hyper-hive-labs/projects',
'path': 'your-org/projects',
'title': 'Projects',
'content': '''# Project Documentation
@@ -1187,10 +1187,10 @@ Project-specific documentation and lessons learned.
## Active Projects
- **[CuisineFlow](hyper-hive-labs/projects/cuisineflow)** - Main product
- **[CuisineFlow-Site](hyper-hive-labs/projects/cuisineflow-site)** - Demo and customer gateway
- **[Intuit-Engine](hyper-hive-labs/projects/intuit-engine)** - API aggregator service
- **[HHL-Site](hyper-hive-labs/projects/hhl-site)** - Company website
- **[My-Project](your-org/projects/my-project)** - Main product
- **[My-Project-Site](your-org/projects/my-project-site)** - Demo and customer gateway
- **[Intuit-Engine](your-org/projects/intuit-engine)** - API aggregator service
- **[Company-Site](your-org/projects/company-site)** - Company website
Each project maintains:
- Lessons learned from sprints
@@ -1201,7 +1201,7 @@ Each project maintains:
'description': 'Index of all project documentation'
},
{
'path': 'hyper-hive-labs/company',
'path': 'your-org/company',
'title': 'Company',
'content': '''# Company Documentation
@@ -1209,9 +1209,9 @@ Company-wide processes, standards, and tools.
## Sections
- **[Processes](hyper-hive-labs/company/processes)** - Development workflows, onboarding, deployment
- **[Standards](hyper-hive-labs/company/standards)** - Code style, API design, security practices
- **[Tools](hyper-hive-labs/company/tools)** - Gitea, Wiki.js, Claude Code plugin guides
- **[Processes](your-org/company/processes)** - Development workflows, onboarding, deployment
- **[Standards](your-org/company/standards)** - Code style, API design, security practices
- **[Tools](your-org/company/tools)** - Gitea, Wiki.js, Claude Code plugin guides
These standards apply to all projects and team members.
''',
@@ -1219,7 +1219,7 @@ These standards apply to all projects and team members.
'description': 'Company processes and standards'
},
{
'path': 'hyper-hive-labs/shared',
'path': 'your-org/shared',
'title': 'Shared Resources',
'content': '''# Shared Resources
@@ -1227,9 +1227,9 @@ Cross-project architecture patterns, best practices, and technical knowledge.
## Sections
- **[Architecture Patterns](hyper-hive-labs/shared/architecture-patterns)** - Microservices, service extraction, API design
- **[Best Practices](hyper-hive-labs/shared/best-practices)** - Error handling, logging, testing strategies
- **[Tech Stack](hyper-hive-labs/shared/tech-stack)** - Python ecosystem, Docker, CI/CD pipelines
- **[Architecture Patterns](your-org/shared/architecture-patterns)** - Microservices, service extraction, API design
- **[Best Practices](your-org/shared/best-practices)** - Error handling, logging, testing strategies
- **[Tech Stack](your-org/shared/tech-stack)** - Python ecosystem, Docker, CI/CD pipelines
These patterns are distilled from lessons learned across all projects.
''',
@@ -1238,40 +1238,40 @@ These patterns are distilled from lessons learned across all projects.
},
# Project placeholders
{
'path': 'hyper-hive-labs/projects/cuisineflow',
'title': 'CuisineFlow',
'content': '''# CuisineFlow
'path': 'your-org/projects/my-project',
'title': 'My-Project',
'content': '''# My-Project
Main product - recipe management and meal planning platform.
## Documentation
- **[Lessons Learned](hyper-hive-labs/projects/cuisineflow/lessons-learned)** - Sprint retrospectives and insights
- **[Architecture](hyper-hive-labs/projects/cuisineflow/documentation/architecture)** - System architecture
- **[API](hyper-hive-labs/projects/cuisineflow/documentation/api)** - API documentation
- **[Lessons Learned](your-org/projects/my-project/lessons-learned)** - Sprint retrospectives and insights
- **[Architecture](your-org/projects/my-project/documentation/architecture)** - System architecture
- **[API](your-org/projects/my-project/documentation/api)** - API documentation
Sprint lessons will be automatically captured here by the projman plugin.
''',
'tags': ['project', 'cuisineflow'],
'description': 'CuisineFlow project documentation'
'tags': ['project', 'my-project'],
'description': 'My-Project project documentation'
},
{
'path': 'hyper-hive-labs/projects/cuisineflow/lessons-learned',
'title': 'CuisineFlow - Lessons Learned',
'content': '''# CuisineFlow - Lessons Learned
'path': 'your-org/projects/my-project/lessons-learned',
'title': 'My-Project - Lessons Learned',
'content': '''# My-Project - Lessons Learned
Sprint retrospectives and insights from CuisineFlow development.
Sprint retrospectives and insights from My-Project development.
## Organization
- **[Sprints](hyper-hive-labs/projects/cuisineflow/lessons-learned/sprints)** - Sprint-specific lessons
- **[Patterns](hyper-hive-labs/projects/cuisineflow/lessons-learned/patterns)** - Recurring patterns and solutions
- **[INDEX](hyper-hive-labs/projects/cuisineflow/lessons-learned/INDEX)** - Complete index with tags
- **[Sprints](your-org/projects/my-project/lessons-learned/sprints)** - Sprint-specific lessons
- **[Patterns](your-org/projects/my-project/lessons-learned/patterns)** - Recurring patterns and solutions
- **[INDEX](your-org/projects/my-project/lessons-learned/INDEX)** - Complete index with tags
Lessons are automatically captured during sprint close via `/sprint-close` command.
''',
'tags': ['lessons-learned', 'cuisineflow'],
'description': 'CuisineFlow lessons learned index'
'tags': ['lessons-learned', 'my-project'],
'description': 'My-Project lessons learned index'
}
]
@@ -1308,7 +1308,7 @@ Lessons are automatically captured during sprint close via `/sprint-close` comma
sys.exit(1)
else:
print(f"\n✅ All pages created successfully!")
print(f"\nView at: https://wiki.hyperhivelabs.com/hyper-hive-labs")
print(f"\nView at: https://wiki.your-company.com/your-org")
if __name__ == '__main__':
@@ -1326,13 +1326,13 @@ python setup_wiki_structure.py
```
Initializing Wiki.js base structure...
============================================================
✅ Connected to Wiki.js at https://wiki.hyperhivelabs.com/graphql
Base path: /hyper-hive-labs
✅ Connected to Wiki.js at https://wiki.your-company.com/graphql
Base path: /your-org
Creating: /hyper-hive-labs
Creating: /your-org
✅ Created successfully
Creating: /hyper-hive-labs/projects
Creating: /your-org/projects
✅ Created successfully
...
@@ -1343,12 +1343,12 @@ Setup complete!
✅ All pages created successfully!
View at: https://wiki.hyperhivelabs.com/hyper-hive-labs
View at: https://wiki.your-company.com/your-org
```
**Post-Setup:**
After running the script:
1. Visit https://wiki.hyperhivelabs.com/hyper-hive-labs to verify structure
1. Visit https://wiki.your-company.com/your-org to verify structure
2. Add additional project directories as needed
3. The structure is now ready for projman plugin to use
@@ -1451,13 +1451,13 @@ if __name__ == '__main__':
curl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"query":"{ pages { list { id title } } }"}' \
https://wiki.hyperhivelabs.com/graphql
https://wiki.your-company.com/graphql
```
**Issue:** Path not found
```bash
# Solution: Verify base structure exists
# Check in Wiki.js web interface that /hyper-hive-labs path exists
# Check in Wiki.js web interface that /your-org path exists
```
**Issue:** Tags not working

View File

@@ -197,7 +197,7 @@ projman-pmo/
**Critical Differences from projman:**
- **NO** `GITEA_REPO` → operates on all repositories
- **NO** `WIKIJS_PROJECT` → operates on entire `/hyper-hive-labs` namespace
- **NO** `WIKIJS_PROJECT` → operates on entire `/your-org` namespace
- Same shared MCP servers at `../mcp-servers/`
### Environment Variables
@@ -282,10 +282,10 @@ User: /pmo-status
PMO: Projects Overview:
CuisineFlow: Sprint in progress, 60% complete
└─ Blocking: CuisineFlow-Site deployment
Main-App: Sprint in progress, 60% complete
└─ Blocking: Main-App-Site deployment
I notice CuisineFlow-Site is waiting on API changes.
I notice Main-App-Site is waiting on API changes.
Use projman in the cuisineflow-site repo to plan the sync work.
```
@@ -309,7 +309,7 @@ User: /pmo-status
PMO: Projects Overview
================
CuisineFlow (main product)
Main-App (main product)
├── Sprint: Intuit Engine Extraction
├── Status: In Progress (60%)
├── Issue: #47
@@ -317,13 +317,13 @@ PMO: Projects Overview
├── Next: API testing
└── Timeline: On track (1 week remaining)
CuisineFlow-Site (demo)
Main-App-Site (demo)
├── Sprint: Dashboard Updates
├── Status: Waiting on dependencies
├── Issue: #12
├── Blockers: Depends on CuisineFlow #47 (API changes)
├── Blockers: Depends on Main-App #47 (API changes)
├── Next: Deploy when API ready
└── Timeline: Blocked (waiting on CuisineFlow)
└── Timeline: Blocked (waiting on Main-App)
Intuit-Engine (service)
├── Sprint: Initial Setup
@@ -333,7 +333,7 @@ PMO: Projects Overview
├── Next: Service boundary definition
└── Timeline: Not started
HHL-Site (marketing)
Company-Site (marketing)
├── Sprint: Content Updates
├── Status: Complete
├── Issue: #8 (closed)
@@ -342,14 +342,14 @@ PMO: Projects Overview
└── Timeline: Ready for deployment
Cross-Project Insights:
- CuisineFlow-Site blocked by CuisineFlow #47
- Main-App-Site blocked by Main-App #47
- Intuit-Engine needs architectural guidance
- HHL-Site ready for deployment
- Company-Site ready for deployment
Suggested Actions:
1. Prioritize CuisineFlow #47 completion (unblocks Site)
1. Prioritize Main-App #47 completion (unblocks Site)
2. Schedule architecture review for Intuit-Engine
3. Deploy HHL-Site content updates
3. Deploy Company-Site content updates
```
**Success Criteria:**
@@ -375,15 +375,15 @@ PMO: Priority Analysis Across Projects
=================================
Critical (Blocks launches):
1. CuisineFlow #47 - Intuit Engine Extraction
→ Blocks: CuisineFlow v2.0 launch (Nov 15)
→ Blocks: CuisineFlow-Site deployment
1. Main-App #47 - Intuit Engine Extraction
→ Blocks: Main-App v2.0 launch (Nov 15)
→ Blocks: Main-App-Site deployment
→ Status: 60% complete, 1 week remaining
→ Recommendation: Maintain focus
High (Important features):
2. CuisineFlow-Site #12 - Dashboard Updates
→ Depends on: CuisineFlow #47
2. Main-App-Site #12 - Dashboard Updates
→ Depends on: Main-App #47
→ Status: Waiting
→ Recommendation: Begin planning, wait for #47
@@ -393,14 +393,14 @@ PMO: Priority Analysis Across Projects
→ Recommendation: Schedule architecture review
Medium (Enhancements):
4. HHL-Site #8 - Content Updates
4. Company-Site #8 - Content Updates
→ Status: Complete, ready to deploy
→ Recommendation: Deploy this week
Resource Analysis:
Leo (primary developer):
- Working on: CuisineFlow #47 (Critical)
- Next: CuisineFlow-Site #12 (High)
- Working on: Main-App #47 (Critical)
- Next: Main-App-Site #12 (High)
- Later: Intuit-Engine #3 (High)
⚠️ Potential Conflict:
@@ -438,27 +438,27 @@ PMO: Project Dependencies
Intuit-Engine (service)
↓ (must complete before)
CuisineFlow (main)
Main-App (main)
↓ (API changes required by)
CuisineFlow-Site (demo)
Main-App-Site (demo)
↓ (deploy together)
Customer VPS (deployments)
Detailed Dependencies:
1. CuisineFlow → Intuit-Engine
1. Main-App → Intuit-Engine
Type: Service extraction
Status: In progress
Blocker: Must complete #47 before v2.0 launch
Impact: High (blocks launch)
2. CuisineFlow → CuisineFlow-Site
2. Main-App → Main-App-Site
Type: Feature sync
Status: Waiting
Blocker: Dashboard updates need API changes from #47
Impact: Medium (demo consistency)
3. CuisineFlow → Customer VPS
3. Main-App → Customer VPS
Type: Deployment
Status: Pending
Blocker: v2.0 launch must complete before customer updates
@@ -466,16 +466,16 @@ PMO: Project Dependencies
Deployment Order:
1. Complete Intuit-Engine service extraction
2. Deploy CuisineFlow v2.0 to production
3. Sync CuisineFlow-Site demo
2. Deploy Main-App v2.0 to production
3. Sync Main-App-Site demo
4. Update customer VPS instances
Critical Path:
Intuit-Engine (#3) → CuisineFlow (#47) → Site (#12) → Customer VPS
Intuit-Engine (#3) → Main-App (#47) → Site (#12) → Customer VPS
Estimated timeline: 3 weeks total
Risks:
- CuisineFlow #47 delay would cascade to all downstream
- Main-App #47 delay would cascade to all downstream
- Customer VPS updates have Nov 20 deadline
```
@@ -505,9 +505,9 @@ PMO: Resource Conflict Analysis
Leo (Developer):
Assigned to:
- CuisineFlow #47: Intuit Engine extraction (Priority: Critical)
- CuisineFlow-Site #12: Dashboard redesign (Priority: High)
- HHL-Site #8: Content update (Priority: Medium)
- Main-App #47: Intuit Engine extraction (Priority: Critical)
- Main-App-Site #12: Dashboard redesign (Priority: High)
- Company-Site #8: Content update (Priority: Medium)
- Intuit-Engine #3: Service setup (Priority: High)
Conflict Analysis:
@@ -517,15 +517,15 @@ PMO: Resource Conflict Analysis
- Timeline: 2 weeks available
Recommendations:
1. FOCUS: CuisineFlow #47 (Critical, blocks launch)
1. FOCUS: Main-App #47 (Critical, blocks launch)
→ Keep as primary focus
→ Estimated completion: 1 week
2. QUEUE: CuisineFlow-Site #12 (High, depends on #47)
2. QUEUE: Main-App-Site #12 (High, depends on #47)
→ Start after #47 completes
→ Natural sequencing
3. DELEGATE: HHL-Site #8 (Medium, content work)
3. DELEGATE: Company-Site #8 (Medium, content work)
→ Can be handled by marketing team
→ Low technical complexity
@@ -536,14 +536,14 @@ PMO: Resource Conflict Analysis
Timeline Conflict:
Without changes:
Week 1-2: CuisineFlow #47
Week 1-2: Main-App #47
Week 3-4: Site #12 + Engine #3 (CONFLICT)
With recommendations:
Week 1-2: CuisineFlow #47 (FOCUS)
Week 3: CuisineFlow-Site #12 (QUEUE)
Week 1-2: Main-App #47 (FOCUS)
Week 3: Main-App-Site #12 (QUEUE)
Week 4: Intuit-Engine #3 (SCHEDULE)
HHL-Site #8: Marketing (DELEGATE)
Company-Site #8: Marketing (DELEGATE)
Apply recommendations?
```
@@ -571,18 +571,18 @@ PMO: Deployment Schedule
===================
Week of Nov 6:
- CuisineFlow: Continue Sprint #47 (Intuit Engine)
- HHL-Site: Deploy content updates (#8) ✅
- Main-App: Continue Sprint #47 (Intuit Engine)
- Company-Site: Deploy content updates (#8) ✅
Week of Nov 13:
- CuisineFlow: Complete Sprint #47 ⚠️
- Main-App: Complete Sprint #47 ⚠️
→ Critical: Must complete by Nov 15 for launch
- CuisineFlow-Site: Begin Dashboard updates (#12)
- Main-App-Site: Begin Dashboard updates (#12)
Week of Nov 20:
- CuisineFlow: Deploy v2.0 to production 🚀
- Main-App: Deploy v2.0 to production 🚀
→ Deployment window: Nov 20-22
- CuisineFlow-Site: Sync demo with v2.0
- Main-App-Site: Sync demo with v2.0
- Customer VPS: Begin rollout (Deadline: Nov 20)
Week of Nov 27:
@@ -590,19 +590,19 @@ PMO: Deployment Schedule
- Intuit-Engine: Begin service implementation (#3)
Critical Dates:
- Nov 15: CuisineFlow v2.0 feature freeze
- Nov 15: Main-App v2.0 feature freeze
- Nov 20: Production deployment
- Nov 20: Customer VPS deadline
- Nov 22: Demo site sync
Dependencies:
✅ Intuit-Engine service boundaries defined
🔄 CuisineFlow #47 in progress (60%)
CuisineFlow-Site #12 waiting
🔄 Main-App #47 in progress (60%)
Main-App-Site #12 waiting
⏳ Customer VPS rollout pending
Risks:
⚠️ CuisineFlow #47 delay would impact:
⚠️ Main-App #47 delay would impact:
- v2.0 launch date (Nov 20)
- Customer VPS deadline (Nov 20)
- Demo site sync (Nov 22)
@@ -632,7 +632,7 @@ PMO: Searching lessons across all projects...
Found 5 relevant lessons:
CuisineFlow:
Main-App:
- Sprint 08: Service boundary issues with shared DB
Tags: #service-extraction #database #refactoring
Key: Define boundaries at data model level first
@@ -646,13 +646,13 @@ PMO: Searching lessons across all projects...
Tags: #service-extraction #dependencies
Key: Watch for import cycles
CuisineFlow-Site:
Main-App-Site:
- Sprint 05: Sync issues during backend refactor
Tags: #sync #refactoring
Key: Coordinate deployments during major changes
Shared Patterns:
- /hyper-hive-labs/shared/architecture-patterns/service-extraction
- /your-org/shared/architecture-patterns/service-extraction
Key: Service Extraction Playbook
Common Themes:
@@ -672,15 +672,15 @@ User: /pmo-status
PMO: [Shows status]
Resource Analysis:
- Leo: 3 active projects (CuisineFlow, Site, Engine)
- Marketing: 1 project (HHL-Site)
- Leo: 3 active projects (Main-App, Site, Engine)
- Marketing: 1 project (Company-Site)
Bottleneck detected: Leo is on critical path for all technical work
Recommendations:
1. Prioritize work that unblocks others
2. Consider hiring/contracting for parallel work
3. Delegate non-critical work (HHL-Site content)
3. Delegate non-critical work (Company-Site content)
Would you like a detailed resource allocation report?
```
@@ -690,18 +690,18 @@ PMO: [Shows status]
```
User: Plan the v2.0 release across all affected projects
PMO: Release Coordination: CuisineFlow v2.0
PMO: Release Coordination: Main-App v2.0
======================================
Affected Projects:
1. CuisineFlow (main product)
1. Main-App (main product)
2. Intuit-Engine (new service)
3. CuisineFlow-Site (demo)
3. Main-App-Site (demo)
4. Customer VPS instances
Pre-Release Checklist:
✅ Intuit-Engine service deployed
🔄 CuisineFlow #47 complete (60%)
🔄 Main-App #47 complete (60%)
⏳ Integration tests pending
⏳ Demo site updates pending
⏳ Customer migration scripts ready
@@ -712,12 +712,12 @@ PMO: Release Coordination: CuisineFlow v2.0
→ Duration: 2 hours
→ Rollback plan: Ready
2. Deploy CuisineFlow v2.0 (main app)
2. Deploy Main-App v2.0 (main app)
→ Date: Nov 20
→ Duration: 4 hours
→ Rollback plan: Ready
3. Sync CuisineFlow-Site (demo)
3. Sync Main-App-Site (demo)
→ Date: Nov 22
→ Duration: 1 hour
→ Dependencies: Step 2 complete
@@ -767,11 +767,11 @@ shared_patterns = await wikijs.get_shared_docs("architecture-patterns")
User: Create a shared pattern document for service extraction
PMO: I'll create a pattern document based on lessons from:
- CuisineFlow Sprint 08
- CuisineFlow Sprint 12
- Main-App Sprint 08
- Main-App Sprint 12
- Intuit-Engine Sprint 02
Creating: /hyper-hive-labs/shared/architecture-patterns/service-extraction
Creating: /your-org/shared/architecture-patterns/service-extraction
Service Extraction Pattern
=========================
@@ -855,7 +855,7 @@ PMO: I'll create a pattern document based on lessons from:
**Deliverable:** Validated PMO plugin integrated with projman
**Tasks:**
1. Test with multiple projects (CuisineFlow, Site, Engine, HHL-Site)
1. Test with multiple projects (Main-App, Site, Engine, Company-Site)
2. Simulate deployment coordination scenarios
3. Test priority conflict resolution
4. Validate dependency tracking
@@ -911,10 +911,10 @@ PMO: I'll create a pattern document based on lessons from:
```
User: /pmo-status
PMO: CuisineFlow-Site: Waiting on dependencies
Blocked by: CuisineFlow #47 (API changes)
PMO: Main-App-Site: Waiting on dependencies
Blocked by: Main-App #47 (API changes)
Recommendation: Focus resources on CuisineFlow #47 to unblock Site work
Recommendation: Focus resources on Main-App #47 to unblock Site work
```
### Example 2: Resource Conflict Resolution
@@ -926,8 +926,8 @@ PMO: Leo assigned to 4 tasks across 3 projects
Estimated: 4 weeks work in 2 weeks timeline
Recommendations:
- Maintain focus on Critical priority (CuisineFlow #47)
- Delegate content work (HHL-Site #8) to marketing
- Maintain focus on Critical priority (Main-App #47)
- Delegate content work (Company-Site #8) to marketing
- Schedule architectural review (Intuit-Engine #3) as team session
```
@@ -936,13 +936,13 @@ PMO: Leo assigned to 4 tasks across 3 projects
```
User: /pmo-schedule
PMO: Critical Path: Engine → CuisineFlow → Site → Customer VPS
PMO: Critical Path: Engine → Main-App → Site → Customer VPS
Deadline: Nov 20 (Customer VPS commitment)
Current: Week 1 of 3
Status: On track
Risk: If CuisineFlow #47 delayed, entire timeline at risk
Risk: If Main-App #47 delayed, entire timeline at risk
Mitigation: Daily progress monitoring
```

View File

@@ -925,13 +925,13 @@ Orchestrator: I'll create a lesson in Wiki.js:
#service-extraction #api #database #refactoring #claude-code-loops
Creating page in Wiki.js... ✅
Path: /hyper-hive-labs/projects/cuisineflow/lessons-learned/sprints/sprint-16-intuit-engine
Path: /your-org/projects/my-project/lessons-learned/sprints/sprint-16-intuit-engine
Updating INDEX.md... ✅
Closing sprint issue #47... ✅
View lesson at: https://wiki.hyperhivelabs.com/hyper-hive-labs/projects/cuisineflow/lessons-learned/sprints/sprint-16-intuit-engine
View lesson at: https://wiki.your-company.com/your-org/projects/my-project/lessons-learned/sprints/sprint-16-intuit-engine
```
**Success Criteria:**

View File

@@ -155,9 +155,9 @@ GITEA_API_TOKEN=your_token
GITEA_OWNER=bandit
# ~/.config/claude/wikijs.env
WIKIJS_API_URL=https://wiki.hyperhivelabs.com/graphql
WIKIJS_API_URL=https://wiki.your-company.com/graphql
WIKIJS_API_TOKEN=your_token
WIKIJS_BASE_PATH=/hyper-hive-labs
WIKIJS_BASE_PATH=/your-org
```
**Project-Level:**
@@ -271,18 +271,18 @@ WIKIJS_PROJECT=projects/cuisineflow
## Wiki.js Structure
```
Wiki.js: https://wiki.hyperhivelabs.com
└── /hyper-hive-labs/
Wiki.js: https://wiki.your-company.com
└── /your-org/
├── projects/ # Project-specific
│ ├── cuisineflow/
│ ├── project-a/
│ │ ├── lessons-learned/
│ │ │ ├── sprints/
│ │ │ ├── patterns/
│ │ │ └── INDEX.md
│ │ └── documentation/
│ ├── cuisineflow-site/
│ ├── intuit-engine/
│ └── hhl-site/
│ ├── project-b/
│ ├── project-c/
│ └── company-site/
├── company/ # Company-wide
│ ├── processes/
│ ├── standards/
@@ -373,9 +373,9 @@ EOF
# Wiki.js config
cat > ~/.config/claude/wikijs.env << EOF
WIKIJS_API_URL=https://wiki.hyperhivelabs.com/graphql
WIKIJS_API_URL=https://wiki.your-company.com/graphql
WIKIJS_API_TOKEN=your_wikijs_token
WIKIJS_BASE_PATH=/hyper-hive-labs
WIKIJS_BASE_PATH=/your-org
EOF
# Secure files
@@ -565,7 +565,7 @@ Previous attempts failed due to:
### Immediate Actions
1. **Set up system configuration** (Gitea + Wiki.js tokens)
2. **Create Wiki.js base structure** at `/hyper-hive-labs`
2. **Create Wiki.js base structure** at `/your-org`
3. **Begin Phase 1.1a** - Gitea MCP Server implementation
4. **Begin Phase 1.1b** - Wiki.js MCP Server implementation
@@ -597,10 +597,10 @@ These decisions were finalized before development:
- **Minimum:** Python 3.10.0
### 2. Wiki.js Base Structure: Needs Creation
- **Status:** `/hyper-hive-labs` structure does NOT exist yet
- **Status:** `/your-org` structure does NOT exist yet
- **Action:** Run `setup_wiki_structure.py` during Phase 1.1b
- **Script:** See MCP-WIKIJS.md for complete setup script
- **Post-setup:** Verify at https://wiki.hyperhivelabs.com/hyper-hive-labs
- **Post-setup:** Verify at https://wiki.your-company.com/your-org
### 3. Testing Strategy: Both Mocks and Real APIs
- **Unit tests:** Use mocks for fast feedback during development