claude-sdk-rs: Command for Claude Code

Update Task — Record progress in a task spec.

Variables

$ARGUMENTS — space-separated values in this order:

1. Target spec identifier, e.g. <spec-slug> (optional — if omitted, auto-detects the current spec from planning/status.md).
2. Step number to mark done, e.g. 3. Pass 0 to append a note without marking a step.
3. Note text (everything after the step number) to append to the spec's Amendment Log, in planning/<spec-slug>/amendments.md — a sibling file to tasks.md/tasks.json, never inside tasks.md itself.

Examples: /update-task 3 Finished scaffolding ← auto-detect spec, mark step 3, log amendment /update-task 0 Still investigating the failing edge case ← auto-detect spec, amendment only /update-task <spec-slug> 2 Fixed the retired model id in frontmatter ← explicit spec, mark step 2, log amendment /update-task <spec-slug> 0 Investigating the failing edge case ← explicit spec, amendment only

Execution Model

Run entirely inline. Spawn no subagent. This is a single-file mark-done-and-append-note edit — a subagent round trip adds latency without adding value.

Instructions

1. Resolve the target spec.

   • If the first token of $ARGUMENTS matches a spec identifier pattern (e.g. <spec-slug>, <spec-slug>), resolve to planning/<name>/tasks.md and verify the file exists. If it does not exist, stop:

     "No spec found at planning//tasks.md — run /generate-tasks <name> to create it."

   • Otherwise (first token is a number or $ARGUMENTS is empty), read planning/status.md to identify the current spec and load it. If no spec exists, say so and stop.

2. Parse the remaining arguments:

   • Step number: first integer token after the (optional) spec identifier. 0 = note-only.
   • Note text: all remaining text after the step number. May be empty.

3. Read the task spec.

4. If a non-zero step number was given, mark that step heading done by prepending [done] to the matching ### <N>. line. If the step is already marked done, report that and skip.