Pipeline

Feature Pipeline

Each feature generates a full document chain in .claude/pipeline/.

Document Chain

.claude/pipeline/{feature}/
├── 01-plan.md           Planner: requirements + 4-lens scores
├── 02-design.md         Designer: design decisions + specs
├── 03-dev-notes.md      Developer: implementation + 6-question analysis + self-review
├── 04-qa-report.md      QA Tester: test map + acceptance criteria verification
├── 05-browser-qa.md     Browser QA: health score (0-100) + screenshots
├── 06-review.md         Reviewer: 4-specialist findings + auto-fixes
└── 07-ship.md           Shipper: PR URL + release notes

Standalone Mode Outputs

.claude/pipeline/project-audit/     00-backlog.md + iterations/
.claude/pipeline/browser-qa/        browser-qa-report.md
.claude/pipeline/security-audit/    security-audit.md
.claude/pipeline/debug-{bug}/       investigation.md
.claude/pipeline/health/            health-report.md
.claude/pipeline/canary/            canary-report.md
.claude/pipeline/review/            review-report.md
.claude/pipeline/qa-audit/          qa-report.md
.claude/pipeline/think/             design-doc.md
.claude/pipeline/arch-review/       architecture-review.md
.claude/pipeline/design-review/     design-review.md

Handoff Protocol

Each agent:

  1. Reads the previous agent's output file
  2. Does its work
  3. Writes its own output file
  4. The next agent reads that file

Every decision is documented. Every handoff is traceable.

Second Opinion

After any mode completes, the orchestrator offers an independent review:

  • Codex CLI available: different AI model challenges the work
  • No Codex: fresh Claude subagent with no session memory

The user decides what to act on.

TemplatesArchitecture