What problem does it solve? Running roadmap chunks one at a time misses what only exists between chunks: a landed chunk can subsume queued work, dependency satisfaction changes which chunk is ready next, and setup costs repeat. This Skill advances several roadmap chunks in a single session while preserving per-chunk atomicity — each chunk keeps its own think open/close, ship objective, quality gates, and commit. ## Core Features & Use Cases - Frontier selection: Builds a candidate set of pending, unblocked, dependency-satisfied chunks and filters out human-gated, exploratory, or backlogged work, stating every exclusion. - Between-chunk subsumption: After each chunk lands, checks whether remaining queued chunks are still necessary and obsoletes dead ones with measurement-backed reasons via roadmap_obsolete_chunk. - Explicit stop conditions: Halts the run on red gates, human decisions, scope explosion, falsified plans, budget exhaustion, or low context, and always emits a handoff prompt. - Use Case: A user types "/roadmap-run perf" to knock out the performance-related chunks; the Skill plans the ordered set, executes each under the full per-chunk contract, obsoletes two chunks made moot by a 64x-cheaper solve, and reports a ledger with commits and gate results. ## Quick Start Type /roadmap-run followed by a count, theme, chunk ids, or an until-condition to advance several roadmap chunks in one session.
