What problem does it solve?
This Skill ensures rough ideas for new features, architectural decisions, or complex system changes are converted into concrete, approval-ready plans before any code, scaffolding, or pseudo-code is produced. It reduces rework and risky implementations by forcing explicit tradeoff analysis, test-path enumeration, and rollback considerations up front.
Core Features & Use Cases
- Multiple approach evaluation: Produce 2–3 distinct approaches with tradeoffs and a single recommended option, including a minimal option.
- Attack-angle validation: Validate recommendations against dependency failure, scale explosion, rollback cost, and premise collapse, refining or discarding approaches that fail these attacks.
- Operational checklist & diagrams: Require explicit test paths, listing of required API keys and third-party dependencies, and ASCII diagrams for multi-component interactions when needed.
- Use Case: Use before major feature launches, service boundary changes, or cross-component integrations to obtain a verified plan and explicit approval before implementation.
Quick Start
Run /think with a concise description of the feature or architecture decision you want validated.