map-melisted

Build the comprehension map across every ship-me run in this project and read it back in plain language. Runs a deterministic script over the markdown the pipeline already wrote (grill-me's R-numbers, solve-me's sub-problems and options, build-me's commits and touched files, verify-me's coverage table) and turns them into a graph: one node per requirement, sub-problem, option, commit, mid-build decision and touched file. Its real job is the holes — requirements nothing built, requirements nothing proved, commits tied to no requirement, decisions made mid-build that never went through a gate, and files where several runs collide. Use when the developer wants the big picture, wants to know what a run actually left behind, or is about to start work in a part of the code several runs have already touched.
Kerliula/ship-me · ★ 1 · AI & Automation · score 72

Install: claude install-skill Kerliula/ship-me

# Map Me — Show the Holes The structure of the work is already readable in the four markdown files. The **holes** are not. That's what this skill is for. You invent nothing here. Every node and edge is already written down by `/grill-me`, `/solve-me`, `/build-me` and `/verify-me`. A script parses them; your job is to read the result back in plain language and say which holes actually matter. **A script parses, you narrate.** Never hand-derive the graph by reading the artifacts yourself — it's slow, it drifts between runs, and the whole value of the map is that it says the same thing every time. --- ## Step 1 — Run the generator The script ships next to this file. From the project root: ```bash node ~/.claude/skills/map-me/map-me.mjs ``` If the skills were installed into a single project, use `.claude/skills/map-me/map-me.mjs` instead. Options: - `--docs <dir>` — where the artifacts live (default `docs`) - `--out <dir>` — where the map goes (default `<docs>/map`) - `--slug <slug>` — map one run only - `--brief` — print only what changed since the last run - `--quiet` — no stdout summary ### Two modes `/map-me` invoked by the developer uses the **full** mode above: it rebuilds everything and you read the holes back in priority order. The other five skills call the same script with `--brief` every time they write an artifact, so the map is never stale mid-pipeline. In that mode it prints only the holes that opened or closed since the last run, and prints nothing at