jira-story-draft

Convert problem statements into INVEST-compliant Jira user stories.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill jira-story-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-story-draft
Source: https://github.com/Eric-Pacheco95/claude-workbench/tree/main/.claude/skills/jira-story-draft
Command: npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill jira-story-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to convert complex problem statements and context into structured, INVEST-compliant Jira user stories, saving time and ensuring consistency in software development and project management workflows.

Core Features & Use Cases

  • Problem Statement Conversion: Transforms any issue into a detailed, actionable user story.
  • INVEST Compliant: Generates user stories adhering to INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) principles.
  • Jira Integration: Output can be directly pasted into a Jira ticket.
  • Use Case: Ideal for product managers and Agile teams to articulate product requirements clearly and consistently.

Quick Start

Run the /jira-story-draft skill with your problem statement or issue. Example: /jira-story-draft AML alerts missing the client's joint-account flag -- RMs are escalating to the wrong queue

Frequently Asked Questions about jira-story-draft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a problem statement into a Jira user story?

To convert a problem statement into a Jira user story, you provide the issue context to the skill, which parses the input and outputs a structured, Jira-ready ticket with summaries, descriptions, and acceptance criteria.

What are INVEST-compliant user stories and how are they generated?

INVEST-compliant user stories adhere to Independent, Negotiable, Valuable, Estimable, Small, and Testable principles. The skill generates them by transforming raw issue statements into structured agile requirements that satisfy these criteria.

How do I write acceptance criteria and non-functional requirements for Agile project management?

You can generate acceptance criteria and non-functional requirements by passing your problem statement into the skill, which automatically structures these details within the Jira user story description for clear Agile project management.

Can I create Jira-ready user stories without using external libraries?

Yes, you can create Jira-ready user stories without external libraries. The skill uses internal script files and regex-based parsing to format the output, requiring no additional dependencies or complex environment setup.

Does this user story generator include project and epic context for Jira tickets?

Yes, the user story generator incorporates project and epic details into the parsing process. This ensures the resulting Jira ticket output includes contextual information for completeness and proper structuring within your project workflow.