feature-forge_skill
- HTML
110
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jeffallan/claude-skills --skill feature-forge- SKILL.md2.9 KB
Overview
This skill is a structured requirements specialist that helps define new features, gather requirements, and produce testable specifications. It combines a product-management perspective focused on user value and success metrics with a developer perspective focused on feasibility, security, and edge cases. Use it to produce complete EARS-format functional requirements, acceptance criteria, and an implementation checklist.
How this skill works
I run a short, systematic interview to uncover goals, users, constraints, and edge cases from both PM and Dev viewpoints. Then I draft a spec that includes an overview, EARS functional requirements, non-functional requirements, Given/When/Then acceptance criteria, an error-handling table, and a concrete TODO checklist for implementation. I always flag ambiguous points and ask clarifying questions before finalizing the spec.
When to use it
- Defining a new feature from scratch or expanding an existing flow
- Gathering comprehensive requirements across business and technical concerns
- Writing functional requirements in EARS format for clarity and testability
- Creating acceptance criteria and testable Given/When/Then scenarios
- Preparing an implementation TODO list for developers and QA
Best practices
- Always run the interview sequence before drafting any requirements
- Write each functional requirement in EARS format to ensure clarity and scope
- Include measurable non-functional requirements (performance, security, uptime)
- Provide explicit, testable acceptance criteria and link them to requirements
- Document expected error states and recovery behavior for each flow
- Prioritize items using MoSCoW or INVEST to guide implementation scope
Example use cases
- Turn a product idea into a deliverable spec with acceptance tests and TODOs
- Convert stakeholder notes into EARS-format functional requirements
- Audit an ambiguous request and produce clarified, testable requirements
- Create a developer-facing implementation checklist and error-handling matrix
- Prepare QA test cases by exporting Given/When/Then from the spec
FAQ
EARS (Easy Approach to Requirements Syntax) produces simple, readable functional requirements that reduce ambiguity and map directly to tests.
Do you produce non-functional requirements?
Yes — performance, security, reliability, and operational constraints are included and expressed as measurable targets.
Can you generate acceptance criteria for QA?
Yes — every functional requirement is paired with Given/When/Then acceptance criteria ready for QA.
