buildlisted

Invoke the `incremental-implementation` skill alongside `tdd`. ## Modes - **`/build`** -- implement the *next* pending task, then stop (one slice at a time). - **`/build auto`** -- generate the plan if needed, get a single approval, then implement *every* task without stopping between them. `$ARGUMENTS` selects the mode. Treat `auto` or `all` as autonomous mode; anything else (or empty) is the default single-task mode. Autonomous mode is not faster *per task*; it runs the same test-driven loop but removes the human stepping *between* tasks. ## Default: one task A plan (`tasks/plan.md`) must exist. If none exists, stop and ask the user to run `/plan` first. Pick the next pending task from `tasks/plan.md`. Then: 1. Read the task's acceptance criteria 2. Load relevant context (existing code, patterns, types) 3. Write a failing test for the expected behavior (RED) 4. Implement the minimum code to pass the test (GREEN) 5. Run the full test suite to check for regressions 6. Run the build to verify compilation 7. Commit with a descriptive message (invoke the `commit` skill) 8. Mark the task complete and stop ## Autonomous: the whole plan (`/build auto`) Removes the manual stepping between tasks, **not** the verification. Every task still earns a passing test and its own commit. ### 1. Require a spec Look for a spec at a known path: `SPEC.md` at the repo root, `docs/SPEC.md`, or a file under `spec/`. A README or arbitrary doc does **not** count. If none exists, stop and as