decompose-into-slices

To break a plan into vertical slices, you need to decompose the approved milestone brief into thin, end-to-end actionable tasks that cut through multiple layers like schema, API, and UI, generating a clear M###-ROADMAP.md document for collaboration.

Vertical slices in project planning are thin, end-to-end work units that cut through multiple layers and can be demonstrated individually. You need them when decomposing a milestone into parallel, dependent tasks to establish a clear execution roadmap.

To generate a roadmap template and decompose plans into slices, you need a stable milestone brief with established consensus scope, which is then exported to the M###-ROADMAP.md document format for team collaboration.

You create a milestone roadmap by decomposing an approved plan into independently-grabbable vertical slices with clear dependency ordering. This produces an M###-ROADMAP.md artifact that enables parallel execution across the team.

Yes, you can wire slices into GitHub issues. When generating the M###-ROADMAP.md template from your decomposed milestone, GitHub issue wiring is supported if explicit confirmation is provided during the process.

Slice decomposition requires a stable brief and a consensus scope before execution. If the milestone brief is not finalized, the generated vertical slices and the resulting M###-ROADMAP.md will lack the necessary dependency ordering for parallel work.