17 lines
1.1 KiB
Markdown
17 lines
1.1 KiB
Markdown
---
|
|
name: implement
|
|
description: "Implement a piece of work based on a spec or set of tickets."
|
|
---
|
|
|
|
Implement the work described by the user in the spec or tickets.
|
|
|
|
Before editing, record the starting commit, the original spec/acceptance criteria, and existing worktree changes. Keep a task-owned path/patch list so verification can separate your work from unrelated changes.
|
|
|
|
Use /tdd when test-first work is requested or useful. Reuse established test seams and infer routine choices from the existing tests; ask only about consequential unresolved design decisions.
|
|
|
|
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
|
|
|
|
Once done, use /code-review with the original spec, recorded baseline, and task-owned paths/patch. Request the current working result, including staged, unstaged, and new files, rather than a HEAD-only review.
|
|
|
|
Commit task-owned changes only when committing is part of the requested workflow; otherwise hand off the verified diff. Preserve unrelated staged and unstaged work. A request to commit already supplies that authority; do not ask again or infer permission to push.
|