Generate user stories with acceptance criteria
user-storyskillsetup L1★17,464
alirezarezvani/claude-skills ↗What it does
Structure and validate user stories with acceptance criteria, dependencies, and implementation guidance
Best for
Agile teams that need structured, testable requirements before a story goes to development.
Inputs
- · User role
- · Feature description
- · Success metrics
- · Acceptance criteria list
Outputs
- · Formatted user story
- · AC checklist
- · Implementation roadmap
Requires
- · Markdown template
- · Jira/Linear/GitHub issues
Preconditions
Product requirement clear; acceptance criteria measurable; stakeholders aligned
Failure modes
- · Acceptance criteria too vague → implementation scope unclear
- · No success metric defined → cannot tell if feature solved the problem
- · Dependencies not listed → blocked by upstream work
Trust signals
- · User story follows: As a [role], I want [feature] so that [benefit]
- · Acceptance criteria are measurable assertions, not tasks
- · Dependencies and blockers explicitly listed