User Story

This skill turns vague asks into stories engineering can execute on without a follow-up meeting. The deliverable is a Markdown ticket that can paste into Jira, Linear, Asana, or a Confluence/Notion backlog with no further translation.

When to use this skill

• A stakeholder said "we need to be able to…" and you're about to write that down.
• A PRD or workshop output needs to be sliced into backlog items.
• A story has been written but engineering pushed back as too big or ambiguous.
• Acceptance criteria are missing or fuzzy.

If the user's request is just "explain what a user story is" — answer in chat, don't run this skill.

Story format

Use this template every time. Variations on the format aren't worth the loss of consistency.

# [Story title — short, outcome-oriented]