apw-gather-requirementslisted

Use this skill when a task is handed in with only a description and some details, and the requirements need to be drawn out before anything is planned or built. It is an upstream front-door that produces a durable `requirements.md` an `apw-plan` or `apw-implement` can then consume. It works as a question loop: each round surfaces the few highest-impact unknowns, the user either answers them or calls for the doc, and the picture is refined until the user decides it is complete enough to write down. Follow the steps below strictly and in order. ## Output style When this skill asks for a plan, report, summary, status update, or other chat-facing output, prefer bullet points or numbered lists over plain paragraphs. Keep each item concise and content-bearing. Omit language that only smooths tone, repeats context, or adds "language sugar" without changing the meaning. ## Step 1 — Familiarize Before asking anything, read everything that defines the task: - **The brief** — the task description and any details the user handed in. - **Related code** — the files, modules, and conventions the work would touch, if any exist, so questions are grounded in reality instead of guesses. - **Prior artifacts** — if your work item already has a `research.md` or `brainstorm.md` (see `apw-work-with-work-item-artifacts` for where they live), read them; they may already answer questions you would otherwise ask. Do not skip this step, even if the task looks small. The point is to spend the user's