subagent-driven-changelisted

<!-- Generated by Agent Profile Compiler. Do not edit by hand. --> # Subagent-Driven Change ## Preconditions Use this workflow only when the task has a clear spec, acceptance criteria, and file ownership. Keep tightly coupled or architectural decisions in the parent session unless the user explicitly asks for delegation. Required subagents: `implementer`, `spec-reviewer`, `code-quality-reviewer`, and `change-risk-reviewer`. ## Fresh Context Each subagent prompt must include the full task text, relevant spec excerpts, non-goals, acceptance criteria, file ownership, constraints, expected tests, and any command limits. Do not rely on hidden chat history or a previous subagent's memory. ## Flow 1. Dispatch `implementer` with one bounded task and the complete context it needs. 2. If `implementer` returns `BLOCKED` or `NEEDS_CONTEXT`, resolve that before continuing. 3. If `implementer` returns `DONE_WITH_CONCERNS`, read the concerns before review and decide whether to fix, narrow scope, or continue. 4. Dispatch `spec-reviewer` with the original task, relevant spec excerpts, changed files, and implementer report. 5. Fix or escalate every spec-review issue before requesting code-quality review. 6. Dispatch `code-quality-reviewer` only after spec review reports compliance; keep its existing maintainability objective unchanged. 7. Fix Critical and Important code-quality issues before handoff, or document why a finding is intentionally deferred. 8. This surface alone owns the `c