aide-analyzelisted

Analyze the codebase for a spec. **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-analyze 55` or `/aide-analyze TODO-01` **Error handling:** If the argument is missing or has an invalid format, show: ```text Missing argument Usage: /aide-analyze 55 # the spec's number /aide-analyze TODO-01 # or its folder Examples: /aide-analyze 55 ``` --- ## Workflow The steps below are this skill's own, inside the queue's `analyze` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `analyze · Step N of X: <title> — started`, and when it ends, one line `analyze · Step N of X: <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 1 of 9: Read the description First write `analyze · Step 1 of 9: Read the description — started`, and when this step ends, `analyze · Step 1 of 9: Read the description — done`. - Read `specs/XX-slug/1-description.md` - Read `.aide/project.yaml` in the project root if it exists — the project manifest gives deployment, logging and dependency context the analysis should use (refresh it with `/aide-manifest`) - **Read the project's wiki, when it has one, before anything else — in a later round too, before the