apw-planlisted

Use this skill when a task needs to be turned into a plan *before* anyone starts building it. It is the upstream companion to `apw-implement` and the downstream consumer of `apw-research` / `apw-brainstorm`: it takes a fuzzy brief (plus any docs or prior artifacts) and produces durable planning documents an implementation can execute against. It exists to fight two failures: jumping into code with the whole plan held only in volatile context — so steps get skipped and the work drifts from the original ask — and producing a plan that loses the thread of the requirements it was supposed to satisfy. Follow the steps below strictly and in order. ## Step 1 — Absorb the inputs Before forming any plan, read everything that defines the task: - **The brief** — the task description, ticket, or request as given. - **Provided material** — any docs, specs, designs, or references handed in with it. - **Prior artifacts** — if your work item's `research.md` or `brainstorm.md` artifacts exist (see `apw-work-with-work-item-artifacts` for where they live), the plan **builds on them**, it does not redo their work. - **The codebase** — the files, modules, and conventions the work will touch, so the plan fits reality instead of an imagined architecture. Do not skip this step, even if the task looks small. A plan is only as good as the picture behind it. ## Step 2 — State your understanding, ask, and choose depth First, write a **concise statement of what you understand needs to be done** — t