aide-implement

Topics in the source

• Smart detection
• A project with a board
• Workflow
• Before Step 1: a merge left open for you
• Step 1 of 4: Preparation
• Step 2 of 4: RED — Write failing tests
• Step 3 of 4: GREEN — Implement until tests pass
• Step 4 of 4: VERIFY — Full suite, types, lint, build

Implement the solution for a spec with TDD. Input: $ARGUMENTS (all arguments after the command) Parse $ARGUMENTS: The spec: the first word is its number, its folder name, or an issue key its title began with Example: /aide-implement 55 or /aide-implement 55-dark-mode Error handling: If the argument is missing or has an invalid format, show: -- Working interactively, hand the step to the board first: Exit 3, or no such command: go on with Step 1. Any other exit: its output is your last words; do nothing else. -- 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 --- Step N of 4: — started, and when it ends, one line --- Step N of 4: — done. A step that ends the run early says — stopped: in place of — done, and one that does not apply to this run — skipped: . Step 3 also marks each task it takes from the plan, as it finishes it: --- Step 3 of 4, task K of M: — done, where M counts the task rows of 4-status.md's GREEN tables. When aide-run-spec could not bring the spec's branch up to date with the default branch, it starts this step with the merge still open in the worktrees

This is an excerpt. Refer to the complete source and its current requirements.