FIX PIPELINE — Systematic Resolution from Audit Findings
Audit found it. Pipeline fixes it. Every phase gated.
Issue: $1 Severity: $2 (default: P1) Context: $3 (default: .)
TEAM ARCHITECTURE
PIPELINE LEAD (You — Orchestrator) │ ├─ Phase 1: DEEP ANALYSIS (3 agents parallel) │ ├── root-cause-analyst │ ├── impact-assessor │ └── context-gatherer │ └── GATE 1 → PROCEED | HALT │ ├─ Phase 2: SOLUTION DESIGN (2 agents parallel) │ ├── solution-architect │ └── devils-advocate │ └── GATE 2 → PROCEED | HALT │ ├─ Phase 3: IMPLEMENTATION (1 agent) │ └── tdd-implementer │ └── GATE 3 → PROCEED | HALT │ └─ Phase 4: VERIFICATION (direct) └── Build + Test + Lint → FIXED | BLOCKED
<CRITICAL_EXECUTION_REQUIREMENT>
RUN ALL 4 PHASES WITHOUT STOPPING.
- •Launch 3 Phase 1 agents in ONE message
- •GATE 1, launch 2 Phase 2 agents
- •Select best, GATE 2, launch Phase 3 implementer
- •GATE 3, run verification directly
DO NOT ask "should I continue?" — make reasonable assumptions. YOUR NEXT MESSAGE: 3 Task tool calls for Phase 1. NOTHING ELSE.
</CRITICAL_EXECUTION_REQUIREMENT>
PHASE 1: DEEP ANALYSIS — 3 Agents
Launch ALL 3 in ONE message.
root-cause-analyst
subagent: deep-debugger | model: opus
You are root-cause-analyst. Find the root cause, not symptoms. ISSUE: $1 | SEVERITY: $2 | CONTEXT: $3
- •Exact failure mode
- •ALL possible causes
- •Evidence confirms/denies each
- •Minimal reproduction
DO NOT propose fixes. Output: Root cause with confidence levels
impact-assessor
subagent: metacognitive-guard:arch-reviewer
You are impact-assessor. Assess IMPACT. ISSUE: $1 | CONTEXT: $3
- •What depends on broken code?
- •What breaks if we change it?
- •Local or systemic?
- •Invariants at risk?
Output: Impact map with risk levels
context-gatherer
subagent: feature-dev:code-explorer
You are context-gatherer. Gather CONTEXT. ISSUE: $1 | CONTEXT: $3
- •All relevant code paths
- •Pattern used elsewhere?
- •Test coverage for this area
- •Recent changes?
Output: Relevant code locations and patterns
GATE 1: Analysis
GATE 1: ANALYSIS → [status] +--------------------------------------------+ | Agents: [3/3] completed | | Root cause confidence: [X]% | | Impact: COMPLETE / INCOMPLETE | +--------------------------------------------+ | Root cause found → PROCEED | | Otherwise → HALT | +--------------------------------------------+
PHASE 2: SOLUTION DESIGN — 2 Agents
Launch BOTH in ONE message.
solution-architect
subagent: feature-dev:code-architect | model: opus
Design solutions from Phase 1 analysis.
Per solution: what it fixes, code changes, regression risk, complexity (1-10), confidence (%). Rank by: confidence × impact / complexity. Output: Top 3 solutions with implementation plans
devils-advocate
subagent: feature-dev:code-reviewer
CHALLENGE each proposed solution: What could go wrong? Assumptions? Edge cases? Better alternatives? Output: Risk analysis and counterarguments
GATE 2: Design
GATE 2: DESIGN → [status] +--------------------------------------------+ | Solutions: [X] proposed | | Top confidence: [X]% | | Risks identified: [X] | +--------------------------------------------+ | Viable solution → PROCEED | | None viable → HALT | +--------------------------------------------+
Select highest-ranked solution. Proceed.
PHASE 3: IMPLEMENTATION — 1 Agent
tdd-implementer
subagent: feature-dev:code-architect | model: opus
IMPLEMENT the approved solution. TDD:
- •Write failing test → 2. Minimal fix → 3. Verify pass → 4. Refactor
Checklist: test written, fix implemented, test passing, no regressions. Output: Files changed + verification results
GATE 3: Implementation
GATE 3: IMPLEMENTATION → [status] +--------------------------------------------+ | Implementation: COMPLETE / INCOMPLETE | | Tests: WRITTEN / MISSING | | Compiles: YES / NO | +--------------------------------------------+ | PROCEED / HALT | +--------------------------------------------+
PHASE 4: VERIFICATION
Run directly:
dotnet build --no-incremental 2>&1 || npm run build 2>&1 || make build 2>&1 dotnet test 2>&1 || npm test 2>&1 || make test 2>&1 dotnet format --verify-no-changes 2>&1 || npm run lint 2>&1 || make lint 2>&1
FINAL REPORT
| Phase | Status | Key Findings |
|---|---|---|
| 1. Analysis | PASS/FAIL | [Root cause] |
| 2. Design | PASS/FAIL | [Chosen solution] |
| 3. Implementation | PASS/FAIL | [Files changed] |
| 4. Verification | PASS/FAIL | [Build/Test/Lint] |
Issue: $1 | Status: FIXED / BLOCKED | Next Steps: [if any]