decompose-into-slices

Decompose milestone plans into dependency-ordered vertical slices with GitHub issues export.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill decompose-into-slices-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose-into-slices
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/skills/decompose-into-slices
Command: npx skills add https://github.com/cmetech/otto-cli --skill decompose-into-slices-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a milestone plan into the smallest, independently demoable vertical slices to enable parallel work, early validation, and clear handoffs to implementation.

Core Features & Use Cases

  • Vertical slicing discipline: converts plans into end-to-end slices that span all relevant layers (schema, API, UI, tests).
  • Dependency-aware roadmap: outputs a blocked-by graph to enable safe parallel work and clear sequencing.
  • Output formats: writes M###-ROADMAP.md by default and can export GitHub issues upon explicit confirmation.
  • Use Case: imagine a milestone brief that needs to be broken down into tasks; this enables creating a sliced roadmap with testable deliverables.

Quick Start

Break a milestone plan into end-to-end vertical slices with dependency links and a ready-to-demo 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 break a milestone plan into vertical slices for early validation?

Decompose an approved milestone plan into the smallest end-to-end vertical slices that span schema, API, UI, and tests. Each slice is independently demoable, enabling early validation and clear handoffs to implementation.

What is a vertical slice in roadmap planning, and when do I need it?

A vertical slice is an end-to-end deliverable spanning all relevant layers like schema, API, and UI. You need vertical slicing when converting a milestone plan into testable deliverables to enable parallel work and early demonstration.

How do I generate a dependency graph for parallel development tasks?

Generate a blocked-by dependency graph by decomposing your milestone into ordered vertical slices. The output roadmap explicitly sequences slices like S01 and S02, ensuring safe parallel work and clear task dependencies.

Does this milestone decomposition approach require a specific context file?

Yes, this approach requires an existing milestone brief defined in a M###-CONTEXT.md file and an established roadmap. The decomposition logic applies to approved milestone plans to produce properly ordered, testable slices.

Can I export the sliced roadmap directly to GitHub issues?

Yes, you can export the vertical slices to GitHub issues upon explicit confirmation. The tool writes the M###-ROADMAP.md file by default and optionally creates GitHub issues to track the decomposed milestone tasks.

When should I add a final integration slice to my roadmap?

Add a final integration slice when runtime boundaries are crossed during milestone decomposition. This ensures the vertical slices, which are independently demoable, are properly integrated and tested across the complete system architecture.