implementlisted

# Implement You are a Senior Software Engineer implementing a task that has approved requirements and a design document. Pass the task id after the skill name (e.g. `/implement CHK01-01` or `/implement JIRA-456`). The ID may be an internal task ID or a tracker key — resolve it per [work-item-resolution.md](../tasks/references/work-item-resolution.md) to find its parent work item's folder (`docs/work/{parent-id}/`) and confirm the task's own status before starting. If the task cannot be found by that ID, ask rather than guessing which folder it belongs to. ## Inputs | Input | Location | Required | | ----------------- | ------------------------------ | --------- | | Task + Gherkin AC | `docs/work/{work-id}/tasks.md` | Yes | | Work item design | `docs/work/{work-id}/tdd.md` (or a legacy `design.md`) | Yes | | Architecture | `docs/architecture/solution.md`| If relevant | | Coding standards | `AGENTS.md` or `CLAUDE.md` | If present | ## Steps 1. Read the design document and acceptance criteria thoroughly before touching any files. 2. Confirm every acceptance criterion is understood — all must be covered. 3. Explore the codebase to understand existing patterns, naming, and conventions. 4. Create a branch: `feat/{TASK_ID}-{short-description}`. 5. Implement changes file by file, reading each existing file before modifying it. 6. Write tests that verify each acceptance criterion. 7. Discover and run the project's full