3-handoff

You are now entering Phase 3: Execution Handoff.

State Check

See _protocols/_shared.md → State Check Template. Required artifacts: REQUIREMENTS.md + DESIGN.md. If missing DESIGN.md: "No design found. Run /qf:2-design first." If missing REQUIREMENTS.md: "No requirements found. Run /qf:1-brainstorm <idea> first."

Milestone Detection

See _protocols/_shared.md → Milestone Detection. Target artifact: ROADMAP.md. Read REQUIREMENTS.md (project-level) + DESIGN.md (milestone-level) + CONTEXT.md (if exists).

GOTCHAs Review (before generating artifacts)

See _protocols/_shared.md → GOTCHAs System → Review Protocol. Read both plans/GOTCHAS.md (global) and plans/{feature-slug}/GOTCHAS.md (feature) if they exist. Filter by tags matching this milestone's requirements. If relevant gotchas found: inject their rules as > ⚠️ GOTCHA [global/feature]: warnings in the appropriate ROADMAP.md phases.

Discipline Protocols (injected into implementation)

When generating ROADMAP.md, inject these requirements into EVERY implementation phase:

All implementation phases MUST follow TDD (see _tdd-enforcement.md). All application code MUST use structured logging (see _structured-logging.md). All phase transitions MUST have verification evidence (see _verification-gates.md).

Each ROADMAP.md implementation phase must include:

1. TDD mandate: "Follow RED-GREEN-REFACTOR. Save evidence to .evidence/tdd/"
2. Logging mandate: "Implement structured logging per _structured-logging.md"
3. Verification mandate: "Save phase gate evidence to .evidence/verification/"

Feature Memory — Context Loading

Before generating artifacts, load the feature's FMU via @mention (see _context-memory.md). If no FMU exists for this feature, create one in .memory/{feature-slug}/ with CONTEXT.md.

Output Files

Generate to ./plans/{feature-slug}/:

1. REQUIREMENTS.md (project-level) — UPDATE the existing draft:

   • Add requirement IDs (REQ-001, REQ-002, ...)
   • Add v1/v2 priority tags
   • Add acceptance criteria per requirement
   • Only finalize requirements tagged for current milestone [M{N}]
   • Change status for current milestone's requirements from DRAFT to FINAL
   • Leave future milestone requirements as DRAFT

2. CONTEXT.md (project-level) — append locked decisions from this milestone

3. OPEN_QUESTIONS.md (project-level) — append/update open items

Generate to ./plans/{feature-slug}/milestone-{N}/:

4. ROADMAP.md — phases with clear deliverable + done criteria per phase

Code Quality Mandates

See _protocols/_shared.md → Code Quality Mandates. Inject into every ROADMAP phase.

Task Granularity Check (auto — after ROADMAP generation)

No ROADMAP phase should produce >150 LOC or cover >3 REQ-IDs. Large phases overwhelm agent context and reduce review quality.

For each phase in the generated ROADMAP.md:

1. Count REQ-IDs assigned to this phase
2. Estimate LOC from MODULES.md file targets:
   • CRUD endpoint: ~40 LOC
   • Service with business logic: ~80 LOC
   • Complex module (auth, realtime, state machine): ~120 LOC
3. If REQ-IDs > 3 OR estimated LOC > 150:
   • Auto-split into sub-tasks: Phase {N}.1, {N}.2, {N}.3...
   • Each sub-task: 1-2 REQ-IDs, single module focus
   • Each sub-task must be independently testable (own TDD cycle)
   • Use MODULES.md boundaries as natural split points
4. Update ROADMAP.md with sub-tasks replacing the original phase
5. Log: "Phase {N} split into {M} sub-tasks (estimated {LOC} LOC, {R} REQ-IDs)"

Split rules:

• Sub-tasks inherit the parent phase's priority and done criteria
• Sub-tasks get sequential numbering: Phase 2.1, 2.2, 2.3
• Each sub-task lists its specific REQ-IDs and target files
• Dev agents receive sub-tasks as their scoped phases (no change to dev-teammate.md)

Skip condition: If ALL phases are already ≤150 LOC and ≤3 REQ-IDs, skip silently.

Review Gate

Autopilot mode: See _protocols/_autopilot.md → Phase 3 — Handoff.

Normal mode:

1. Read back CONTEXT.md locked decisions to the user
2. Ask: "Anything missing or incorrect? Type CONFIRM to finalize."

Agent waits. Does nothing until user types CONFIRM.

Output Rule

See _protocols/_shared.md → Output Rule.

Execution Gate

After CONFIRM, check REQUIREMENTS.md for team_mode and team_composition settings.

If team_mode: true:

1. Read team_composition from REQUIREMENTS.md

2. Map ROADMAP.md phases to team roles based on file ownership boundaries

3. Present the execution plan:

   "Team mode enabled. Here's the execution plan:

   Role	Type	Phases	File Ownership
   lead	Orchestrator	Coordinate all	Main session
   domain-engineer	Architect (recommended)	Before devs	plans/{slug}/milestone-{N}/design/
   dev-backend	Developer	Phase 1, 3	src/api/*, src/models/*
   dev-frontend	Developer	Phase 2, 4	src/components/*, src/pages/*
   tech-lead	Reviewer (optional)	After devs	Read-only on all dev files
   tester	Tester	After review	tests/*

   Pipeline: domain-engineer designs -> devs implement (parallel) -> [optional] tech-lead reviews -> tester tests

   Options:

   • SHIP — Launch team pipeline (/qf:cook)
   • REFINE — Adjust team composition"

Autopilot shortcut: See _protocols/_autopilot.md → Phase 3. Auto-SHIP, skip REFINE.

4. On REFINE:

   • Ask: "What would you like to change?" and accept freeform instructions
   • Lead, PM, and Tester roles cannot be removed
   • Apply changes, re-display updated table, ask again: SHIP / REFINE
   • Update team_composition in REQUIREMENTS.md after each refinement
   • Loop until user types SHIP

5. On SHIP:

   • Auto-invoke /qf:cook — cook.md is the single source of truth for pipeline orchestration
   • Cook reads team_composition from REQUIREMENTS.md and executes the full pipeline

If team_mode: false (or not set):

• Set team_mode: true automatically — multi-agent is the only mode
• Auto-compose minimal team: 1 dev + tester + pm
• Present team table and proceed to SHIP/REFINE gate

Progress Logging

See _protocols/_shared.md → Progress Tracking. Append Phase 3 row to plans/{feature-slug}/PROGRESS.md. Key decisions to log: execution mode (SHIP), ROADMAP phase count, team composition summary.

Next Step

Tell user: "Phase 3 complete for milestone-{N}. Artifacts saved to ./plans/{feature-slug}/milestone-{N}/."

Then suggest next command based on mode:

If team_mode: true:

**Next:** `/qf:cook` — Launch team pipeline (domain-engineer -> devs -> tech-lead -> tester -> PM)
  => Skip? You can implement manually (Solo mode) — run `/qf:4-verify` after implementing
  => Also available: `/qf:status` (check status), `/qf:status save` (save context)

Solo mode has been removed. All execution runs through /qf:cook.