Delegated-Worker Development

Execute plan by dispatching fresh delegated worker per task, with two-stage review after each: spec compliance review first, then code quality review.

Core principle: Fresh delegated implementation pass per task + two-stage review (spec then quality) = high quality, fast iteration

When to Use

dot

digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Tasks mostly independent?" [shape=diamond];
    "Stay in this session?" [shape=diamond];
    "delegated-worker-development" [shape=box];
    "executing-plans" [shape=box];
    "Manual execution or brainstorm first" [shape=box];

    "Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
    "Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
    "Tasks mostly independent?" -> "Stay in this session?" [label="yes"];
    "Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
    "Stay in this session?" -> "delegated-worker-development" [label="yes"];
    "Stay in this session?" -> "executing-plans" [label="no - parallel session"];
}

vs. Executing Plans (parallel session):

•Same session (no context switch)
•Fresh delegated implementation pass per task (no context pollution)
•Two-stage review after each task: spec compliance first, then code quality
•Faster iteration (no human-in-loop between tasks)

The Process

dot

digraph process {
    rankdir=TB;

    subgraph cluster_per_task {
        label="Per Task";
        "Dispatch implementer delegated worker (./implementer-prompt.md)" [shape=box];
        "Implementer delegated worker asks questions?" [shape=diamond];
        "Answer questions, provide context" [shape=box];
        "Implementer delegated worker implements, tests, commits, self-reviews" [shape=box];
        "Dispatch spec reviewer delegated worker (./spec-reviewer-prompt.md)" [shape=box];
        "Spec reviewer delegated worker confirms code matches spec?" [shape=diamond];
        "Implementer delegated worker fixes spec gaps" [shape=box];
        "Dispatch code quality reviewer delegated worker (./code-quality-reviewer-prompt.md)" [shape=box];
        "Code quality reviewer delegated worker approves?" [shape=diamond];
        "Implementer delegated worker fixes quality issues" [shape=box];
        "Mark task complete in checklist" [shape=box];
    }

    "Read plan, extract all tasks with full text, note context, create checklist" [shape=box];
    "More tasks remain?" [shape=diamond];
    "Dispatch final code reviewer delegated worker for entire implementation" [shape=box];
    "Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];

    "Read plan, extract all tasks with full text, note context, create checklist" -> "Dispatch implementer delegated worker (./implementer-prompt.md)";
    "Dispatch implementer delegated worker (./implementer-prompt.md)" -> "Implementer delegated worker asks questions?";
    "Implementer delegated worker asks questions?" -> "Answer questions, provide context" [label="yes"];
    "Answer questions, provide context" -> "Dispatch implementer delegated worker (./implementer-prompt.md)";
    "Implementer delegated worker asks questions?" -> "Implementer delegated worker implements, tests, commits, self-reviews" [label="no"];
    "Implementer delegated worker implements, tests, commits, self-reviews" -> "Dispatch spec reviewer delegated worker (./spec-reviewer-prompt.md)";
    "Dispatch spec reviewer delegated worker (./spec-reviewer-prompt.md)" -> "Spec reviewer delegated worker confirms code matches spec?";
    "Spec reviewer delegated worker confirms code matches spec?" -> "Implementer delegated worker fixes spec gaps" [label="no"];
    "Implementer delegated worker fixes spec gaps" -> "Dispatch spec reviewer delegated worker (./spec-reviewer-prompt.md)" [label="re-review"];
    "Spec reviewer delegated worker confirms code matches spec?" -> "Dispatch code quality reviewer delegated worker (./code-quality-reviewer-prompt.md)" [label="yes"];
    "Dispatch code quality reviewer delegated worker (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer delegated worker approves?";
    "Code quality reviewer delegated worker approves?" -> "Implementer delegated worker fixes quality issues" [label="no"];
    "Implementer delegated worker fixes quality issues" -> "Dispatch code quality reviewer delegated worker (./code-quality-reviewer-prompt.md)" [label="re-review"];
    "Code quality reviewer delegated worker approves?" -> "Mark task complete in checklist" [label="yes"];
    "Mark task complete in checklist" -> "More tasks remain?";
    "More tasks remain?" -> "Dispatch implementer delegated worker (./implementer-prompt.md)" [label="yes"];
    "More tasks remain?" -> "Dispatch final code reviewer delegated worker for entire implementation" [label="no"];
    "Dispatch final code reviewer delegated worker for entire implementation" -> "Use superpowers:finishing-a-development-branch";
}

Prompt Templates

•./implementer-prompt.md - Dispatch implementer delegated worker
•./spec-reviewer-prompt.md - Dispatch spec compliance reviewer delegated worker
•./code-quality-reviewer-prompt.md - Dispatch code quality reviewer delegated worker

Example Workflow

code

You: I'm using Delegated-Worker Development to execute this plan.

[Read plan file once: docs/plans/feature-plan.md]
[Extract all 5 tasks with full text and context]
[Create checklist with all tasks]

Task 1: Hook installation script

[Get Task 1 text and context (already extracted)]
[Dispatch implementation delegated worker with full task text + context]

Implementer: "Before I begin - should the hook be installed at user or system level?"

You: "User level (~/.config/superpowers/hooks/)"

Implementer: "Got it. Implementing now..."
[Later] Implementer:
  - Implemented install-hook command
  - Added tests, 5/5 passing
  - Self-review: Found I missed --force flag, added it
  - Committed

[Dispatch spec compliance reviewer]
Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra

[Get git SHAs, dispatch code quality reviewer]
Code reviewer: Strengths: Good test coverage, clean. Issues: None. Approved.

[Mark Task 1 complete]

Task 2: Recovery modes

[Get Task 2 text and context (already extracted)]
[Dispatch implementation delegated worker with full task text + context]

Implementer: [No questions, proceeds]
Implementer:
  - Added verify/repair modes
  - 8/8 tests passing
  - Self-review: All good
  - Committed

[Dispatch spec compliance reviewer]
Spec reviewer: ❌ Issues:
  - Missing: Progress reporting (spec says "report every 100 items")
  - Extra: Added --json flag (not requested)

[Implementer fixes issues]
Implementer: Removed --json flag, added progress reporting

[Spec reviewer reviews again]
Spec reviewer: ✅ Spec compliant now

[Dispatch code quality reviewer]
Code reviewer: Strengths: Solid. Issues (Important): Magic number (100)

[Implementer fixes]
Implementer: Extracted PROGRESS_INTERVAL constant

[Code reviewer reviews again]
Code reviewer: ✅ Approved

[Mark Task 2 complete]

...

[After all tasks]
[Dispatch final code-reviewer]
Final reviewer: All requirements met, ready to merge

Done!

Advantages

vs. Manual execution:

•Delegated implementation passes follow TDD naturally
•Fresh context per task (no confusion)
•Parallel-safe (independent delegated passes do not interfere)
•Each delegated pass can ask questions (before and during work)

vs. Executing Plans:

•Same session (no handoff)
•Continuous progress (no waiting)
•Review checkpoints automatic

Efficiency gains:

•No file reading overhead (controller provides full text)
•Controller curates exactly what context is needed
•Each delegated pass gets complete information upfront
•Questions surfaced before work begins (not after)

Quality gates:

•Self-review catches issues before handoff
•Two-stage review: spec compliance, then code quality
•Review loops ensure fixes actually work
•Spec compliance prevents over/under-building
•Code quality ensures implementation is well-built

Cost:

•More delegated passes (implementer + 2 reviewers per task)
•Controller does more prep work (extracting all tasks upfront)
•Review loops add iterations
•But catches issues early (cheaper than debugging later)

Red Flags

Never:

•Start implementation on main/master branch without explicit user consent
•Skip reviews (spec compliance OR code quality)
•Proceed with unfixed issues
•Dispatch multiple implementation delegated workers in parallel (conflicts)
•Make delegated worker read plan file (provide full text instead)
•Skip scene-setting context (delegated worker needs to understand where task fits)
•Ignore delegated worker questions (answer before letting them proceed)
•Accept "close enough" on spec compliance (spec reviewer found issues = not done)
•Skip review loops (reviewer found issues = implementer fixes = review again)
•Let implementer self-review replace actual review (both are needed)
•Start code quality review before spec compliance is ✅ (wrong order)
•Move to next task while either review has open issues

If delegated worker asks questions:

•Answer clearly and completely
•Provide additional context if needed
•Don't rush them into implementation

If reviewer finds issues:

•Implementer (same delegated worker) fixes them
•Reviewer reviews again
•Repeat until approved
•Don't skip the re-review

If delegated worker fails task:

•Dispatch fix delegated worker with specific instructions
•Don't try to fix manually (context pollution)

Integration

Required workflow skills:

•superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
•superpowers:writing-plans - Creates the plan this skill executes
•superpowers:requesting-code-review - Code review template for reviewer delegated workers
•superpowers:finishing-a-development-branch - Complete development after all tasks

Delegated workers should use:

•superpowers:test-driven-development - Delegated workers follow TDD for each task

Alternative workflow:

•superpowers:executing-plans - Use for parallel session instead of same-session execution