the-controller-autonomous-execution

Files (1)

• SKILL.md

SKILL.md (first lines)

# Autonomous Execution

Execute an implementation plan end-to-end with zero human interaction. Same quality gates as subagent-driven-development (fresh subagent per task, spec review, code quality review, final review), but the orchestrator handles all decisions autonomously.

**Core principle:** Full subagent-driven-development quality, zero human checkpoints — orchestrator resolves ambiguity from plan context, only surfaces when genuinely blocked.

**Announce at start:** "I'm using the the-controller-autonomous-execution skill to execute this plan autonomously. I'll report back when all tasks are complete."

## When to Use

```dot
digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Want fully autonomous execution?" [shape=diamond];
    "the-controller-autonomous-execution" [shape=box];
    "the-controller-subagent-driven-development" [shape=box];
    "Use the-controller-writing-plans first" [shape=box];

    "Have implementation plan?" -> "Want fully autonomous execution?" [label="yes"];
    "Have implementation plan?" -> "Use the-controller-writing-plans first" [label="no"];
    "Want fully autonomous execution?" -> "the-controller-autonomous-execution" [label="yes"];
    "Want fully autonomous execution?" -> "the-controller-subagent-driven-development" [label="no - want human checkpoints"];
}
```

**vs. subagent-driven-development:**
- Same quality gates (implementer + spec review + code quality review + final review)
- Orchestrator answers subagent questions from plan context (no human in loop)
- Includes worktree setup (no separate step needed)
- No merge at end (human reviews and decides)

**vs. executing-plans:**
- Fresh subagent per task (no context pollution)
- Automated review gates (not human checkpoints)
- Fully autonomous (no "ready for feedback" pauses)

## The Process

```dot
digraph process {
    rankdir=TB;

    "Set up worktree (the-controller-using-git-worktrees)" [shape=box];
    "Read plan, extract all tasks with full text, create TodoWrite" [shape=box];

    subgraph cluster_per_task {
        label="Per Task";
        "Dispatch implementer subagent" [shape=box];
        "Implementer asks questions?" [shape=diamond];
        "Orchestrator answers from plan context" [shape=box];
        "Orchestrator can answer?" [shape=diamond];
        "Surface to human (ONLY blocker case)" [shape=box style=filled fillcolor=lightyellow];
        "Implementer implements, tests, commits, self-reviews" [shape=box];
        "Dispatch spec reviewer subagent" [shape=box];
        "Spec compliant?" [shape=diamond];
        "Implementer fixes spec gaps" [shape=box];
        "Dispatch code quality reviewer subagent" [shape=box];
        "Code quality approved?" [shape=diamond];
        "Implementer fixes quality issues" [shape=box];
        "Mark task complete" [shape=box];
    }

    "More tasks?" [shape=diamond];
    "Dispatch final code reviewer for entire implementation" [shape=box];
    "Report final summary" [shape=box style=filled fillcolor=lightgreen];

    "Set up worktree (the-controller-using-git-worktrees)" -> "Read plan, extract all tasks with full text, create TodoWrite";
    "Read plan, extract all tasks with full text, create TodoWrite" -> "Dispatch implementer subagent";

    "Dispatch implementer subagent" -> "Implementer asks questions?";
    "Implementer asks questions?" -> "Orchestrator answers from plan context" [label="yes"];
    "Implementer asks questions?" -> "Implementer implements, tests, commits, self-reviews" [label="no"];
    "Orchestrator answers from plan context" -> "Orchestrator can answer?";
    "Orchestrator can answer?" -> "Dispatch implementer subagent" [label="yes - send answer"];
    "Orchestrator can answer?" -> "Surface to human (ONLY blocker case)" [label="no"];
    "Surface to human (ONLY blocker case)" -> "Dispatch implementer subagent" [label="human answers"];

    "Implementer implements, tests, commits, self-reviews" -> "Dispatch spec reviewer subagent";
    "Dispatch spec reviewer subagent" -> "Spec compliant?";
    "Spec compliant?" -> "Implementer fixes spec gaps" [label="no"];
    "Implementer fixes spec gaps" -> "Dispatch spec reviewer subagent" [label="re-review"];
    "Spec compliant?" -> "Dispatch code quality reviewer subagent" [label="yes"];
    "Dispatch code quality reviewer subagent" -> "Code quality approved?";
    "Code quality approved?" -> "Implementer fixes quality issues" [label="no"];
    "Implementer fixes quality issues" -> "Dispatch code quality reviewer subagent" [label="re-review"];
    "Code quality approved?" -> "Mark task complete" [label="yes"];

    "Mark task complete" -> "More tasks?";
    "More tasks?" -> "Dispatch implementer subagent" [label="yes"];
    "More tasks?" -> "Dispatch final code reviewer for entire implementation" [label="no"];
    "Dispatch final code reviewer for entire implementation" -> "Report final summary";
}
```

## Prompt Templates

Reuse from the-controller-subagent-driven-development:
- Implementer: `the-controller-subagent-driven-development/implementer-prompt.md`
- Spec reviewer: `the-controller-subagent-driven-development/spec-reviewer-prompt.md`
- Code quality reviewer: `the-controller-subagent-driven-development/code-quality-reviewer-prompt.md`

## Orchestrator Question Handling

When an implementer subagent asks a question, the orchestrator MUST attempt to answer it before surfacing to the human:

1. **Check plan text** — Does the plan specify the answer?
2. **Check project context** — Can you determine the answer from codebase, CLAUDE.md, docs?
3. **Make reasonable inference** — Is there an obvious correct answer given the architecture?

**Only surface to human if:** The answer genuinely cannot be determined from available context and guessing wrong would cause significant rework.

**When answering:** Dispatch a fresh implementer subagent with the original task text plus the answer. Provide the answer clearly, with reasoning, so the implementer can proceed confidently.

## Final Summary Report

After all tasks complete and final review passes, report:

- Tasks completed (N/N)
- Files created/modified (list)

From kwannoel/the-controller, MIT.

More from kwannoel/the-controller