skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Break down specifications into trackable issues with checklists.

30|2|Updated Feb 13, 2026
Search Tags:#planning#issues#spec#plan#sprint#tracker
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill plan-joestump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/plan
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill plan-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down an existing specification into trackable issues in your issue tracker. Use when the user says "plan a sprint", "create issues from spec", "break down the spec", or wants to turn requirements into tasks.

Core Features & Use Cases

  • Groups requirements into 3-4 story-sized issues by functional area to enable focused development.
  • Supports Scrum mode and a single-agent planning flow, including optional project, branch naming, and PR convention integration.
  • Reads spec.md and design.md to fully understand scope and generates task checklists with governing references.

Quick Start

Provide the capability spec and run /design:plan to split it into 3-4 stories for tracking.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I break down a specification into sprint-ready tasks?▼

To break down a specification into sprint-ready tasks, this Skill reads your spec.md and design.md files to generate 3-4 story-sized issues grouped by functional area. It creates trackable issues with task checklists and wires up branch and PR conventions for downstream work.

What is the best way to create trackable issues from an existing spec?▼

Creating trackable issues from an existing spec is best handled by automatically parsing your specification documents and grouping requirements into focused stories. This approach ensures structured planning and traceability by generating issues complete with governing references and task checklists.

Do I need both spec.md and design.md files to plan a sprint?▼

You need both spec.md and design.md files to plan a sprint using this flow. The Skill reads both documents to fully understand the project scope and architecture before generating grouped stories and applying branch and PR conventions.

How does grouping requirements into story-sized issues work?▼

Grouping requirements into story-sized issues works by categorizing specification details into 3-4 functional areas. This enables focused development by creating trackable issues that include task checklists and governing references for sprint planning.

Can I set up branch and PR conventions when generating tasks from requirements?▼

You can set up branch and PR conventions when generating tasks from requirements. The Skill supports Scrum mode and a single-agent planning flow that wires up project branch naming and pull request conventions for downstream development work.

Related Skills

Explore More Software Engineering Skills→
marcius-llmusmarcius-llmus
1

tlc-spec-driven

Plan software projects into testable specifications and atomic tasks.

Community
Advanced
luanluan
4

graphite

Manage Graphite stacked pull requests with branch creation, syncing, and submission.

Community
Intermediate
markus41markus41
18

jira:branch

Create Git branches with standardized names linked to Jira issues.

Community
Basic
hoonsubinhoonsubin

breakdown-plan

Generate GitHub issues from Epic, Feature, Story, Enabler, and Test hierarchies.

Community
Advanced