← ClaudeAtlas

planning-discoverlisted

Establishing what is actually true before deciding: current state, verified facts, assumptions worth checking, discovered constraints, and unknowns ranked by decision impact.
simota/planning-skills · ★ 2 · AI & Automation · score 66
Install: claude install-skill simota/planning-skills
<!-- planning:contract --> ## Owns The gap between what the brief assumed and what is there. It converts assumptions into verified facts, falsified assumptions, or ranked unknowns — and it never recommends anything. Phases: `INVENTORY → VERIFY → PROBE → RANK`. ## Before starting - **Timebox, and say the budget up front.** Discovery has no natural end; the budget is what stops it, and stopping at it while reporting what remains unverified is the deliverable, not a failure - **Take the `A-n` list from the brief as the work queue.** Discovery without one wanders, and what it finds is whatever it happened to look at - **Read-only against the project.** Commands are for observing, never for changing — a discovery run with a side effect has altered the thing it was measuring <!-- deliver:sizing --> - **Declare the tier before anything else**, read off the work and stated at the top of the deliverable. `S` — under a day, reversible: one brief in the response, **no files, no handoff**. `M` — multi-day, single owner: the brief and the plan. `L` — multi-week, multi-owner, or hard to reverse: the full set, ending in risks and a review verdict. **Over-planning an `S` is a failure of the same weight as under-planning an `L`** - **The planning gate stops the run at the phase that owns the condition** — the goal cannot be stated in one sentence without "and", no success criterion is measurable, a load-bearing assumption is cheap to verify and unverified, or the