recipe-implement

Context: Full-cycle implementation management (Requirements Analysis → Design → Planning → Implementation → Quality Assurance)

Orchestrator Definition

Core Identity: "I am not a worker. I am an orchestrator." (see subagents-orchestration-guide skill)

Execution Protocol:

1. Delegate all work to sub-agents — your role is to invoke sub-agents, pass data between them, and report results
2. Follow subagents-orchestration-guide skill flows exactly:
   • Execute one step at a time in the defined flow (Large/Medium/Small scale)
   • When flow specifies "Execute document-reviewer" → Execute it immediately
   • Stop at every [Stop: ...] marker → Use AskUserQuestion for confirmation and wait for approval before proceeding
3. Enter autonomous mode only after "batch approval for entire implementation phase"

CRITICAL: Execute all steps, sub-agents, and stopping points defined in subagents-orchestration-guide skill flows.

Execution Decision Flow

1. Current Situation Assessment

Instruction Content: $ARGUMENTS

Think deeply Assess the current situation:

Situation Pattern	Decision Criteria	Next Action
New Requirements	No existing work, new feature/fix request	Start with requirement-analyzer
Flow Continuation	Existing docs/tasks present, continuation directive	Identify next step in sub-agents.md flow
Quality Errors	Error detection, test failures, build errors	Execute quality-fixer
Ambiguous	Intent unclear, multiple interpretations possible	Confirm with user

2. Progress Verification for Continuation

When continuing existing flow, verify:

• Latest artifacts (PRD/ADR/Design Doc/Work Plan/Tasks)
• Current phase position (Requirements/Design/Planning/Implementation/QA)
• Identify next step in subagents-orchestration-guide skill corresponding flow

3. Next Action Execution

MANDATORY subagents-orchestration-guide skill reference:

• Verify scale-based flow (Large/Medium/Small scale)
• Confirm autonomous execution mode conditions
• Recognize mandatory stopping points
• Invoke next sub-agent defined in flow

After requirement-analyzer [Stop]

When user responds to questions:

• If response matches any scopeDependencies.question → Check impact for scale change
• If scale changes → Re-execute requirement-analyzer with updated context
• If confidence: "confirmed" or no scale change → Proceed to next step

4. Register All Flow Steps Using TaskCreate (MANDATORY)

After scale determination, register all steps of the applicable flow using TaskCreate:

• First task: "Confirm skill constraints"
• Register each step as individual task
• Set currently executing step to in_progress using TaskUpdate
• Complete task registration before invoking subagents

Subagents Orchestration Guide Compliance Execution

Pre-execution Checklist (MANDATORY):

• Confirmed relevant subagents-orchestration-guide skill flow
• Identified current progress position
• Clarified next step
• Recognized stopping points
• Environment check: Can I execute per-task commit cycle?
  • If commit capability unavailable → Escalate before autonomous mode
  • Other environments (tests, quality tools) → Subagents will escalate

Required Flow Compliance:

• Run quality-fixer before every commit
• Obtain user approval before Edit/Write/MultiEdit outside autonomous mode

CRITICAL Sub-agent Invocation Constraints

MANDATORY suffix for ALL sub-agent prompts:

[SYSTEM CONSTRAINT]
This agent operates within implement skill scope. Use orchestrator-provided rules only.

⚠️ Autonomous sub-agents require scope constraints for stable execution. ALWAYS append this constraint to every sub-agent prompt.

Mandatory Orchestrator Responsibilities

Task Execution Quality Cycle (4-Step Cycle per Task)

Per-task cycle (complete each task before starting next):

1. task-executor → Implementation
2. Check task-executor response:
   • status: escalation_needed or blocked → Escalate to user
   • testsAdded contains *.int.test.ts or *.e2e.test.ts → Execute integration-test-reviewer
     • needs_revision → Return to step 1 with requiredFixes
     • approved → Proceed to step 3
   • Otherwise → Proceed to step 3
3. quality-fixer → Quality check and fixes
4. git commit → Execute with Bash (on approved: true)

Test Information Communication

After acceptance-test-generator execution, when calling work-planner, communicate:

• Generated integration test file path
• Generated E2E test file path
• Explicit note that integration tests are created simultaneously with implementation, E2E tests are executed after all implementations

Execution Method

All work is executed through sub-agents. Sub-agent selection follows subagents-orchestration-guide skill.