apw-tech-designlisted

Use this skill when a task needs a *technical solution design* before anyone starts building it. It sits between open-ended ideation (`apw-brainstorm`) and full planning (`apw-plan`): it takes a task description, explores the codebase and constraints, then converges to a concrete technical recommendation the user can confirm before any detailed planning or code begins. 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 forming any opinion, read everything relevant to the task: - **The task description** — exactly what needs to be built or changed. - **The codebase** — files, modules, and conventions the change will touch; existing patterns that constrain or enable each option. - **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), read them; the design builds on them, it does not redo their work. - **External constraints** — API contracts, dependencies, performance requirements, or anything else that would make an option non-viable. Do not skip this step, even if the task looks small. An option that ignores an existing patter