Modes
Feature

Feature Mode

The default mode. Full pipeline from planning to shipping, with adversarial challengers at the plan/spec boundaries and a spec-compliance gate before code review.

Trigger

@buildcrew Add user dashboard
@buildcrew Implement dark mode, 2 iterations

Pipeline

Planner(01) → Plan-Challenger(01.5) → Designer(02) → Spec-Challenger(02.5) → Developer(03)

→ [ QA Tester(04) ∥ Browser QA(05) ∥ Spec-Verifier(03.5) ]   ← parallel verification fleet

→ Reviewer(06) → Coherence-Auditor(last)
  • Challengers attack the plan/spec before downstream work starts. Verdicts: APPROVED → proceed, REVISE → re-run upstream agent (max 2 cycles), REJECT → escalate to user.
  • Verification fleet (v1.15) — qa-tester, browser-qa, and spec-verifier are all read-only and independent, so the orchestrator dispatches them concurrently in a single message. Any failure → one developer fix pass from the merged findings → only the failed members re-run (max 2 cycles). Wall-clock drops to the slowest member instead of the sum.
  • Spec-Verifier checks every acceptance criterion (AC-1 …) against the actual implementation with file:line evidence. Reviewer runs only after PASS. Disputed criteria can be settled by a 3-voter majority (SCOPE: AC-n).
  • Parallel review lenses — large or security-sensitive diffs get 4 concurrent reviewer instances (LENS: security/performance/testing/maintainability, report-only); small diffs keep the single auto-fixing reviewer.
  • Design panel (opt-in) — @buildcrew {task}, 3 designs generates candidates from distinct angles in parallel; spec-challenger judges and grafts runner-up ideas into the winner.
  • Coherence-Auditor runs once at the very end: parses Handoff Records, cross-checks source code, outputs a Coordination Score 0-100%.
  • Safety rule: only read-only agents parallelize — anything that writes (developer, full reviewer) always runs alone.

Quality Gate

After QA + Browser QA + Spec-Verify + Review:

  • All PASS → suggest Ship Mode
  • FAIL → route back to responsible agent (UI → designer, code → developer, spec → planner)
  • Max iterations reached → ship with known issues documented

Output Files

.claude/pipeline/{feature}/
├── 01-plan.md
├── 01.5-plan-critique.md
├── 02-references.md
├── 02-design.md
├── 02.5-spec-critique.md
├── 03-dev-notes.md
├── 04-qa-report.md
├── 05-browser-qa.md
├── 03.5-spec-verification.md
├── 06-review.md
├── 07-ship.md (after Ship Mode)
└── coherence-report.md
ModesProject Audit