Take a **specification** and the **set of tickets** that implement it, and produce one build/sequencing plan: a dependency graph that fixes completion order, a recommended wave ordering with the critical path, and a coverage matrix that cross-references every spec element against the tickets to **surface gaps**. The plan is a markdown artefact the user reviews and shares; it is not the spec, not the tickets, and not the implementation.
