requirements-specification
From the author
Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.
Install
npx skills add nicepkg/ai-workflow --skill requirements-specification -a claude-code
Installs to .claude/skills/requirements-specification/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 72
Security85
Provenance70
Maintenance50
Licence100
Adoption41
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- project-specificationathola/claude-night-marketTransforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.Planning★ 343
- specification-writinga5c-ai/babysitterWrite feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.Writing★ 1.9K
- feature-specw95/awesome-claude-corporate-skillsWrite detailed feature specifications with functional requirements, edge cases, data models, API contracts, and UX flows. Create comprehensive technical specifications that enable clear implementation.Planning★ 285
- specification-generationa5c-ai/babysitterConvert requirements into structured technical specifications with architecture decisionsPlanning★ 1.9K
- spechashgraph-online/awesome-codex-pluginsSpec phase. Converts user requirements into a numbered Requirements + Acceptance Criteria document saved as SPEC-{timestamp}.md. Prompts /team suggestion when 3+ requirements are detected.Planning★ 1.4K
- product-requirementscbrock84/headcountWrites down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.Planning★ 2.2K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in