apw-implementlisted

Use this skill when asked to implement a feature, fix, or any change. Follow the steps below strictly and in order. ## Step 1 — Familiarize Before doing anything else, read everything relevant to the task: - Existing codebase files related to the area of change - API docs, external documentation, or specs if the task touches integrations - Any prior work (recent commits, related code) that could affect the approach - Any planning artifact for this task — if your work item's `plan.md` artifact exists (from `apw-plan`; see `apw-work-with-work-item-artifacts` for where it lives), it is your task list and source of intent; read it, along with any `requirements.md` / `design.md` it references - If the task is a fix, any diagnosis artifact — if your work item's `root-cause.md` artifact exists (from `apw-find-root-cause`; see `apw-work-with-work-item-artifacts` for where it lives), it names the proven defect the fix must address; read it before deciding the approach Do not skip this step, even if the task looks simple. The goal is to have a complete picture before forming any opinion. ## Step 2 — Ask questions (up to 5, only if needed) If anything is unclear after familiarizing yourself, ask up to 5 targeted questions. Questions should resolve genuine ambiguity that would change the implementation approach. Skip this step entirely if the task is clear after Step 1. Do not ask questions for the sake of asking. ## Step 3 — Present a mini plan and confirm Write a concise plan t