Orchestrate Ecosystem Command

Multi-submodule zero human-in-the-loop orchestration for entire CODITECT ecosystems.

System Prompt

⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. IMMEDIATELY execute - no questions, no explanations first
2. ALWAYS show full output from script/tool execution
3. ALWAYS provide summary after execution completes

DO NOT:

• Say "I don't need to take action" - you ALWAYS execute when invoked
• Ask for confirmation unless requires_confirmation: true in frontmatter
• Skip execution even if it seems redundant - run it anyway

The user invoking the command IS the confirmation.

---

Usage

/orchestrate-ecosystem [options]

Options

• --root PATH - Root directory (default: current)
• --phase PHASE - Execute specific phase (0.8, 0.9, 1.0, etc.)
• --execute - Generate and execute agent tasks
• --parallel N - Parallel analysis workers (default: 4)
• --report - Generate comprehensive compliance report
• --generate-script - Generate master coordination script
• --format FORMAT - Output format: text, json (default: text)
• --output FILE - Output to file

Phases

Phase	Category	Priority	Description
0.7	dev/	COMPLETE	Development tools (11 submodules)
0.8	core/	P0	Framework core (5 submodules)
0.9	cloud/	P0	Cloud platform (4 submodules)
1.0	docs/	P1	Documentation (5 submodules)
1.1	ops/	P2	Operations (7 submodules)
1.2	gtm/	P1	Go-to-market (9 submodules)
1.3	labs/	P2	Research/labs (14 submodules)
1.4	mixed	P2	Market/compliance/investors (4 submodules)

Execution

When invoked with --execute, this command will:

1. Discover all submodules in ecosystem
2. Analyze each submodule in parallel
3. Generate phase-specific execution plan
4. Orchestrate agents for each non-compliant submodule
5. Track progress and update master TASKLIST.md
6. Report final ecosystem compliance status

Agent Orchestration Flow

For each phase:
  For each non-compliant submodule:
    1. Task(subagent_type="codebase-analyzer", prompt="Analyze {submodule}")
    2. Task(subagent_type="project-organizer", prompt="Standardize {submodule}")
    3. Task(subagent_type="codi-documentation-writer", prompt="Create CLAUDE.md")
    4. Task(subagent_type="compliance-checker-agent", prompt="Verify 90+")
    5. /git-sync --target {submodule}

  Mark phase complete in master TASKLIST.md

Example Workflows

Analyze Ecosystem

/orchestrate-ecosystem --report

Execute Single Phase

/orchestrate-ecosystem --phase 0.8 --execute

Generate Master Script

/orchestrate-ecosystem --generate-script --output ecosystem_orchestration.py

Full Ecosystem Automation

# Execute all phases sequentially
for phase in 0.8 0.9 1.0 1.1 1.2 1.3 1.4; do
  /orchestrate-ecosystem --phase $phase --execute
done

Generated Artifacts

• ecosystem_orchestration.py - Master coordination script with all agent invocations
• compliance_report.txt - Full ecosystem compliance report
• execution_plan.json - Detailed task breakdown per phase

Master Orchestrator Integration

This command updates the master orchestrator documents:

coditect-rollout-master/
├── docs/project-management/
│   ├── PROJECT-PLAN.md  ← Updated with phase status
│   └── TASKLIST.md      ← Checkboxes marked complete
└── MEMORY-CONTEXT/
    └── checkpoint.md    ← Phase completion checkpoint

For Customers/Contributors

Use this command to orchestrate compliance across your CODITECT project:

# In your project root
cd /path/to/my-coditect-project

# Analyze ecosystem status
/orchestrate-ecosystem --report

# Execute orchestration for all non-compliant submodules
/orchestrate-ecosystem --execute

# Or execute phase by phase
/orchestrate-ecosystem --phase 0.8 --execute

Output Example

==============================================================
CODITECT ECOSYSTEM ORCHESTRATOR
==============================================================
Root: /path/to/project
Mode: Execute
Phase: 0.8

[Analyzing ecosystem...]
Discovered: 58 submodules
Compliant: 11/58 (19%)
Average Score: 69.2/100

[Generating execution plan...]
Tasks to execute: 47
Estimated duration: 3.9 hours

[Executing Phase 0.8: core/ (5 submodules)]
  → coditect-core: [project-organizer] [codi-documentation-writer] ✅
  → coditect-core-framework: [project-organizer] [codi-documentation-writer] ✅
  → coditect-dashboard: [project-organizer] [codi-documentation-writer] ✅
  → coditect-web-search-tools: [project-organizer] [codi-documentation-writer] ✅
  → coditect-core-architecture: ✅ Already compliant

[Phase 0.8 Complete]
Compliance: 5/5 (100%)
Average Score: 94.2/100

---

Action Policy

<default_behavior> This command orchestrates multi-submodule compliance. Proceeds with:

• Ecosystem discovery
• Parallel analysis
• Phase execution (if --execute)
• Progress tracking

Reports compliance status and generates plans. </default_behavior>

After execution, verify: - All submodules analyzed - Agents invoked correctly - Compliance improved - TASKLIST.md updated

Success Output

When orchestrate-ecosystem completes:

✅ COMMAND COMPLETE: /orchestrate-ecosystem
Phase: <phase>
Submodules: <N> processed
Compliance: <before>% → <after>%
Status: Phase complete

Completion Checklist

Before marking complete:

• Submodules discovered
• Analysis completed
• Agents executed (if --execute)
• Reports generated
• TASKLIST.md updated

Failure Indicators

This command has FAILED if:

• ❌ No submodules found
• ❌ Analysis failed
• ❌ Agent execution errors
• ❌ Compliance not improved

When NOT to Use

Do NOT use when:

• Single submodule (use /orchestrate-submodule)
• No ecosystem structure
• Quick single fix needed

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skip --report first	Blind execution	Analyze first
Force all phases	Too aggressive	Phase by phase
Ignore failures	Incomplete	Handle each failure

Principles

This command embodies:

• #3 Complete Execution - Full ecosystem processing
• #1 Self-Provisioning - Auto agent orchestration
• #6 Clear, Understandable - Clear progress

Full Standard: CODITECT-STANDARD-AUTOMATION.md

---

Related: /orchestrate-submodule, orchestration-automation skill