skills.rest
fyodoriv
fyodorivCOMMUNITY
Explore all skills by this author →
GitHub

plan

Convert Jira tickets into structured plans with file maps and task chunks.

Updated Aug 23, 2026
Search Tags:#planning#decomposition#jira#ticket#planning-template#task-splitting
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill plan-fyodoriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/plan
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill plan-fyodoriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and scoping complex features becomes reproducible by breaking ideas into concrete specs, tasks, and incremental chunks, enabling predictable delivery.

Core Features & Use Cases

  • Structured ticket decomposition: convert a Jira issue into a clear set of tasks and milestones.
  • Risk, scope, and size: identify risks, define success criteria, and estimate effort in a repeatable manner.
  • Execution handoff: produce a plan that includes file maps, task templates, and acceptance criteria for teams to implement.

Quick Start

Generate a structured plan from a Jira ticket, including a file map, task chunks, and risk notes.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I break down complex Jira tickets into actionable tasks?▼

Ticket decomposition breaks complex features into structured, testable chunks by generating a file map, task templates, and milestones. This converts vague requirements into clear execution steps with defined acceptance criteria for teams.

What is the best way to scope software features and identify project risks?▼

Feature scoping identifies risks, defines success criteria, and estimates effort in a repeatable manner. It maps dependencies and outlines execution steps to ensure predictable delivery across teams before implementation begins.

How do I create a planning template for task splitting across teams?▼

Task splitting uses planning templates to map files, dependencies, and chunk templates across teams. It produces a structured plan with incremental chunks and execution handoff notes, ensuring reproducible feature delivery.

Can I generate a file map and acceptance criteria from a single feature spec?▼

Yes, feature specs are converted into execution handoff plans that include file maps, task chunks, and acceptance criteria. This ensures teams receive concrete implementation guidance and testable milestones directly from the spec.

Does structured feature planning work for incremental delivery and milestone tracking?▼

Structured planning supports incremental delivery by breaking ideas into concrete specs, tasks, and chunks. It defines milestones and success criteria, making delivery predictable and progress measurable across teams.

Related Skills

Explore More Product & Management Skills→
aurora-atomsaurora-atoms

feature-spec-author

Draft bounded feature specifications and feature_delivery_case JSONL records from requirements.

Community
Intermediate
X-School-AcademyX-School-Academy
19

dev-swarm-stage-sprints

Plan agile sprints by breaking product requirements into backlogs with acceptance criteria and test plans.

Official
Advanced
voidreadervoidreader

milestone-runner

Coordinate milestone execution state for multi-phase AI development workflows.

Community
Advanced
Productfculty-aipmProductfculty-aipm
70

user-story-decomposition

Break features or PRDs into INVEST user stories with Gherkin acceptance criteria.

Community
Intermediate