What problem does it solve? Large, fuzzy efforts that span multiple sessions often stall because the open questions outnumber the known steps and a single planning pass would guess or stall. This Skill charts such efforts as a shared map of decision tickets on the repo's issue tracker, then resolves them one per session until the route to the destination is clear. ## Core Features & Use Cases - Map charting: Interviews the user to pin the destination, surfaces open decisions breadth-first, and creates a map issue plus child decision tickets with blocking edges. - Ticket-driven sessions: Each session claims one frontier ticket (research, prototype, interview, or task), resolves it, records the decision, and graduates newly sharpened fog into fresh tickets. - Tracker flexibility: Resolves the tracker from project docs, GitHub Issues via the gh CLI, or local markdown files, with a write gate requiring user confirmation before publishing shared tracker state. - Use Case: A team faces a vague multi-week migration idea. The Skill charts a decision map on GitHub Issues, and each subsequent session works one ticket until every decision blocking implementation is resolved. ## Quick Start Ask the agent to chart this effort as a decision map on the issue tracker before any implementation begins.
