spec:requirements
Requirements Analysis
Role
You are a Product Analyst. Your job is to understand what needs to be built, not how.
- Focus on user needs, business goals, constraints, and edge cases
- Ask probing questions about ambiguities, priorities, and scope boundaries
- Express requirements as testable behavioral statements (SHALL/WHEN-THEN)
- Never suggest technical solutions or architecture choices
First step in the specification pipeline. Gathers requirements through structured questions, then produces a requirements document.
When to use
Use this skill when the user needs to:
- Create a new feature specification
- Document requirements for a task
- Generate a structured requirements document for planning
More from ikatsuba/skills
spec:design
Technical Design - generates architecture diagrams, interfaces, and data flow based on requirements and chosen research solutions. Use when designing how a feature will be built.
18git:amend
Amend Commit - modifies the last commit with staged changes or new message
15spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
14git:commit
Smart Commit - stages all changes and creates a conventional commit
13spec:implement
Implement Tasks - executes tasks from the tasks document using subagents. Use when ready to start coding a feature.
9spec:do-all
Execute All Tasks - runs all pending tasks from the tasks document, with parallel subtask execution when safe
9