What problem does it solve?
It helps you stop drifting by forcing your proposed plan to be challenged against the project’s established domain language and documented decisions, reducing vague or conflicting terminology before execution.
Core Features & Use Cases
- Relentless plan interrogation: Interview-driven questioning that walks the design tree branch-by-branch until shared understanding is reached.
- Terminology sharpening: Detects glossary conflicts and replaces fuzzy or overloaded terms with precise canonical ones.
- Scenario-based boundary testing: Probes edge cases with concrete invented scenarios to clarify relationships and constraints.
- Code cross-referencing: Checks whether the user’s stated behavior matches what the code actually does, and surfaces contradictions.
- Inline documentation updates: Updates CONTEXT.md in the project’s documented format as terms become resolved.
- Sparing ADR offers: Proposes adding ADRs only when decisions meet the project’s criteria for being hard to reverse, surprising without context, and involving real trade-offs.
Quick Start
Ask the skill to stress-test your current plan by walking it down one branch at a time while it challenges terminology and validates assumptions against the codebase and existing docs.