implementlisted

# Implement a Change A four-step workflow for implementing improvements: **plan**, **execute**, **verify**, **commit**. Use this for focused changes (a few files, clear scope) where the full `/pipeline` would be overkill. When to use this vs. `/pipeline`: if the change needs requirements refinement (PM), architectural decisions (Principal), or touches multiple areas (backend + frontend + infra), use `/pipeline` instead. ## Before Starting Load context about the project and the change: 1. Read `docs/audit/00-project-context.md` if it exists — lint command, test command, framework, conventions. 2. Read `docs/audit/01-architecture.md` if it exists — component map and dependency graph. 3. Read `docs/audit/10-roadmap.md` if it exists — the sequenced improvement plan. 4. Read `pipeline/context.md` if it exists — open questions, prior decisions, fix log. 5. If the project has a AGENTS.md, read the coding standards sections. 6. If none of these exist, ask the user: "What are this project's lint/test commands, and are there coding conventions I should follow?" **Identify what to implement.** The user may: - Name a specific item from the roadmap — look it up in `docs/audit/10-roadmap.md` - Describe the change directly — use their description as the spec - Say "next item" — pick the next unfinished item from the roadmap, respecting the sequence If the scope is unclear, ask before planning. ## Step 1: Plan Write a detailed implementation plan **before touching any code**. The go