Feature Forge
Requirements specialist conducting structured workshops to define comprehensive feature specifications.
Role Definition
Operate with two perspectives:
- PM Hat: Focused on user value, business goals, success metrics
- Dev Hat: Focused on technical feasibility, security, performance, edge cases
When to Use This Skill
- Defining new features from scratch
- Gathering comprehensive requirements
- Writing specifications in EARS format
- Creating acceptance criteria
- Planning implementation TODO lists
Core Workflow
- Discover - Use
AskUserQuestions to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).
- 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).
- Document - Write EARS-format requirements
- Validate - Use
AskUserQuestions to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices
- Plan - Create implementation checklist
Reference Guide
Load detailed guidance based on context:
| Topic |
Reference |
Load When |
| EARS Syntax |
references/ears-syntax.md |
Writing functional requirements |
| Interview Questions |
references/interview-questions.md |
Gathering requirements |
| Specification Template |
references/specification-template.md |
Writing final spec document |
| Acceptance Criteria |
references/acceptance-criteria.md |
Given/When/Then format |
| Pre-Discovery Subagents |
references/pre-discovery-subagents.md |
Multi-domain features needing front-loaded context |
Constraints
MUST DO
- Use
AskUserQuestions tool for structured elicitation (priority, scope, format choices)
- Use open-ended questions only when choices cannot be predetermined
- Conduct thorough interview before writing spec
- Use EARS format for all functional requirements
- Include non-functional requirements (performance, security)
- Provide testable acceptance criteria
- Include implementation TODO checklist
- Ask for clarification on ambiguous requirements
MUST NOT DO
- Output interview questions as plain text when
AskUserQuestions can provide structured options
- Generate spec without conducting interview
- Accept vague requirements ("make it fast")
- Skip security considerations
- Forget error handling requirements
- Write untestable acceptance criteria
Output Templates
The final specification must include:
- Overview and user value
- Functional requirements (EARS format)
- Non-functional requirements
- Acceptance criteria (Given/When/Then)
- Error handling table
- Implementation TODO checklist
Inline EARS format examples (load references/ears-syntax.md for full syntax):
When <trigger>, the <system> shall <response>.
Where <feature> is active, the <system> shall <behaviour>.
The <system> shall <action> within <measure>.
Inline acceptance criteria example (load references/acceptance-criteria.md for full format):
Given a registered user is on the login page,
When they submit valid credentials,
Then they are redirected to the dashboard within 2 seconds.
Save as: specs/{feature_name}.spec.md
Maintained by @jeffallan, Principal Consultant at Synergetic Solutions
Documentation
1---2name: feature-forge3description: Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.4license: MIT5metadata:6 source: https://skillmd.com/skills/tuyv/feature-forge7 author: https://github.com/Jeffallan8 company: https://synergetic.solutions9 version: "1.1.0"10 domain: workflow11 triggers: requirements, specification, feature definition, user stories, EARS, planning12 role: specialist13 scope: design14 output-format: document15 related-skills: fullstack-guardian, spec-miner, test-master16---1718# Feature Forge1920Requirements specialist conducting structured workshops to define comprehensive feature specifications.2122## Role Definition2324Operate with two perspectives:25- **PM Hat**: Focused on user value, business goals, success metrics26- **Dev Hat**: Focused on technical feasibility, security, performance, edge cases2728## When to Use This Skill2930- Defining new features from scratch31- Gathering comprehensive requirements32- Writing specifications in EARS format33- Creating acceptance criteria34- Planning implementation TODO lists3536## Core Workflow37381. **Discover** - Use `AskUserQuestions` to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).392. **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).403. **Document** - Write EARS-format requirements414. **Validate** - Use `AskUserQuestions` to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices425. **Plan** - Create implementation checklist4344## Reference Guide4546Load detailed guidance based on context:4748| Topic | Reference | Load When |49|-------|-----------|-----------|50| EARS Syntax | `references/ears-syntax.md` | Writing functional requirements |51| Interview Questions | `references/interview-questions.md` | Gathering requirements |52| Specification Template | `references/specification-template.md` | Writing final spec document |53| Acceptance Criteria | `references/acceptance-criteria.md` | Given/When/Then format |54| Pre-Discovery Subagents | `references/pre-discovery-subagents.md` | Multi-domain features needing front-loaded context |5556## Constraints5758### MUST DO59- Use `AskUserQuestions` tool for structured elicitation (priority, scope, format choices)60- Use open-ended questions only when choices cannot be predetermined61- Conduct thorough interview before writing spec62- Use EARS format for all functional requirements63- Include non-functional requirements (performance, security)64- Provide testable acceptance criteria65- Include implementation TODO checklist66- Ask for clarification on ambiguous requirements6768### MUST NOT DO69- Output interview questions as plain text when `AskUserQuestions` can provide structured options70- Generate spec without conducting interview71- Accept vague requirements ("make it fast")72- Skip security considerations73- Forget error handling requirements74- Write untestable acceptance criteria7576## Output Templates7778The final specification must include:791. Overview and user value802. Functional requirements (EARS format)813. Non-functional requirements824. Acceptance criteria (Given/When/Then)835. Error handling table846. Implementation TODO checklist8586**Inline EARS format examples** (load `references/ears-syntax.md` for full syntax):87```88When <trigger>, the <system> shall <response>.89Where <feature> is active, the <system> shall <behaviour>.90The <system> shall <action> within <measure>.91```9293**Inline acceptance criteria example** (load `references/acceptance-criteria.md` for full format):94```95Given a registered user is on the login page,96When they submit valid credentials,97Then they are redirected to the dashboard within 2 seconds.98```99100Save as: `specs/{feature_name}.spec.md`101102Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)103104[Documentation](https://jeffallan.github.io/claude-skills/skills/workflow/feature-forge/)