maestria-co/jira-story
skills/jira-story/SKILL.md
Format a structured story spec into a Jira-ready user story. Used by the product-manager agent to produce the final Jira output — do not gather requirements here, just format them. Also invocable directly when someone says "format this as a Jira ticket", "turn this spec into a Jira story", or "write this up for Jira".
development
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add maestria-co/ai-playbook jira-storyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 6:34 AM56.7s1 file scanned
SKILL.md
- name:
- jira-story
- user-invocable:
- true
- description:
- >
Skill: Jira Story
Purpose
Receive a structured story spec and format it as a well-formed Jira user story. This skill is a formatter only — it does not gather requirements, research the codebase, or make technical decisions. Those steps belong to the product-manager agent upstream.
Input Expected
A structured spec containing some or all of:
- User story statement (persona / goal / benefit)
- Draft acceptance criteria
- Technical detail notes (affected components, API changes, data model)
- Dependencies and blocking tickets
- Open questions
If any of these are missing, format what is available and note the gaps in the output's Open Questions section.
Output Format
Produce a single Markdown block ready to paste into Jira (or save as story.md):
**Story:**
As a [specific persona],
I want [goal],
So that [measurable benefit]
---
**Acceptance Criteria:**
1. Given [context], when [action], then [result]
2. Given [context], when [action], then [result]
3. Given [context], when [action], then [result]
[Mark any inferred AC with `(inferred — pending PO confirmation)`]
---
**Technical Notes:**
- Affected Components: [list]
- API Changes: [list or "None"]
- Data Model Changes: [list or "None"]
- Key Files: [list]
- Cross-Cutting Concerns: [auth, caching, events — or "None"]
- Complexity Estimate: [S / M / L / XL]
---
**Dependencies:**
- Blocking Tickets: [ticket IDs or "None"]
- Required Resources: [list or "None"]
- Approvals Needed: [list or "None"]
---
**Open Questions:**
- Q: [question] — Owner: [PO / Tech Lead / etc.] — Assumed: [assumption made]
Formatting Rules
- Persona must be specific — not "user" but e.g. "logged-in admin", "guest checkout user"
- AC must be testable (Given/When/Then) — rewrite any AC that can't be verified as pass/fail
- Mark every inferred AC clearly — the PO must confirm these during grooming
- Technical Notes are for developers, not business logic — keep them factual
- Open Questions must include who should answer and what was assumed in the meantime
- Do not add requirements that weren't in the input spec — format only what exists
Constraints
- No requirement gathering — receive the spec, format it, done
- No silent rewrites of ACs — if you rephrase for testability, note the change
- No implementation instructions in the story body — those go in Technical Notes
- One story per output — if the input describes multiple features, note that a split is recommended
Related Skills
maestria-co/writing-tests
development
VerifiedTrustedCommunity
Writes and runs a test suite for a piece of code, covering happy path, edge cases, error cases, and security cases. Use when: implementation is complete and needs test coverage, a bug needs a reproduction test and fix validation, or code needs coverage before a refactor. Do not use when: the code under test is not yet implemented, or the spec is still unclear.
SKILL.mdUpdated Apr 26, 2026
maestria-co/writing-skills
testing
VerifiedTrustedCommunity
Use when creating a new skill, editing an existing skill, or helping a user author a skill for this system. Covers structure, discoverability, quality, and discipline hardening.
SKILL.mdUpdated Apr 26, 2026
maestria-co/verification-checklist
development
VerifiedTrustedCommunity
Evidence-based verification process to run before marking any task complete. Use this skill every time you're about to report that work is done — for features, bug fixes, refactoring, or any code change. This catches the most common failure mode: declaring "done" without proof. If you're finishing up and about to tell the user the task is complete, run this checklist first.
SKILL.mdUpdated Apr 26, 2026
maestria-co/using-skills
development
VerifiedTrustedCommunity
Teaches agents how to discover, select, and invoke skills from the skill library. Use this skill whenever you're uncertain which skill applies to a task, when composing multiple skills for complex work, or when you need to understand what skills are available. This is your go-to when facing an ambiguous task and need to figure out the right approach before diving into implementation.
SKILL.mdUpdated Apr 26, 2026