plan-pipeline

Generates implementation plans for Jira tickets and posts them as comments.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill plan-pipeline-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-pipeline
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/plan-pipeline
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill plan-pipeline-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing detailed, codebase-grounded implementation plans for Jira tickets is time-consuming, and vague plans slow developers down. This Skill automates the planning step by reading Jira epics and tickets, inspecting the actual codebase, and posting concrete implementation plans back to each ticket as comments. ## Core Features & Use Cases - Jira Ticket and Epic Planning: Accepts a single ticket key, multiple keys, or an epic key, then fetches the epic and all child tickets via JQL for batch planning. - Codebase-Grounded Plans: Reads relevant Django models, views, serializers, and frontend components so plans cite real file paths, model names, and endpoints rather than generic descriptions. - Structured Plan Output and Posting: Produces a consistent plan template covering data model changes, APIs, frontend changes, edge cases, testing, dependencies, and complexity estimates, then posts it as a Jira comment. - Use Case: A tech lead receives an epic with eight child stories and asks the Skill to plan the whole epic; each ticket gets a detailed, actionable implementation plan posted as a comment without any code being written. ## Quick Start Ask the assistant to run plan-pipeline for a Jira issue key such as RGDEV-180 or an epic key to generate and post implementation plans.

Frequently Asked Questions about plan-pipeline

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

FAQPage Schema
How do I generate an implementation plan for a Jira ticket?

Provide a Jira issue key such as RGDEV-180 as the argument. The Skill fetches the ticket details, inspects the relevant codebase files, generates a structured implementation plan, and posts it as a comment on the ticket.

How do I plan all tickets in a Jira epic at once?

Pass the epic key as the argument. The Skill runs a JQL search for all child stories, tasks, and bugs linked to the epic, then generates and posts an individual implementation plan for each ticket.

Does this Skill write or modify any code?

No, the Skill is planning-only and explicitly does not implement code. It reads the existing codebase to cite real file paths and model names in the plan, then posts the plan as a Jira comment.

What happens if a Jira ticket description is too vague to plan?

Instead of guessing, the Skill posts a comment on the ticket asking for clarification. This keeps plans actionable and avoids producing speculative implementation details.

What information does each generated implementation plan include?

Each plan covers an overview, affected systems table, data model changes, API and endpoint changes, frontend changes, business logic, edge cases, a testing plan, dependencies, implementation order, and complexity estimates in story points.