// Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?"
| name | issue-writing |
| description | Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?" |
This skill guides the creation of well-structured, actionable Jira issues that any developer or AI can pick up and execute independently.
Apply this skill when:
h2. IMPORTANT: Jira Issue Discipline
[Standard discipline rules]
---
h2. Problem
[1-2 sentences: Why does this feature need to exist?]
h2. Solution
[1-2 sentences: What are we building to solve this?]
h2. High-Level Implementation
[Bullet points: Key technical decisions, patterns]
h2. Codebase Investigation Findings
[What patterns to follow, similar features, code locations]
h2. Out of Scope / Deferred
[Explicitly list what we're NOT doing]
h2. Objective
[1-2 sentences: What specific thing needs to be done?]
h2. Acceptance Criteria
* [Specific, testable criterion 1]
* [Specific, testable criterion 2]
* [Specific, testable criterion 3]
h2. Implementation Notes
* Relevant files: [paths]
* Patterns to follow: [reference]
* Dependencies: [other Subtasks]
Jira uses Wiki markup, not Markdown:
h1., h2., h3.*bold** or -#{{inline}} or {code}block{code}[title|url]Remember: A good issue can be executed by anyone who reads it.