What problem does it solve?
Fuzzy, half-formed ideas often stall because open questions get lost between sessions or get tackled in the wrong order. This Skill turns a vague idea into a persistent, git-tracked decision map of typed investigation tickets with explicit blocking edges, so planning survives across sessions and each ticket is resolved in a valid order.
Core Features & Use Cases
- Session-Resumable Planning Maps: Stores the entire planning effort in one Markdown file at
.planning/decision-maps/<slug>.md, reloaded whole at the start of every session.
- Typed Investigation Tickets: Supports Research, Prototype, and Grilling ticket types, each with declared blockers, a question, and an inline resolution recording the decision and its reasoning.
- Graduation to Buildable Work: Resolved tickets that produce buildable outcomes are graduated into
.planning/intake/ items for downstream autopilot or campaign execution.
- Use Case: You have an idea for a new feature but several unknowns about APIs, UX, and architecture. Bootstrap a decision map, then resolve one ticket per session until every question is answered and the resulting intake items are ready to build.
Quick Start
Ask the agent to create a decision map for your idea, for example: "Plan this out — create a decision map for adding real-time collaboration to the editor."
