roadmap-planning

This skill generates a sequenced roadmap by clustering 5+ candidate research items into sprint-shaped waves. It applies reconciliation verdicts and PM gating to produce a dependency graph with explicit blocks and blocked_by constraints for reliable execution.

PM gating requires explicit approval on contested architectural decisions before stub authoring begins. You need it when organizing 5+ candidate items into sprint waves to ensure every KEEP verdict materializes with traceable, evidence-backed sources.

You generate sprint sequencing by processing a research corpus through inventory clustering and reconciliation verdicts. The output includes spinoff-roadmap stubs with blocks/blocked_by dependencies, sprint wave sequencing, and an STUB-INDEX for downstream handoff tooling to query and dispatch.

Yes, roadmap planning processes peer-repo deep-dive artifacts and contested architectural decisions by generating evidence-backed research-corpus files. It requires an OVERVIEW with explicit PM approval gates before outputting traceable spinoff stubs.

Yes, roadmap planning requires 5+ candidate items to organize them into sprint-shaped waves. The skill applies when a PM needs items clustered into sequenced dependencies with explicit PM approval gates and evidence-backed research corpus files.

The best way to create machine-readable handoff stubs is generating spinoff-roadmap stubs with blocks/blocked_by dependencies and an STUB-INDEX. This outputs machine-readable handoff readiness that downstream dispatch tooling can query directly for sprint-aware execution.