Orchestration Automation Skill

Orchestration Automation Skill

When to Use This Skill

Use this skill when implementing orchestration automation patterns in your codebase.

How to Use This Skill

1. Review the patterns and examples below
2. Apply the relevant patterns to your implementation
3. Follow the best practices outlined in this skill

Purpose

Zero human-in-the-loop orchestration for bringing submodules and ecosystems to CODITECT compliance standards. Enables fully autonomous standardization workflows using specialized AI agents.

Capabilities

1. Submodule Orchestration

Analyze and standardize individual submodules:

• Compliance score calculation (0-100)
• Gap identification (CLAUDE.md, symlinks, docs/, etc.)
• Agent task generation
• Automated execution plan

2. Ecosystem Orchestration

Coordinate standardization across entire ecosystems:

• Multi-submodule parallel analysis
• Phase-based execution (0.8, 0.9, 1.0, etc.)
• Master coordination script generation
• Progress tracking and reporting

3. Agent Coordination

Orchestrate specialized agents for each task:

• project-organizer - Directory structure
• codi-documentation-writer - CLAUDE.md files
• compliance-checker-agent - Score validation
• git-workflow-orchestrator - Sync operations

Usage

Single Submodule

# Analyze submodule
python3 scripts/orchestrate-submodule.py --path /path/to/submodule

# Full automation
python3 scripts/orchestrate-submodule.py --path /path/to/submodule --auto-commit --auto-push

# Generate agent script
python3 scripts/orchestrate-submodule.py --path /path/to/submodule --generate-script

Full Ecosystem

# Analyze ecosystem
python3 scripts/orchestrate-ecosystem.py --root /path/to/project

# Execute specific phase
python3 scripts/orchestrate-ecosystem.py --root /path/to/project --phase 0.8 --execute

# Generate master coordination script
python3 scripts/orchestrate-ecosystem.py --root /path/to/project --generate-script

# Generate compliance report
python3 scripts/orchestrate-ecosystem.py --root /path/to/project --report

Via Slash Command

# Orchestrate current submodule
/orchestrate-submodule

# Orchestrate entire ecosystem
/orchestrate-ecosystem --phase 0.8

# Generate orchestration report
/orchestrate-ecosystem --report

Via Task Tool (Agentic)

# Single submodule
Task(subagent_type="orchestrator", prompt="Bring submodules/core/coditect-core to 90+ CODITECT compliance using project-organizer and codi-documentation-writer agents")

# Ecosystem phase
Task(subagent_type="orchestrator", prompt="Execute Phase 0.8 (core category) orchestration, bringing all 5 core submodules to 90+ compliance")

# Full ecosystem
Task(subagent_type="orchestrator", prompt="Generate and execute ecosystem-wide orchestration plan for all phases 0.8-1.4")

Agent Task Flow

1. Analysis Phase
   └─→ orchestrate-submodule.py analyzes structure
   └─→ Generates compliance score and gap list
   └─→ Creates agent task queue

2. Execution Phase
   └─→ For each task in queue:
       ├─→ project-organizer: Directory standardization
       ├─→ codi-documentation-writer: CLAUDE.md creation/refactoring
       └─→ compliance-checker-agent: Score validation

3. Sync Phase
   └─→ git-workflow-orchestrator: Commit and push
   └─→ Update master repo pointer
   └─→ Mark phase complete in master tasklist.md

4. Verification Phase
   └─→ Re-run analysis to confirm 90+ score
   └─→ Generate completion report

Compliance Scoring

Check	Points	Criteria
CLAUDE.md	25	Exists and <150 lines
.coditect symlink	10	Points to distributed intelligence
.claude symlink	10	Points to .coditect
docs/ directory	15	Exists with structure
README.md	10	Exists
.gitignore	10	Exists
project-plan.md	10	In docs/project-management/
Clean root	10	<3 unexpected files
Total	100	Target: 90+

Generated Artifacts

Per Submodule

• agent_tasks.py - Executable agent invocations
• docs/project-management/project-plan.md - Submodule planning
• docs/project-management/tasklist.md - Submodule tasks

Per Ecosystem

• ecosystem_orchestration.py - Master coordination script
• compliance_report.txt - Ecosystem compliance report
• execution_plan.json - Detailed task breakdown

Integration with Master Orchestrator

This skill integrates with the master orchestrator in coditect-rollout-master:

coditect-rollout-master/
├── docs/project-management/
│   ├── project-plan.md  ← Master orchestration plan
│   └── tasklist.md      ← Phase-level tracking
└── submodules/*/docs/project-management/
    ├── project-plan.md  ← Submodule goals
    └── tasklist.md      ← Detailed tasks

The skill reads master phase definitions and generates submodule-specific execution plans that roll up to master progress tracking.

Customer/Contributor Usage

This skill is designed for general use by CODITECT customers and contributors:

1. New Projects: Run ecosystem orchestrator to bring existing project to CODITECT standards
2. Submodule Addition: Run submodule orchestrator when adding new components
3. Compliance Validation: Run in report mode to check ongoing compliance
4. Automation: Use generated scripts for CI/CD integration

Success Output

When this skill is successfully applied, you MUST output:

✅ SKILL COMPLETE: orchestration-automation

Completed:
- [x] Compliance analysis complete (score calculated)
- [x] Gap identification finished (missing components documented)
- [x] Agent task generation complete (execution plan created)
- [x] Automated execution successful (compliance score improved)
- [x] Verification complete (target score achieved)

Outputs:
- Compliance report: [file path] (current score, gaps, target)
- Agent tasks: [file path] (generated invocations)
- Updated submodule: [path] (CLAUDE.md, symlinks, docs/, etc.)
- Final compliance score: [score]/100 (✅ if ≥90)

Completion Checklist

Before marking this skill as complete, verify:

• Initial compliance score calculated and documented
• All gaps identified (missing CLAUDE.md, symlinks, docs/, etc.)
• Agent task queue generated with proper invocations
• Specialized agents executed (project-organizer, codi-documentation-writer, etc.)
• Git sync completed (commit, push, update master pointer)
• Final compliance score ≥90 achieved
• Verification re-run confirms sustained compliance
• Master tasklist updated with phase completion

Failure Indicators

This skill has FAILED if:

• ❌ Compliance score not calculated or documented
• ❌ Gaps identified but agent tasks not generated
• ❌ Agent invocations created but not executed
• ❌ Execution completed but compliance score still <90
• ❌ Changes not committed/pushed to git
• ❌ Master repo pointer not updated
• ❌ Verification shows compliance regressed

When NOT to Use

Do NOT use this skill when:

• Submodule already at 90+ compliance (no gaps to fix)
• Manual customization required (standard structure won't work)
• Non-CODITECT project (different framework/standards)
• Single file change only (overhead > benefit, use direct edit)
• Experimental/prototype repository (premature standardization)

Use alternatives:

• For high-compliance submodules: compliance-checker-agent for validation only
• For custom structures: Manual organization with project-organizer agent
• For non-CODITECT: Framework-specific organization skills
• For single changes: Direct file editing

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skipping compliance analysis	Don't know what needs fixing	Always run analysis first to identify gaps
Manual execution of tasks	Error-prone, time-consuming	Use generated agent invocations for automation
No verification step	Can't confirm success	Re-run analysis to verify score improved
Ignoring git sync	Changes not persisted	Always commit, push, update master pointer
One-size-fits-all approach	Doesn't account for submodule specifics	Customize agent tasks based on gap analysis
Not updating master tasklist	Progress not tracked	Mark phase complete in master PROJECT-PLAN
Running on dirty repo	Git conflicts, unclear changes	Ensure clean working directory first
Over-standardizing	Destroys valuable custom structure	Preserve custom docs, only add missing standard components

Principles

This skill embodies:

• #10 Full Automation - Zero human-in-the-loop orchestration for compliance
• #1 Recycle → Extend → Re-Use → Create - Use existing specialized agents
• #4 Separation of Concerns - Each agent handles its domain (docs, structure, git)
• #8 No Assumptions - Verify compliance before and after automation
• #11 Resilience and Robustness - Multi-phase execution with verification gates

Full Standard: CODITECT-STANDARD-AUTOMATION.md

Related Components

• Scripts: scripts/orchestrate-submodule.py, scripts/orchestrate-ecosystem.py
• Commands: /orchestrate-submodule, /orchestrate-ecosystem
• Agents: orchestrator, project-organizer, codi-documentation-writer

---

Status: Production Ready Author: CODITECT Team Version: 1.0.0 Last Updated: 2025-12-09