Fix It
Plan and implement a repair from diagnosis — smallest real fix, evidence matched to regime.
What it is
Section titled “What it is”Turn troubleshoot-app / diagnose-bug (or clear breakage evidence) into an implementation-ready plan, then execute when approved. Bridge diagnose → plan → check-readiness → merge-it.
Why it works
Section titled “Why it works”Small, tested repairs beat speculative rewrites (DORA small batches). The repair oracle comes from the quality trace (DocSlime + lightweight BDD / contracts); proof shape follows quality regimes. A bug remains a bug whether the interest is labeled development, data, craft, or framing debt (Bugs & debt).
When to use it
Section titled “When to use it”After a diagnosis (or clear failing contract) when you need a decision-complete plan — not for pure refactors (refactor-it) or greenfield without a broken promise.
- Name regime A/B/C; lock Use Existing / Refine / Create New for the contract
- Prefer smallest fix that restores the scenario; map scenario → evidence
- One write owner; ask before mutating unless already ordered to implement
- Hide behavior change inside “refactor”
- Invent a parallel Definition of Done when DocSlime/issue BDD exists
- Spawn overlapping agents to “go faster”
Related concepts
Section titled “Related concepts”03-smallest-next-step, 04-evidence-over-vibes, 11-quality-regimes, 12-bugs-and-debt, 13-quality-trace
Further reading
Section titled “Further reading”- Quality regimes (handbook)
- Quality trace (handbook)
- DORA — Working in small batches
- Martin Fowler — Refactoring
- Practical Test Pyramid
See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”fix-it