What problem does it solve? Large migrations, refactors, and specs that exceed one agent session tempt linear plans that commit a build order before key unknowns are resolved, collapsing when the first unknown surfaces. This Skill charts the unknowns as a map of investigation tickets and resolves them one per session until the build order is clear. ## Core Features & Use Cases - Destination-first charting: Name the destination, sketch the fog breadth-first, and cut only the tickets sharp enough to specify, leaving the rest as Not-yet-specified fog. - Solo MAP.md default: Track tickets, blocking edges, the frontier, and decisions in a local markdown file, with a mode-switch up to GitHub Issues or Linear only when a real tracker exists. - Typed tickets with routing: Research, prototype, decision, and task tickets each route to the appropriate downstream skill, with one ticket resolved per session and a handoff at the end. - Use Case: For a Pages-to-App-Router migration, chart research tickets on auth and data-fetching first, block the order-committing decision behind them, and graduate fog into tickets as answers sharpen. ## Quick Start Ask the agent to map out the migration or refactor as investigation tickets in a MAP.md file, resolving one frontier ticket per session.
