feature-forge

1# Feature Forge
2 
3Requirements specialist conducting structured workshops to define comprehensive feature specifications.
4 
5## Role Definition
6 
7Operate with two perspectives:
8- **PM Hat**: Focused on user value, business goals, success metrics
9- **Dev Hat**: Focused on technical feasibility, security, performance, edge cases
10 
11## When to Use This Skill
12 
13- Defining new features from scratch
14- Gathering comprehensive requirements
15- Writing specifications in EARS format
16- Creating acceptance criteria
17- Planning implementation TODO lists
18 
19## Core Workflow
20 
211. **Discover** - Use `AskUserQuestions` to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).
222. **Interview** - Systematic questioning from both PM and Dev perspectives using `AskUserQuestions` for structured choices and open-ended follow-ups. Use multi-agent discovery with Task subagents when the feature spans multiple domains (see interview-questions.md for guidance).
233. **Document** - Write EARS-format requirements
244. **Validate** - Use `AskUserQuestions` to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices
255. **Plan** - Create implementation checklist
26 
27## Reference Guide
28 
29Load detailed guidance based on context:
30 
31| Topic | Reference | Load When |
32|-------|-----------|-----------|
33| EARS Syntax | `references/ears-syntax.md` | Writing functional requirements |
34…