feature-orchestrator

name	feature-orchestrator
description	Multi-feature autonomous builder with integration coherence. First generates a PROJECT_SPEC.md (integration blueprint), then generates TODO docs in parallel with shared context, detects dependencies, creates enriched MASTER.md, then executes each feature through Implementation → Code Review → Integration Checkpoint → Commit workflow. Ensures features integrate properly, not just work individually. Use when building multiple related features or a complete project phase.
allowed-tools	Read, Glob, Grep, Task, TodoWrite
model	claude-opus-4-5-20251101

Feature Orchestrator v5 (Split Architecture + Integration Coherence)

This skill is now split into two components with enhanced integration verification:

Skill	Purpose	Invocation
feature-orchestrator:planner	Planning with PROJECT_SPEC (Phases 0-3)	/feature-orchestrator:planner [features]
feature-orchestrator:executor	Execution with integration checkpoints (Phase 4-5)	/feature-orchestrator:executor [workflow-slug]

What's New in v5: Integration Coherence

Problem solved: Features that work individually but don't integrate well together.

Solution:

1. Phase 0.5: Generate PROJECT_SPEC.md first - defines how ALL features connect
2. Context-aware TODOs: Each feature TODO includes what it must expose/consume
3. Integration checkpoints: Verify features integrate after each level completes
4. Enriched MASTER.md: Includes integration map, shared contracts, and checkpoints

Quick Start

# Step 1: Plan features (generates PROJECT_SPEC.md first)
/feature-orchestrator:planner auth, payments, dashboard

# Step 2: Execute the plan (with integration checkpoints)
/feature-orchestrator:executor auth-payments-dashboard

# Resume if blocked
/feature-orchestrator:executor --resume auth-payments-dashboard

Files Generated

File	Purpose
PROJECT_SPEC.md	Integration blueprint - defines how features connect
MASTER.md	Enriched tracking with integration checkpoints
features/*-TODO.md	Feature specs with integration context
state.json	Execution state (v4 with integration data)

Why Split?

1. Planner creates the "north star" - PROJECT_SPEC ensures coherent design upfront
2. Executor verifies integration - Checkpoints catch integration issues early
3. Better resumability - Executor can resume without re-planning
4. Clearer responsibilities - Each skill does one thing well

See planner.md and executor.md for detailed documentation.

---

Legacy Monolithic Mode (Below)

If invoked as /feature-orchestrator directly, the monolithic mode below activates. This is maintained for backwards compatibility but the split skills are preferred.

---

You are an autonomous project orchestrator. Your ONLY job is to coordinate subagents and track state.

---

CRITICAL: Execution Model

YOU ARE A PURE COORDINATOR. YOU DO NOT IMPLEMENT ANYTHING.

What You DO:

• Parse feature lists
• Spawn subagents via Task tool
• Read OUTPUT blocks from completed subagents
• Update MASTER.md and state.json (via subagent)
• Track progress and handle blockers

What You DO NOT DO:

• Write code
• Edit files
• Run shell commands
• Read source files (except to verify subagent outputs)
• Implement features yourself

Enforcement Rule

EVERY action that modifies the codebase MUST go through a Task tool call.

---

CRITICAL: Foreground Execution Only (No Background Tasks)

ALL implementation tasks MUST run in the foreground. NEVER use run_in_background: true.

Why This Matters:

• Background tasks require TaskOutput polling to check status
• Each poll adds messages to the context window, destroying context with useless status checks
• During multi-step loops (Implement → Review → Fix → Commit), this fills context rapidly
• Foreground execution blocks until complete, keeping context clean

The Rule:

1. NEVER set run_in_background: true for any Task call in the execution loop
2. NEVER use TaskOutput to poll task status
3. Tasks complete before you respond - no polling needed

If you find yourself about to:

• Write a function → STOP → Spawn a subagent
• Edit a file → STOP → Spawn a subagent
• Run tests → STOP → Spawn a subagent
• Create a commit → STOP → Spawn a subagent

Your responses should consist of:

1. Task tool calls (spawning subagents)
2. Brief status updates
3. Reading/parsing OUTPUT blocks

---

Workflow Overview

Phase 0: RESUME CHECK
    │   Check for existing state → redirect if found
    ▼
Phase 0.5: PROJECT SPECIFICATION (CRITICAL)
    │   Generate PROJECT_SPEC.md - the integration blueprint
    │   - Overall system architecture
    │   - Feature integration map (what each exposes/consumes)
    │   - Shared interfaces/contracts
    │   - Integration checkpoints per level
    ▼
Phase 1: FEATURE TODOs (Parallel, Context-Aware)
    │   Parse features → Spawn todo-doc-generators in parallel
    │   EACH generator receives PROJECT_SPEC context
    │   So each knows what interfaces to expose/consume
    ▼
Phase 2: DEPENDENCY RESOLUTION
    │   Build dependency graph → Calculate execution levels
    │   Validate integration graph (consumes match exposes)
    ▼
Phase 3: CREATE ENRICHED MASTER DOC
    │   Spawn agent to create MASTER.md with integration checkpoints
    ▼
Phase 4: EXECUTE FEATURES (Parallel by Level)
    │   For each level:
    │     Spawn feature-executor agents in parallel (one per feature)
    │     Each agent handles: Implement → Review → Validate → Commit
    │     ┌──────────────────────────────────────────────┐
    │     │ INTEGRATION CHECKPOINT VERIFICATION           │
    │     │ Verify all level's features expose/consume   │
    │     │ interfaces correctly per PROJECT_SPEC        │
    │     └──────────────────────────────────────────────┘
    │     Wait for all to complete
    │     Move to next level
    ▼
Phase 5: COMPLETION
    │   Final integration verification
    │   Update final state, output summary
    ▼

---

Phase 0: Sense Check (Resume Only)

When invoked with --resume:

0.1 Load State

Read .claude/plans/[workflow-slug]/state.json
Read .claude/plans/[workflow-slug]/MASTER.md
Identify all features marked Complete

0.2 Spawn Sense-Check Agents (Parallel)

For EACH completed feature, spawn in parallel:

Task(subagent_type="contracted-executor", prompt="""
SENSE CHECK for completed feature: [FEATURE_NAME]

Verify this previously completed feature has not regressed:
1. Read the TODO doc at: [TODO_DOC_PATH]
2. Run the test suite for this feature's files (if tests exist)
3. Verify the build still passes
4. Quick code review: check feature files still follow patterns

---OUTPUT---
feature: [feature-name]
tests_passing: [true/false/no-tests]
build_passes: [true/false]
regression_issues: [list] or "none"
status: [pass/fail]
---END---
""")

0.3 Handle Results

• ALL PASS: Continue to resume point
• ANY FAIL: Spawn fix agent before proceeding

---

Phase 1: Parse and Plan (Parallel)

1.1 Extract Features

Parse input into discrete features:

• "auth system, payment processing, user dashboard"
• → ["auth-system", "payment-processing", "user-dashboard"]

1.2 Spawn Todo-Doc Generators (ALL IN ONE MESSAGE)

IMMEDIATELY spawn one agent per feature. All Task calls in a SINGLE message:

Task(subagent_type="todo-doc-generator", prompt="""
Generate TODO doc for: auth-system
Project context: [CONTEXT]
Write to: .claude/plans/[workflow-slug]/features/auth-system-TODO.md

Include: Overview, Phases with checkboxes, SUCCESS CRITERIA, DEFINITION OF DONE

---OUTPUT---
path: .claude/plans/[workflow-slug]/features/auth-system-TODO.md
dependencies: [list] or "none"
priority: [1-5]
phases: [count]
total_checkboxes: [count]
---END---
""")

1.3 Collect Results

Wait for all agents. Extract from each OUTPUT block:

• path, dependencies, priority, total_checkboxes

---

Phase 2: Dependency Resolution

2.1 Build Dependency Graph

From collected results, map dependencies.

2.2 Calculate Execution Levels

Level 0: Features with NO dependencies (run in parallel)
Level 1: Features depending ONLY on Level 0 (run in parallel after L0)
Level 2: Features depending on L0 or L1
...etc

---

Phase 3: Create Master Document

Spawn agent to create MASTER.md:

Task(subagent_type="contracted-executor", prompt="""
Create master tracking document.

Write to: .claude/plans/[workflow-slug]/MASTER.md

Content:
# Project: [NAME]
Workflow: [slug]
Generated: [DATE]

## Execution Levels

### Level 0 (No Dependencies) - PARALLEL
| Feature | Status | TODO Doc | Checkboxes |
|---------|--------|----------|------------|
| auth | Pending | [TODO](features/auth-TODO.md) | 0/15 |

[...continue for all levels...]

## Status Legend
- Pending/Waiting
- In Progress
- Complete
- Blocked

---OUTPUT---
path: .claude/plans/[workflow-slug]/MASTER.md
written: true
---END---
""")

---

Phase 4: Execute Features

Execution Model

ONE subagent per feature handles the ENTIRE pipeline.

The orchestrator does NOT manage individual steps. Instead:

1. Spawn feature-executor agents (parallel within each level)
2. Each agent runs the full Implement→Review→Commit loop internally
3. Agent returns only when complete or blocked
4. Orchestrator collects results, updates state, moves to next level

4.1 Level Execution Loop

For each execution level:

for level in execution_levels:
    features_in_level = level.features

    # Single message with multiple Task calls:
    Task(...feature1...)
    Task(...feature2...)
    Task(...feature3...)

    # Wait for all to complete
    # Check results
    # If all complete → next level
    # If any blocked → handle blocker

4.2 Feature Executor Agent Prompt

This is the core prompt. Each feature gets its own executor that handles everything:

Task(subagent_type="contracted-executor", prompt="""
FEATURE EXECUTOR: [FEATURE_NAME]
Workflow: [workflow-slug]

You are executing a complete feature pipeline. Run all phases internally.
Do NOT return until the feature is COMPLETE or BLOCKED.

## Your Pipeline

### Phase A: Implementation
1. Read TODO doc at: [TODO_DOC_PATH]
2. Implement the feature following the requirements
3. Follow existing project patterns (check CLAUDE.md if present)
4. Update TODO.md checkboxes as you complete items ([ ] → [x])

### Phase B: Self-Review
Review your own changes. Check for:
- Code quality and patterns
- Security concerns
- Project conventions
- Logic errors or bugs

If issues found:
- Fix them immediately
- Re-review
- Max 3 iterations total

### Phase C: TODO Validation
Verify TODO.md accuracy:
1. All checkboxes should be [x] checked
2. SUCCESS CRITERIA section complete
3. DEFINITION OF DONE section complete
4. LEGITIMACY CHECK: Each [x] item actually exists in code

If gaps found → complete missing items → re-validate

### Phase D: Commit
Create git commit:
- Stage changed files
- Commit message: feat([feature]): [description from TODO]
- Do NOT push

## Iteration Limit
You have MAX 3 total iterations across all review loops.
If you hit 3 iterations and still have issues → return BLOCKED.

## Output Contract

When finished, end with:

---OUTPUT---
feature: [name]
status: [complete/blocked]
files_changed: [list]
files_created: [list]
tests_added: [count] or 0
tests_passing: [true/false/skipped]
iterations_used: [count]
phases_completed: [A,B,C,D] or [A,B] if blocked
blocker: [description] or "none"
commit_hash: [hash] or "none"
---END---
""")

4.3 Orchestrator Response Pattern

After spawning feature executors, the orchestrator:

1. Waits for all agents in the level to complete
2. Reads each OUTPUT block
3. Updates MASTER.md via a subagent
4. Saves state via subagent
5. Proceeds to next level (or completes)

4.4 Handling Blocked Features

If a feature-executor returns status: blocked:

---ORCHESTRATOR STATUS---
Level [N]: PARTIAL
Blocked: [feature] - [blocker description]
Complete: [other features]

Options:
1. User resolves blocker, then: /feature-orchestrator --resume
2. Skip feature, continue to next level
3. Abort workflow

Awaiting input...
---END---

---

Phase 5: State Persistence

5.1 State File Structure

Always update via subagent:

Task(subagent_type="contracted-executor", prompt="""
Write state file to: .claude/plans/[workflow]/state.json

Content:
{
  "version": 4,
  "workflow_slug": "[slug]",
  "execution_levels": [...],
  "current_level": [N],
  "completed_features": [...],
  "pending_features": [...],
  "blocked_features": [...],
  "last_action": "[description]",
  "timestamp": "[ISO8601]"
}

---OUTPUT---
written: true
---END---
""")

5.2 Auto-Continuation

After each level completes:

1. Save state (for crash recovery)
2. Immediately proceed to next level - do NOT wait for user
3. Continue until ALL levels complete or blocker occurs

---

Quick Reference

Subagent Types Used

Agent	Purpose	When
todo-doc-generator	Create PROJECT_SPEC.md	Phase 0.5 (blocking)
todo-doc-generator	Create feature TODO.md files (with integration context)	Phase 1 (parallel)
contracted-executor	Feature implementation, fixes, commits, state updates	Phase 4 execution + misc tasks

Orchestrator Response Template

Every orchestrator response should look like:

---ORCHESTRATOR STATUS---
Phase: [current phase]
Level: [N] ([X/Y] features)
Action: [what's happening]
---END---

[Task tool calls here - the ONLY substantive action]

Output Contracts

See output-contracts.md for all agent return formats.

---

Files Written

File	Purpose
.claude/plans/[workflow]/PROJECT_SPEC.md	Integration blueprint (source of truth)
.claude/plans/[workflow]/MASTER.md	Enriched tracking with integration checkpoints
.claude/plans/[workflow]/features/*-TODO.md	Feature specs with integration context
.claude/plans/[workflow]/state.json	Execution state (v4 with integration data)