decomposing-into-milestones

Decomposes design docs into INVEST-compliant GitHub Project cards with vertical slicing.

2|Updated Apr 24, 2026

Search Tags:#planning #decomposition #invest #design-doc #project-cards #vertical-slicing

Ready to run

npx skills add https://github.com/PanQiWei/board-superpowers --skill decomposing-into-milestones

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decomposing-into-milestones
Source: https://github.com/PanQiWei/board-superpowers/tree/main/archive/skills/decomposing-into-milestones
Command: npx skills add https://github.com/PanQiWei/board-superpowers --skill decomposing-into-milestones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decompose a design document into a set of INVEST-compliant GitHub Project cards that map end-to-end capabilities, enabling a single Consumer session to deliver work in one PR.

Core Features & Use Cases

Decomposes a design doc into INVEST-compliant cards capturing end-to-end capabilities.
Enforces vertical slicing and explicit dependencies to avoid big-bang merges.
Produces ready-to-use card bodies with context, acceptance criteria, and scope for quick board setup.

Quick Start

Feed the design doc to the skill and it will generate initial card bodies for the first vertical slice.

Frequently Asked Questions about decomposing-into-milestones

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

FAQPage Schema

How do I decompose a design doc into GitHub project cards?▼

To decompose a design doc into GitHub project cards, feed the document into the skill to generate INVEST-compliant card bodies. Each card includes Context, Acceptance Criteria, Out of Scope, Size, and Execution Hints for ready-to-use board setup.

What is vertical slicing in project planning and why use it?▼

Vertical slicing in project planning breaks end-to-end capabilities into thinnest demonstrable segments. It enforces explicit dependencies to avoid big-bang merges, enabling a single session to deliver work in one PR.

Can I generate INVEST-compliant project cards from an existing design document?▼

Yes, you can generate INVEST-compliant project cards by feeding an existing design document into the skill. It automatically maps capabilities and outputs cards with a machine-readable marker for quick board initialization.

What's the best way to structure project cards to avoid big-bang merges?▼

The best way to avoid big-bang merges is applying vertical slicing to project cards. This prioritizes the thinnest demonstrable card first and maps subsequent slices with explicit dependencies for single-PR delivery.

Do I need a specific format for my design doc to generate project cards?▼

No specific external dependencies are required. You need a design document capturing end-to-end capabilities; the skill processes it directly to output structured GitHub Project cards with context, scope, and sizing.