1.3 KiB
1.3 KiB
description
| description |
|---|
| Implement an approved OpenSpec change and keep tasks in sync. |
The user wants to apply the following change. Use the openspec instructions to implement the approved change.
$ARGUMENTS **Guardrails** - Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required. - Keep changes tightly scoped to the requested outcome. - Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.Steps Track these steps as TODOs and complete them one by one.
- Read
changes/<id>/proposal.md,design.md(if present), andtasks.mdto confirm scope and acceptance criteria. - Work through tasks sequentially, keeping edits minimal and focused on the requested change.
- Confirm completion before updating statuses—make sure every item in
tasks.mdis finished. - Update the checklist after all work is done so each task is marked
- [x]and reflects reality. - Reference
openspec listoropenspec show <item>when additional context is required.
Reference
- Use
openspec show <id> --json --deltas-onlyif you need additional context from the proposal while implementing.