planning

Generates a planning document with sequenced tasks and estimated durations from GitHub issues or other inputs, ready to be saved as PLAN.md in your repository.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/rom-orlovich/agents-system --skill planning-rom-orlovich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/rom-orlovich/agents-system/tree/main/claude-code-cli-poc/planning-agent/.claude/skills/planning
Command: npx skills add https://github.com/rom-orlovich/agents-system --skill planning-rom-orlovich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts discovery inputs and ticket information into a structured, executable planning artifact, reducing ambiguity and accelerating delivery.

Core Features & Use Cases

  • Generate a complete implementation plan from discovery results and Jira tickets.
  • Create a PLAN.md template with scope, architecture, risks, and testing strategies.
  • Prepare Draft PRs and Jira comments to align stakeholders before implementation.
  • Break down work into tasks with estimated hours and dependencies for sprint planning.

Quick Start

Use this skill on a Jira ticket to generate PLAN.md, draft a PR, and update the ticket with a summary of the plan.

Frequently Asked Questions about 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?

Task breakdown for sprint planning involves converting discovery results into a list of manageable tasks with estimated hours and dependencies. This structured breakdown reduces ambiguity and accelerates delivery by clarifying exactly what needs to be done.

Can I prepare a Draft PR before starting implementation?

Yes, you can prepare a Draft PR before implementation to align stakeholders early. Using the GitHub MCP, the skill generates a draft pull request alongside a PLAN.md file to establish context and scope prior to writing code.

What is the best way to turn discovery results into an executable plan?

Yes, you can prepare a Draft PR using GitHub MCP before implementation to align stakeholders early. The skill generates a draft pull request alongside a PLAN.md file to establish context and scope prior to writing code.

How do I break down work into tasks with estimates for sprint planning?

Breaking down work for sprint planning involves converting discovery inputs into a structured task list with estimated hours and dependencies. This clarifies the scope of each ticket and produces a manageable breakdown for execution.

Does generating a planning artifact require a Jira ticket to work?

No, generating a planning artifact does not strictly require a Jira ticket. The skill creates a PLAN.md from discovery results, but it also supports Jira updates and ticket scoping if that platform is part of your workflow.