plan-maplisted

# Plan Map A plan gets read once, by someone deciding whether to let it run. The map takes the place of the document for that decision. The detail stays in the document — the map points at it, it never copies it. **The test: if the reader still has to open the plan to decide, the map failed.** ## What You Produce Both, every time: 1. **In the conversation: ten lines at most.** What gets built, in what order, what you need from them. Then the path to the map. 2. **One HTML file.** Copy `template.html` from this skill's directory and fill it in. Never write your own CSS and never edit the stylesheet — the template owns how it looks, you own what it says. If the plan is a straight line of five steps or fewer, it has no shape worth drawing. Say it in five lines and write no file. ## What the Map Must Answer Five questions, on its own. Each has a place in the template. If any of them sends the reader to the document, the map is not finished. | Question | Where it goes | |---|---| | What will exist when this is done? | the boxes | | In what order, and what runs at the same time? | the phases | | How much work is this? | the count on each phase, the totals in the footer | | What could go wrong? | **Most likely to be wrong** | | What do you need from me? | **Your call** | | What is this *not* going to do? | **Not in this plan** | ## Filling the Template **Lede**: one sentence, what the reader gets when this is done. Anything you learned that does not fit in one sentence be