decompose-into-slices

Decompose milestone briefs into dependency-ordered vertical slices and generate ROADMAP.md.

12|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/qdzsh/gsd-revamp --skill decompose-into-slices
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decompose-into-slices
Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/decompose-into-slices
Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill decompose-into-slices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a milestone brief into independently actionable vertical slices that collectively cover end-to-end delivery, enabling parallel work and clear traceability.

Core Features & Use Cases

  • Vertical slicing discipline: converts high-level plans into many thin, end-to-end slices with explicit dependencies.
  • Roadmap generation: outputs a structured M###-ROADMAP.md by default for project tracking.
  • Optional GitHub integration: can export slices as GitHub issues when explicitly confirmed by the user.

Quick Start

Provide a milestone brief and allow the tool to generate a vertical-slice roadmap.

Frequently Asked Questions about decompose-into-slices

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

FAQPage Schema
How do I decompose a project milestone into vertical slices?▼

You provide a milestone brief and the tool drafts a dependency-ordered set of independently end-to-end vertical slices. This breaks down high-level plans into thin, actionable items that enable parallel work and clear traceability.

What is vertical slicing in software planning and when should I use it?▼

Vertical slicing converts high-level plans into many thin, end-to-end slices with explicit dependencies. Use it when you have a stable plan and need to break a milestone brief into independently actionable items covering end-to-end delivery.

Do I need a stable roadmap before generating vertical slices?▼

Yes, you need a stable plan before generating vertical slices, specifically an existing M###-CONTEXT.md and a ROADMAP. The tool applies after this stable plan exists to draft a dependency-ordered set of slices for project tracking.

Can I export generated slices directly to GitHub issues?▼

Yes, you can export slices as GitHub issues when explicitly confirmed by the user. The tool offers optional GitHub integration to generate these issues alongside outputting a structured M###-ROADMAP.md by default.

How are runtime boundaries handled when decomposing sprints into slices?▼

When runtime boundaries are crossed, the tool enforces a final integration or milestone-level slice. This ensures the dependency-ordered set of vertical slices collectively covers complete end-to-end delivery without missing integration steps.