Loading...
Loading...
Found 18 Skills
Create, update, validate, or analyze a PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD.
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
Use when you need to move a feature from a vague concept to an executable development plan, and complete requirement analysis, task breakdown, and status tracking within the same plan document.
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.
Produce a high-level technical design with architecture diagram, component responsibilities, data flow, and test scenario map. Use after the product intent specification is approved.
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Triggers on /brainstorm command, when exploring ideas before planning, when user describes a vague goal or feature request, or when design decisions need collaborative exploration. Explores user intent, requirements and design before implementation.