New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Feature Forge

by Jeffallan in Jeffallan/claude-skills

Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.

MITAuto-check passedProduct & Project Management

Install Feature Forge

skills CLI
$ npx skills add Jeffallan/claude-skills --skill feature-forge -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Jeffallan/claude-skills feature-forge --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Jeffallan/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/feature-forge .claude/skills/feature-forge && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feature-forge
GitHub stars
12k
Token cost
~1.1k tokens
SKILL.md length
345 words
Files
6 (incl. references)
Skills in repo
58
Repo updated
First seen
Licence
MIT

At a glance

Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.

  • Works in 5 steps: Discover - Use AskUserQuestions to… → Interview - Systematic questioning from… → Document - Write EARS-format requirements → …
  • Defining a new feature from a rough idea before any code is written
  • SKILL.md covers Role Definition, When to Use This Skill, Core Workflow and Reference Guide, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Here the agent plays a requirements specialist with two viewpoints: a product manager focused on user value, goals and metrics, and a developer focused on feasibility, security and edge cases. It moves through five steps: discover the goal and users, interview from both perspectives, write EARS-format requirements, review acceptance criteria with the stakeholder, and plan an implementation checklist.

Questions go through the AskUserQuestions tool as structured choices where possible, with open-ended follow-ups only when options cannot be set in advance. For features that span several domains, Task subagents can gather context first. Reference files cover EARS syntax, interview questions, a specification template, Given/When/Then criteria and pre-discovery subagents. The agent must finish the interview before writing the spec and must include non-functional requirements.

When your agent uses it

  • Defining a new feature from a rough idea before any code is written
  • Writing functional requirements in EARS format
  • Drafting acceptance criteria in Given/When/Then form
  • Turning stakeholder answers into a spec and a TODO checklist

Example prompts

  • “Interview me about a CSV export feature for our reports page, then write the spec.”
  • “Rewrite these requirements for the notification settings in EARS format.”
  • “Draft acceptance criteria for the password reset flow and list the edge cases.”
  • “Turn the signed-off spec into an implementation checklist for the team.”

Requirements

  • An agent that supports the `AskUserQuestions` tool

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Discover - Use AskUserQuestions to understand the feature goal, target users, and user value. Present structured choices where possible…
  2. Interview - Systematic questioning from both PM and Dev perspectives using AskUserQuestions for structured choices and open-ended…
  3. Document - Write EARS-format requirements
  4. Validate - Use AskUserQuestions to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices
  5. Plan - Create implementation checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 1be15d8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • synergetic.solutions
    • jeffallan.github.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Forge loads about 1.1k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 345 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jeffallan/claude-skills at commit 1be15d8, republished under its MIT licence (© Jeffallan). 345 words, ~1,117 tokens.

Download SKILL.mdSave it as .claude/skills/feature-forge/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
feature-forge
description
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.
license
MIT
metadata.author
https://github.com/Jeffallan
metadata.company
https://synergetic.solutions
metadata.version
1.1.0
metadata.domain
workflow
metadata.triggers
requirements, specification, feature definition, user stories, EARS, planning
metadata.role
specialist
metadata.scope
design
metadata.output-format
document
metadata.related-skills
fullstack-guardian, spec-miner, test-master

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

  1. Discover - Use AskUserQuestions to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).
  2. 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).
  3. Document - Write EARS-format requirements
  4. Validate - Use AskUserQuestions to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices
  5. Plan - Create implementation checklist

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
EARS Syntaxreferences/ears-syntax.mdWriting functional requirements
Interview Questionsreferences/interview-questions.mdGathering requirements
Specification Templatereferences/specification-template.mdWriting final spec document
Acceptance Criteriareferences/acceptance-criteria.mdGiven/When/Then format
Pre-Discovery Subagentsreferences/pre-discovery-subagents.mdMulti-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:

  1. Overview and user value
  2. Functional requirements (EARS format)
  3. Non-functional requirements
  4. Acceptance criteria (Given/When/Then)
  5. Error handling table
  6. 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

© Jeffallan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/feature-forge of Jeffallan/claude-skills.

  • SKILL.md
  • references/acceptance-criteria.md
  • references/ears-syntax.md
  • references/interview-questions.md
  • references/pre-discovery-subagents.md
  • references/specification-template.md

Open the folder on GitHubat commit 1be15d8

Compare with similar skills

Feature Forge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature Forge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Forge this skillJeffallan/claude-skills12k—~1.1kAutomated safety check: PassMIT
PRD Developmentdeanpeters/Product-Manager-Skills7.2k3 repos~6.2kAutomated safety check: PassCustom licence
Ambiguity Detectormajiayu000/claude-skill-registry6661 repos~2.5kAutomated safety check: PassMIT
User Alignment and Agent-Ready PRDstryproduck/produck-skills510—~5.3kAutomated safety check: PassApache-2.0
RalphTheCraigHewitt/skills157—~1kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k1 repos~5.7kAutomated safety check: PassMIT

Similar skills

  • PRD Development

    deanpeters/Product-Manager-Skills

    Builds a structured PRD that ties problem, users, solution and success criteria together, turning discovery notes into a document engineers can act on.

    7.2k GitHub starsUsed in 3 repos~6.2k tokens
    Product & Project ManagementAuto-check passed

  • Ambiguity Detector

    majiayu000/claude-skill-registry

    Detects and analyzes ambiguous language in software requirements and user stories.

    666 GitHub starsUsed in 1 repo~2.5k tokens
    Product & Project ManagementAuto-check passed

  • User Alignment and Agent-Ready PRDs

    tryproduck/produck-skills

    Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.

    510 GitHub stars~5.3k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Ralph

    TheCraigHewitt/skills

    Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation.

    157 GitHub stars~1k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

More from Jeffallan/claude-skills

All 58 skills in this repo

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Auto-check passed

  • CLI Developer

    Jeffallan/claude-skills

    Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.

    12k GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed

  • Fine-Tuning Expert

    Jeffallan/claude-skills

    Guides LLM fine-tuning with LoRA and QLoRA through Hugging Face PEFT, from dataset validation and training checks to adapter merging, quantization and deployment.

    12k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • GraphQL Architect

    Jeffallan/claude-skills

    Designs GraphQL schemas and Apollo Federation graphs, with DataLoader resolvers, subscriptions, query complexity limits and caching.

    12k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Kubernetes Specialist

    Jeffallan/claude-skills

    Creates and checks Kubernetes manifests, Helm charts, RBAC and network policies, and helps debug pod problems, with kubectl checks and rollback steps.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Laravel Specialist

    Jeffallan/claude-skills

    Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

Categories

Questions about Feature Forge

What does Feature Forge do?

Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist. Here the agent plays a requirements specialist with two viewpoints: a product manager focused on user value, goals and metrics, and a developer focused on feasibility, security and edge cases. It moves through five steps: discover the goal and users, interview from both perspectives, write EARS-format requirements, review acceptance criteria with the stakeholder, and plan an implementation checklist.

When should I use Feature Forge?

Feature Forge fits situations like: defining a new feature from a rough idea before any code is written; writing functional requirements in EARS format; drafting acceptance criteria in Given/When/Then form; turning stakeholder answers into a spec and a TODO checklist.

How do I install Feature Forge in Claude Code?

Run `npx skills add Jeffallan/claude-skills --skill feature-forge -a claude-code`. Or copy the skill folder (skills/feature-forge in Jeffallan/claude-skills) into .claude/skills/feature-forge in your project. Claude Code loads it when a task matches its description.

How do I install Feature Forge in Codex?

Run `npx skills add Jeffallan/claude-skills --skill feature-forge -a codex`. Or copy the skill folder (skills/feature-forge in Jeffallan/claude-skills) into .agents/skills/feature-forge in your project. Codex loads it when a task matches its description.

Can I use Feature Forge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jeffallan/claude-skills --skill feature-forge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-forge, .gemini/skills/feature-forge, .github/skills/feature-forge and .opencode/skills/feature-forge in your project.

What does Feature Forge need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Forge is instructions for the agent only. Our summary lists: An agent that supports the `AskUserQuestions` tool.

Does Feature Forge access the network?

SKILL.md names 3 domains. As links in the text: github.com, synergetic.solutions and jeffallan.github.io. This is read from the text; nothing was executed.

Is Feature Forge safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature Forge use?

Feature Forge is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature Forge use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Feature Forge?

Skills that share tags, products or a category with Feature Forge: PRD Development (deanpeters/Product-Manager-Skills, 7.2k stars), Ambiguity Detector (majiayu000/claude-skill-registry, 666 stars), User Alignment and Agent-Ready PRDs (tryproduck/produck-skills, 510 stars) and Ralph (TheCraigHewitt/skills, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Forge?

Jeffallan (a GitHub user) maintains it in Jeffallan/claude-skills, which has 11,767 GitHub stars. The repository holds 58 skills in this directory. The repository was last updated on October 3, 2026.

Source: Jeffallan/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.