jira-story-writerlisted

# Jira Story Writer These are **guidelines, not rigid rules** — adapt them to the story's context and the team's maturity. Use this skill two ways: - **Rewrite mode** — given a rough story or bullet-point notes, produce a clean, paste-ready story the PO can drop straight into Jira with minimal edits. - **Review mode** — given an existing story, flag what is already strong, call out specific gaps, and suggest targeted improvements. Stay at the **Product Owner altitude** throughout: describe the *what* and the *why*. Leave the *how* entirely to engineering. > **Supporting files live alongside this SKILL.md. Consult them as you work:** > - `references/invest-and-structure.md` — INVEST in depth + story anatomy > - `references/acceptance-criteria.md` — patterns for crisp, testable AC > - `references/anti-patterns.md` — story smells and fixes > - `assets/jira-story-template.md` — ready-to-paste output template --- ## What a strong story has | Element | What makes it good | |---------|-------------------| | **Title** | Verb-led, outcome-focused, ≤ 10 words. Who benefits is implicit or stated. | | **Value statement** | "As a `<persona>`, I want `<capability>`, so that `<outcome>`." The *so that* is the point — keep it concrete and benefit-oriented. | | **Context / background** | Enough of the *why* and the current situation that someone outside the conversation understands the motivation. One to three sentences. | | **Acceptance criteria** | The heart of the story. Each cr