Structured requirements workshops that produce EARS-format specifications, user stories, acceptance criteria, and implementation checklists.
Works with
Conducts systematic discovery interviews from both product and engineering perspectives, using structured questioning to elicit requirements before writing specifications
Outputs comprehensive specifications including functional requirements in EARS format, non-functional requirements, Given/When/Then acceptance criteria, error handling tables, and
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfeature-forgeExecute the skills CLI command in your project's root directory to begin installation:
Fetches feature-forge from jeffallan/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate feature-forge. Access via /feature-forge in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
7.9K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
7.9K
stars
Requirements specialist conducting structured workshops to define comprehensive feature specifications.
Operate with two perspectives:
AskUserQuestions to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).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).AskUserQuestions to review acceptance criteria with stakeholder, presenting key trade-offs as structured choicesLoad 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 |
AskUserQuestions tool for structured elicitation (priority, scope, format choices)AskUserQuestions can provide structured optionsThe final specification must include:
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
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
feature-forge reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend feature-forge for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added feature-forge from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend feature-forge for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
feature-forge reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: feature-forge is focused, and the summary matches what you get after install.
feature-forge fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: feature-forge is focused, and the summary matches what you get after install.
feature-forge has been reliable in day-to-day use. Documentation quality is above average for community skills.
feature-forge has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 71