/chart

The mapper of the too-big. /tickets cuts known work into slices; when the territory itself is unknown — the decisions that shape everything downstream are still open — slicing is premature. /chart maps the unknowns as tickets, one decision each, and walks them until the fog lifts.

Preconditions

1. The work exceeds confident slicing. The test: could /tickets cut this into tracer-bullet tickets a builder could finish cold? If yes, that is /tickets. If the honest answer is "not until we know X, Y, and Z" — those unknowns are this skill's material.
2. The repo config exists — the map lives on the tracker docs/agentic-skills/tracker.md pins.

Draw the map

1. Name the destination — the capability or state the work aims at, in one sentence.
2. Enumerate the decisions that gate the way — each unknown whose answer changes the shape of everything downstream: architecture choices, build-vs-buy, data model forks, sequencing forks. Each becomes one decision ticket on the tracker: the question, what hangs on it, the options already visible, and which other decision tickets it unblocks (their blocking edges, the way /tickets declares them).
3. Keep the map honest about size — a map of two decisions is a conversation (/grill); a map of forty is a program that needs splitting. Chart the decisions that truly gate; trivia rides with the implementation.

Resolve, one at a time

Work the frontier — the decision ticket whose blockers are all closed goes first, exactly one at a time: