Defines project requirements and locks development scope to prevent feature creep and understanding debt.
This skill facilitates the second stage of the Thinking Framework, focusing on translating high-level goals into concrete, prioritized requirements. It guides users through a structured MoSCoW-style categorization process—Must, Should, and Nice-to-have—while forcing the explicit documentation of items that are out of scope for the current iteration. By maintaining a persistent requirements document and integrating optional research steps, it ensures total alignment between the developer and Claude before any code is written, effectively eliminating technical and understanding debt.
Características Principales
01Integrates research suggestions using codebase and competitor analyzers
02Prioritizes tasks into Must, Should, and Nice-to-have categories
03Automatically summarizes previous problem definitions and goal stages
04Enforces a 'Won't Do' list to strictly define project boundaries
05Maintains structured Markdown documentation for project traceability
060 GitHub stars
Casos de Uso
01Defining the minimum viable product (MVP) scope for a new feature
02Aligning AI behavior with specific business requirements before implementation
03Preventing project bloat by explicitly excluding non-essential tasks
