New: 97,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

Requirements Specification

by nicepkg in nicepkg/ai-workflow

Master requirements gathering, user story writing, acceptance criteria definition, and scope management.

MITAuto-check passedProduct & Project Management

Install Requirements Specification

skills CLI
$ npx skills add nicepkg/ai-workflow --skill requirements-specification -a claude-code

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

GitHub CLI
$ gh skill install nicepkg/ai-workflow requirements-specification --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/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/product-manager-workflow/.claude/skills/requirements .claude/skills/requirements-specification && 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
requirements-specification
GitHub stars
285
Token cost
~2k tokens
SKILL.md length
629 words
Files
4 (incl. scripts, references, assets)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Master requirements gathering, user story writing, acceptance criteria definition, and scope management.

  • Works in 6 steps: Document the change → Assess impact (time, complexity) → Present trade-offs → …
  • Tasks that involve User stories
  • SKILL.md covers User Story Writing (INVEST…, Acceptance Criteria (BDD Format), Requirements Document Structure and Scope Management, plus 3 more sections
  • Runs Python scripts from its folder

What it does

Requirements Specification is an agent skill from nicepkg/ai-workflow. Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/config.yaml`, `references/GUIDE.md` and `scripts/helper.py`).

It sits in Product & Project Management, covering User stories. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.

When your agent uses it

  • Tasks that involve User stories

Example prompts

  • “/requirements-specification”

Requirements

  • Python 3

Workflow steps

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

  1. Document the change
  2. Assess impact (time, complexity)
  3. Present trade-offs
  4. Get stakeholder decision
  5. Update requirements document
  6. Communicate to team

What it can do on your machine

Read from SKILL.md and the folder at commit d167b41. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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

Requirements Specification loads about 2k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 629 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 629 words, ~1,967 tokens.

Download SKILL.mdSave it as .claude/skills/requirements-specification/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
requirements-specification
description
Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.
version
2.0.0
sasmp_version
1.3.0
bonded_agent
03-requirements-definition
bond_type
PRIMARY_BOND
retry_logic.max_attempts
3
retry_logic.backoff
exponential
logging.level
info
logging.hooks
start, complete, error

Requirements & Specification Skill

Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.

User Story Writing (INVEST Format)

INVEST Principles

I - Independent (minimal dependencies) N - Negotiable (details can be discussed) V - Valuable (delivers customer value) E - Estimable (team can estimate effort) S - Small (can complete in 1-2 sprints) T - Testable (clear success criteria)

User Story Template
As a [user role]
I want [action/capability]
So that [benefit/outcome]

Acceptance Criteria:
Given [context]
When [user action]
Then [expected result]
Good vs Bad Examples

Bad Story:

As a user
I want a better dashboard
So that I can see my data

Problem: Too vague, not testable, too large

Good Story:

As a project manager
I want to see all tasks assigned to me in the last 24 hours
So that I can track what happened while I was offline

Acceptance Criteria:
Given I'm logged in
When I view the Home dashboard
Then I see a "Recent Tasks" section
And it shows tasks assigned to me from last 24 hours
And tasks are sorted by assignment time (newest first)
And clicking a task opens the task detail page

Acceptance Criteria (BDD Format)

Scenario Template
Scenario: [Specific user action]
Given [initial context/state]
When [user performs action]
Then [expected result]
And [additional verification]
Example: Password Reset Feature
Scenario: User resets password with valid email
Given I'm on the login page
And I'm not logged in
When I click "Forgot Password?"
And enter my email address
And click "Send Reset Email"
Then I see message "Check your email for reset link"
And a password reset email is sent to that address
And the email contains a valid reset link

Scenario: User uses expired reset link
Given I received a password reset email
And the reset link is more than 24 hours old
When I click the reset link
Then I see "Link has expired"
And I'm offered to request a new reset link

Scenario: Password doesn't meet requirements
Given I'm on password reset page
When I enter password "123"
Then I see error "Password must be 8+ characters"
And the form doesn't submit

Requirements Document Structure

Executive Summary (1 page)
  • Overview of feature/product
  • Business goal/context
  • Key benefits
  • Timeline
  • Success metrics
Requirements Overview (5-10 pages)

Functional Requirements

  • What the system must do
  • Features and capabilities
  • User interactions
  • Data handling

Non-Functional Requirements

  • Performance (response time < 2s)
  • Scalability (support 10K concurrent users)
  • Security (encrypt PII)
  • Availability (99.9% uptime)
  • Accessibility (WCAG AA compliance)

Business Requirements

  • Why we're building this
  • Business metrics
  • Customer need
  • Competitive advantage

Constraints

  • Technical constraints
  • Budget constraints
  • Timeline constraints
  • Resource constraints
User Stories & Epics (20-50 pages)

Structure:

  • Epic: Large initiative grouping related stories
  • User Stories: Individual features (10-20 stories per epic)
  • Tasks: Engineering breakdown (if needed)

Each Story Includes:

  • Story ID and title
  • As a... I want... so that...
  • Acceptance criteria (3-8 scenarios)
  • Story points estimate
  • Dependencies
  • Design reference (wireframe/mockup)
  • Note/clarifications
Use Cases & Flows (10-20 pages)

Use Case Template:

Use Case: [Use Case Name]
Primary Actor: [User role]
Precondition: [State before action]

Main Flow:
1. User does X
2. System responds with Y
3. User does Z
4. System returns result

Alternative Flows:
3a. If data invalid
    - System shows error
    - User corrects and resubmits
Data Models (10 pages)

Entity Relationship Diagram

  • Entities (User, Post, Comment)
  • Relationships (User creates Posts)
  • Attributes (Post title, content, creation_date)
  • Primary keys, foreign keys
UI/Wireframes (Attached)
  • User interface mockups
  • User flows and navigation
  • Key interactions

Scope Management

MVP vs Nice-to-Have

MoSCoW Method:

MUST Have (Non-negotiable)

  • Core functionality
  • Without these: product won't work
  • Must launch with these
  • Example: User login, basic content view

SHOULD Have (Important but not critical)

  • Enhance user experience
  • Value add
  • If time allows
  • Example: Advanced search, saved preferences

COULD Have (Nice-to-have)

  • Polish features
  • Low priority
  • Do if extra time/budget
  • Example: Dark mode, animations

WON'T Have (Explicitly out of scope)

  • Clear for future
  • Helps say "no" to stakeholders
  • Plan for later version
  • Example: Mobile app (launching web first)
Scope Creep Prevention

Red Flags:

  • "Can we just add...?"
  • "This would be better if..."
  • "What about also including..."
  • "One more thing..."

Responses:

  • "That's a great idea. Let's add it to the roadmap for Q2."
  • "That would add 3 weeks. What would you deprioritize?"
  • "That's outside current scope. Document for next phase."
Show full SKILL.md (229 more words)Show less
Change Management

Change Request Process:

  1. Document the change
  2. Assess impact (time, complexity)
  3. Present trade-offs
  4. Get stakeholder decision
  5. Update requirements document
  6. Communicate to team

Common Pitfalls

Too Vague

❌ "Improve performance" ✅ "Reduce page load time from 4s to under 2s"

No Success Criteria

❌ "Build dashboard" ✅ "Build dashboard showing active users in last 24h with 95% accuracy"

Missing Context

❌ "Fix the bug" ✅ "When searching with special characters, results show error. Fix to handle special chars."

Over-Specifying

❌ "Use Redux with saga middleware for state management" ✅ "State changes must be traceable and debuggable"

Ambiguous Acceptance Criteria

❌ "System should be fast" ✅ "API response time < 200ms for 95th percentile"

Requirements Review Checklist

  • ✓ Each requirement is testable
  • ✓ No requirement specifies implementation
  • ✓ Dependencies identified and documented
  • ✓ Acceptance criteria clear and complete
  • ✓ Engineering has estimated effort
  • ✓ Design mockups provided
  • ✓ Data models documented
  • ✓ Edge cases considered
  • ✓ Scope clearly defined (MVP vs future)
  • ✓ Success metrics identified
  • ✓ Timeline realistic
  • ✓ Reviewed by engineering lead
  • ✓ Reviewed by design lead
  • ✓ Stakeholder aligned

Troubleshooting

Yaygın Hatalar & Çözümler
HataOlası SebepÇözüm
Story çok büyükEpic olarak yazıldıStory breakdown
AC belirsizVague criteriaGiven/When/Then format
Scope creepChange mgmt yokChange request process
Missing edge casesHappy path focusEdge case workshop
Debug Checklist
[ ] Her story INVEST criteria geçiyor mu?
[ ] Acceptance criteria testable mı?
[ ] Non-functional requirements tanımlı mı?
[ ] Dependencies documented mı?
[ ] Engineering review yapıldı mı?
Recovery Procedures
  1. Ambiguous Requirements → Clarification meeting
  2. Scope Creep → Trade-off matrix
  3. Missing Feasibility → Engineering spike

Write clear requirements and avoid 90% of project problems!

© nicepkg, 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 3 other files (scripts, references, assets) in workflows/product-manager-workflow/.claude/skills/requirements of nicepkg/ai-workflow.

  • SKILL.md
  • assets/config.yaml
  • references/GUIDE.md
  • scripts/helper.py

Open the folder on GitHubat commit d167b41

Compare with similar skills

Requirements Specification 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.

Requirements Specification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Requirements Specification this skillnicepkg/ai-workflow285—~2kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

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

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

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

  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

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

  • Check

    VibiumDev/vibium

    Independently check application acceptance criteria in a live browser or saved recording with the Vibium CLI.

    2.9k GitHub stars~2k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from nicepkg/ai-workflow

All 61 skills in this repo

  • Capture Triage

    nicepkg/ai-workflow

    Processes Drafts Pro captures from the Inbox folder. An agent skill from nicepkg/ai-workflow.

    285 GitHub stars~3k tokensUpdated 8 mo ago
    Auto-check passed

  • Legacy To AI Ready

    nicepkg/ai-workflow

    Transform legacy codebases into AI-ready projects with Claude Code configurations.

    285 GitHub stars~2.2k tokensUpdated 8 mo ago
    Auto-check: notes

  • Newsletter Coach

    nicepkg/ai-workflow

    Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts.

    285 GitHub stars~3.7k tokensUpdated 8 mo ago
    Auto-check passed

  • Webfluence

    nicepkg/ai-workflow

    Content web architecture framework. An agent skill from nicepkg/ai-workflow.

    285 GitHub stars~1.4k tokensUpdated 8 mo ago
    Auto-check passed

  • Workflow Creator

    nicepkg/ai-workflow

    Create complete Claude Code workflow directories with curated skills.

    285 GitHub stars~2.6k tokensUpdated 8 mo ago
    Auto-check passed

  • Media Processing

    nicepkg/ai-workflow

    Video/audio/image processing with FFmpeg and ImageMagick. An agent skill from nicepkg/ai-workflow.

    285 GitHub stars~2.4k tokensUpdated 8 mo ago
    Auto-check: notes

Categories

Questions about Requirements Specification

What does Requirements Specification do?

Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Requirements Specification is an agent skill from nicepkg/ai-workflow. Master requirements gathering, user story writing, acceptance criteria definition, and scope management.

When should I use Requirements Specification?

Requirements Specification fits situations like: tasks that involve User stories.

How do I install Requirements Specification in Claude Code?

Run `npx skills add nicepkg/ai-workflow --skill requirements-specification -a claude-code`. Or copy the skill folder (workflows/product-manager-workflow/.claude/skills/requirements in nicepkg/ai-workflow) into .claude/skills/requirements-specification in your project. Claude Code loads it when a task matches its description.

How do I install Requirements Specification in Codex?

Run `npx skills add nicepkg/ai-workflow --skill requirements-specification -a codex`. Or copy the skill folder (workflows/product-manager-workflow/.claude/skills/requirements in nicepkg/ai-workflow) into .agents/skills/requirements-specification in your project. Codex loads it when a task matches its description.

Can I use Requirements Specification 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 nicepkg/ai-workflow --skill requirements-specification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirements-specification, .gemini/skills/requirements-specification, .github/skills/requirements-specification and .opencode/skills/requirements-specification in your project.

What does Requirements Specification need to run?

Going by SKILL.md and its folder, Requirements Specification needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Requirements Specification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Requirements Specification 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Requirements Specification use?

Requirements Specification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Requirements Specification use?

About 2k tokens (SKILL.md is roughly 7.9k 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 6 tokens, read only when the agent opens those files.

What are the alternatives to Requirements Specification?

Skills that share tags, products or a category with Requirements Specification: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Requirements Specification?

nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on January 20, 2026.

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