Feature Forge skill: what it does and how to install it
Runs structured requirements workshops in Claude Code, turning feature ideas into EARS requirements, acceptance criteria and implementation checklists.
Summary generated from the skill's documentation.
Warning. A security audit flagged this skill with a critical risk warning. Read its SKILL.md and scripts before you install it.
Install
$ npx skills add Jeffallan/claude-skills --skill feature-forgeRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Interviews stakeholders from product and development perspectives to clarify goals, users, scope, trade-offs and edge cases. It produces EARS functional requirements, non-functional requirements, Given/When/Then acceptance criteria, error handling and an implementation checklist in a feature specification.
When to use it. For new features, requirements gathering, user stories, PRDs, acceptance criteria or EARS-format specifications. It requires a thorough interview before writing and does not accept vague or untestable requirements.
History
Repo stars
12.1k+332 since 5 Oct 2026
Stars are counted for the whole repository, which holds 51 skills.
Show as a table
| Date | Repo stars |
|---|---|
| 26 Oct 2026 | 12,068 |
| 25 Oct 2026 | 12,050 |
| 24 Oct 2026 | 12,032 |
| 23 Oct 2026 | 12,017 |
| 22 Oct 2026 | 11,999 |
| 21 Oct 2026 | 11,974 |
| 20 Oct 2026 | 11,948 |
| 19 Oct 2026 | 11,940 |
| 18 Oct 2026 | 11,921 |
| 17 Oct 2026 | 11,909 |
| 16 Oct 2026 | 11,895 |
| 15 Oct 2026 | 11,881 |
| 14 Oct 2026 | 11,865 |
| 13 Oct 2026 | 11,850 |
| 12 Oct 2026 | 11,838 |
| 11 Oct 2026 | 11,819 |
| 10 Oct 2026 | 11,806 |
| 9 Oct 2026 | 11,791 |
| 8 Oct 2026 | 11,776 |
| 7 Oct 2026 | 11,756 |
| 6 Oct 2026 | 11,746 |
| 5 Oct 2026 | 11,736 |
Installs
4.3k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- BrainstormingExplores intent, requirements and design with you before any feature or component is implemented.
- Requirements ClarityClarifies ambiguous requirements through focused questions before implementation starts.
- Spec to BacklogConverts a Confluence specification into a structured Jira backlog of epics and implementation tickets.