aide-implementlisted

Implement the solution for a spec with TDD. **Input:** $ARGUMENTS (all arguments after the command) ## Smart detection Parse `$ARGUMENTS`: **The spec:** the first word is its number, its `TODO-<name>` folder, or an issue key its title began with - Example: `/aide-implement 55` or `/aide-implement TODO-01` **Error handling:** If the argument is missing or has an invalid format, show: ```text Missing argument Usage: /aide-implement 55 # the spec's number /aide-implement TODO-01 # or its folder ``` --- ## Workflow The steps below are this skill's own, inside the queue's `implement` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `implement · Step N of 4: <title> — started`, and when it ends, one line `implement · Step N of 4: <title> — done`. A step that ends the run early says `— stopped: <why>` in place of `— done`, and one that does not apply to this run `— skipped: <why>`. Step 3 also marks each task it takes from the plan, as it finishes it: `implement · Step 3 of 4, task K of M: <task> — done`, where M counts the task rows of `4-status.md`'s GREEN tables. ### Step 1 of 4: Preparation First write `implement · Step 1 of 4: Preparation — started`, and when this step ends, `implement · Step 1 of 4: Preparation — done`. 1. Read `specs/XX-slug/2-analysis.md` (affected files) 2. Read `specs/XX-slug/3-solution.md` (implementation plan) 3. If the spec is MEDIUM/HIGH and `3-solution.md` has no "Plan