Pizza1
Justify by correctness, never by convention. Use when a design, fix, API, macro, library surface, hook message, or naming decision is defended by 'it's what the codebase does', 'the established pattern', 'the canonical lane does it', 'more ergonomic', 'less churn', 'already wired', or 'out of scope to change'. Prevalence is not evidence. Re-derive from correctness, name the bug the alternative ca…
Grill With Docs Requiem
A high-judgment design interview that sharpens plans in useful batches and records settled domain language and ADRs as the conversation progresses.
Antimatter Code Quality Review
Total annihilation: no finding survives unless it survives refutation. An unusually strict maintainability and structural-quality audit of a diff — abstraction quality, cohesion, type/boundary cleanliness, duplication, control-flow tangles, and correct-by-construction opportunities. Use for a deep code-quality audit, a harsh pre-merge review, or to determine what structural change makes a class o…
To Issues
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices, then wire the blocked-by/parent relationships into native GitHub sub-issues and dependencies so the tracker renders the real tree (not just prose). Use when converting a plan into issues, creating implementation tickets, or breaking work into slices.