Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrequirements-specificationExecute the skills CLI command in your project's root directory to begin installation:
Fetches requirements-specification from pluginagentmarketplace/custom-plugin-product-manager and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate requirements-specification. Access via /requirements-specification in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
2
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2
stars
Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.
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)
As a [user role]
I want [action/capability]
So that [benefit/outcome]
Acceptance Criteria:
Given [context]
When [user action]
Then [expected result]
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
Scenario: [Specific user action]
Given [initial context/state]
When [user performs action]
Then [expected result]
And [additional verification]
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
Functional Requirements
Non-Functional Requirements
Business Requirements
Constraints
Structure:
Each Story Includes:
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
Entity Relationship Diagram
MoSCoW Method:
MUST Have (Non-negotiable)
SHOULD Have (Important but not critical)
COULD Have (Nice-to-have)
WON'T Have (Explicitly out of scope)
Red Flags:
Responses:
Change Request Process:
❌ "Improve performance" ✅ "Reduce page load time from 4s to under 2s"
❌ "Build dashboard" ✅ "Build dashboard showing active users in last 24h with 95% accuracy"
❌ "Fix the bug" ✅ "When searching with special characters, results show error. Fix to handle special chars."
❌ "Use Redux with saga middleware for state management" ✅ "State changes must be traceable and debuggable"
❌ "System should be fast" ✅ "API response time < 200ms for 95th percentile"
| Hata | Olası Sebep | Çözüm |
|---|---|---|
| Story çok büyük | Epic olarak yazıldı | Story breakdown |
| AC belirsiz | Vague criteria | Given/When/Then format |
| Scope creep | Change mgmt yok | Change request process |
| Missing edge cases | Happy path focus | Edge case workshop |
[ ] 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ı?
Write clear requirements and avoid 90% of project problems!
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
requirements-specification reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: requirements-specification is focused, and the summary matches what you get after install.
requirements-specification fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
requirements-specification has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend requirements-specification for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added requirements-specification from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
requirements-specification is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
requirements-specification fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in requirements-specification — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
requirements-specification fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 47