What problem does it solve?
Defining new or modified full-stack features often leads to incomplete, ambiguous requirements that cause development rework, cross-team misalignment, and missed edge cases. This skill eliminates those unknowns by guiding you through a structured, layer-by-layer questioning process to capture every functional detail needed for successful implementation.
Core Features & Use Cases
- Codebase-First Research: Automatically explores existing frontend, backend, data, and integration layers before asking questions to avoid redundant clarifications.
- Structured Guided Questioning: Asks one targeted question at a time with actionable options and recommendations, covering UI behavior, API contracts, data models, business rules, permissions, and edge cases.
- Standardized Documentation: Structures finalized requirements into coherent, testable markdown files saved to the docs/requirements folder, tailored to simple, medium, or complex feature scopes.
- Use Case: For example, if you want to add a real-time match history feature to the Bulls and Cows PvP game, this skill will guide you through clarifying UI elements, required API endpoints, database schema changes, and scoring business rules before any development work begins.
Quick Start
Use the shaping-requirements skill to define the functional requirements for adding a public match lobby feature to the Bulls and Cows game.
