jira-driven-planning

Generates structured implementation plans from Jira tickets and Confluence documents.

5.4k|571|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/breaking-brake/cc-wf-studio --skill jira-driven-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-driven-planning
Source: https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning
Command: npx skills add https://github.com/breaking-brake/cc-wf-studio --skill jira-driven-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning Jira ticket requirements and scattered Confluence documentation into a concrete, organized implementation plan is time-consuming and error-prone. This Skill automates the planning step by producing a structured plan split across Frontend, Backend, and Infrastructure workstreams.

Core Features & Use Cases

  • Requirements Summarization: Restates Jira ticket requirements, acceptance criteria, and ambiguities in clear, actionable terms.
  • Three-Axis Task Breakdown: Organizes tasks into Frontend, Backend, and Infrastructure tracks with dependencies and blockers explicitly identified.
  • Risk Assessment: Documents technical risks with severity ratings, mitigation strategies, and fallback plans.
  • Use Case: After fetching a Jira ticket and related Confluence design docs, invoke this Skill to produce a review-ready implementation plan covering architecture decisions, task breakdown, dependencies, and risks before any code is written.

Quick Start

Create an implementation plan for the retrieved Jira ticket and Confluence documents, split into frontend, backend, and infrastructure tasks.

Frequently Asked Questions about jira-driven-planning

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

FAQPage Schema
How do I create an implementation plan from a Jira ticket?

Provide the Jira ticket details (title, description, acceptance criteria, priority) along with related Confluence documents, then invoke this Skill. It produces a structured plan with requirements summary, technical approach, task breakdown, dependencies, and risks.

How to break down a Jira ticket into frontend and backend tasks?

This Skill automatically splits work into Frontend, Backend, and Infrastructure tracks. Frontend covers UI components and API integration, Backend covers endpoints and database changes, and Infrastructure covers IaC, CI/CD, and monitoring.

Does this Skill fetch Jira or Confluence data itself?

No. The Skill assumes Jira ticket information and Confluence search results have already been retrieved in a prior step. It only consumes that pre-fetched context to build the implementation plan.

What does the implementation plan output include?

The plan includes a requirements summary, technical approach with architecture rationale, task breakdown across three tracks, dependency and blocker mapping, and risks with severity ratings and mitigation strategies.

When should I not use Jira-driven planning?

Avoid it when requirements are unclear or Jira/Confluence inputs are unavailable, since the Skill depends on that context. It also stays at the planning level and does not produce implementation-level code detail.