compound-v

Compound V

"You don't tell people you're injecting them with Compound V. You just hand them the spec and watch them go faster." — internal Vought memo, probably

Compound V is a transparent interceptor that sits between Superpowers phases AND, as of v1.0, a lightweight execution orchestrator — the orchestrated pipeline is now the default execution path. You don't invoke it directly — it fires automatically at four transitions:

Stage −1 — Pre-Evaluation (v2.9). Before Trigger 0 even offers recon, a fast, cheap Pre-Evaluation scores the change request on two separate axes (difficulty ⊥ impact) from deterministic tiered evidence and — only when a change is provably trivial and low-impact — OFFERS a proportionate fast-path that collapses the full pipeline into one scope-gated implementer plus one combined SPEC+QUALITY Opus review. Everything else routes to the full pipeline below. It uses no raw LLM magnitude, never auto-routes (it only ever offers), and fails closed on any ambiguity, sensitive-path touch, or shared-token/a11y surface. A sibling post-diff re-classifier can still ESCALATE an accepted fast-path back to the full pipeline before merge (minting a new run-id, never mutating the frozen manifest). See phase-preeval.md; the offer/accept decision is captured as a thin ADR via /v:adr.

1. Before brainstorming begins → offers a gated pre-brainstorm recon (Trigger 0): a bounded deep-research/WebSearch pass that writes an anti-anchoring recon doc to docs/superpowers/recon/ — evidence to widen the brainstorm's questions, never a conclusion to converge on. See phase-0-recon.md.
2. After brainstorming, before writing-plans → injects THREE parallel pre-flights:
   • Phase 1A: Code-Archaeology — the technical reality of the existing code
   • Phase 1B: Domain-Expert Advisor — the product/domain reality (web-searched if needed, knowledge-base persisted)
   • Phase 1C: Library/Doc Validator — library currency via Context7 MCP (stale deps, abandoned libs, outdated API signatures)
3. Inside writing-plans → enforces Disjoint File Partitioning and materializes a manifest.yaml (the machine-readable contract) so tasks can run in parallel
4. At execution → runs the orchestration pipeline: dispatch each manifested job to its backend (Claude subagent on Opus by default, Sonnet only for clearly junior mechanical tasks, or a headless Codex worker for large isolated builds — see phase-3-parallel-opus-dispatch.md), enforce file-scope with a git diff gate after every job, collect canonical job_results, review against the spec's Acceptance Criteria, and update outcome memory. Runs autonomously with guardrails and is crash-resumable via state.json.

The unified pipeline (orchestrator-as-default):

★ PRE-EVAL (v2.9)  two-axis score → OFFER fast-path | FULL_PIPELINE   (fail-closed; never auto-routes)
   │  └─ accepted fast-path ─► materialize 1-job manifest ─► implement ─► scope gate
   │        ─► post-diff re-classify (ESCALATE → full pipeline, new run-id) ─► review ─► merge
   ▼  (full pipeline)
★ RECON (gated)  docs/superpowers/recon/YYYY-MM-DD-<topic>.md   (Trigger 0 — skip: plumbing | KB hit | off)
   ▼
brainstorm ─► spec (carries feature-level Acceptance Criteria)
   ▼ auto-fire
[1A archaeology ∥ 1B domain ∥ 1C library] ─► 3 audits   (🔴 critical finding → HALT)
   ▼ writing-plans + Phase 2 Partition Map
★ MANIFEST  docs/superpowers/execution/<run-id>/manifest.yaml   (partition FAIL → HALT)
   ▼ DISPATCH — batched Task (4–6) ∥ Codex via backend-launcher; per-job worktree|direct
★ COLLECT + SCOPE GATE  git diff --name-only vs write_allowed   (violation → BLOCKED → HALT)
   ▼ REVIEW  spec + quality + final integration (Opus), AC-gated   (unfixable ISSUES → HALT)
   ▼ MEMORY  append task-outcomes.jsonl + routing-lessons.md
   ▼ finishing-a-development-branch
                          state.json updated after every phase ──► /v:status · /v:resume