story-to-impl-plan

Convert user stories with acceptance criteria into deterministic implementation plans with Jira tasks and Markdown artifacts.

8|1|Updated Jul 7, 2025
One-click install
npx skills add https://github.com/dasheck0/qraft-templates --skill story-to-impl-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-to-impl-plan
Source: https://github.com/dasheck0/qraft-templates/tree/main/opencode-global-skills/story-to-impl-plan
Command: npx skills add https://github.com/dasheck0/qraft-templates --skill story-to-impl-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Converts a finished user story with ACs into a deterministic, AI-native implementation plan and publishes it as Jira tasks and a Markdown file in the project. This enables teams to align on a concrete execution plan without ambiguity.

Core Features & Use Cases

  • Generate a complete implementation plan from a user story, including tasks and subtasks wired to acceptance criteria.
  • Map the plan to Jira and produce a Markdown artifact in the repository for traceability.
  • Validate inputs, trigger planning when a story with ACs is provided, and enforce governance constraints.

Quick Start

Provide the Jira Story Key (e.g., SCRUM-47) or paste the user story text to generate the plan.

Frequently Asked Questions about story-to-impl-plan

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

FAQPage Schema
How do I generate an implementation plan from a Jira user story?

To generate an implementation plan from a Jira user story, provide the Jira Story Key like SCRUM-47 or paste the story text. The system validates inputs and transforms acceptance criteria into deterministic tasks and subtasks.

What is a deterministic implementation plan for AI agents?

A deterministic implementation plan for AI agents is an executable Markdown file containing structured tasks and subtasks. It enforces strict input validation and maps acceptance criteria to ensure unambiguous downstream execution.

Does this planning approach enforce traceability between Jira tasks and acceptance criteria?

Yes, the planning approach enforces traceability by explicitly mapping generated tasks and subtasks to acceptance criteria. It connects Jira stories, Git repository artifacts, and AI agent governance constraints.

Can I use user story text instead of a Jira integration to create implementation tasks?

Yes, you can use user story text instead of a Jira integration to create implementation tasks. Simply paste the finished user story text directly, and the system will validate inputs and generate the plan.

What is the best way to align teams on user story execution without ambiguity?

The best way to align teams on user story execution without ambiguity is generating a deterministic plan that publishes Jira tasks and a Markdown artifact in the repository, ensuring concrete execution alignment.