BUCKYVERSE

Command: done (mark iteration item done)

Use for: done: (optionally with a ## heading, file/line reference, **Id:** ITER-N, or a pasted block that matches one section in work/ITERATION.md)

Prerequisites: Read ../bootstrap.md and ../rules.md first.

Trigger

done: [reference to section in ITERATION.md]

→ Find the referenced section in ITERATION.md
→ Remove that section from ITERATION.md
→ Confirm completion

Workflow

  1. Read ITERATION.md — backfill missing ids per ../id-prefixes.md (Backfill), then locate the referenced section.

  2. Identify the section in work/ITERATION.md per ../procedures/section-disambiguation.md (scope: work/ITERATION.md, id format: ITER-N).

  3. Snapshot the block — Copy the full section text before removing it. Capture the Source and Source id fields from the iteration entry for provenance.

  4. Remove the section from ITERATION.md (preserve file structure)

  5. CHANGELOG — If CHANGELOG.md exists at the workspace root and the completed work is worth recording, update it: add one sentence summarizing the outcome, matching the file's existing style. Do not include the entry id in the CHANGELOG line — describe the change in plain language.

  6. Commit — Stage only the changed work/ file(s) and CHANGELOG.md (when updated). Commit with message xp_work: done ITER-N (using the id of the removed section, e.g. xp_work: done ITER-3). Do not use git add .; only stage specific files that were modified.

  7. Ship Proof gate (conditional) — If the project has a ship-proof skill (check for .claude/skills/ship-proof/SKILL.md), and the done item involved user-visible UI changes, invoke the ship-proof skill. Decide the proof level based on the feature: screenshots for static UI, video for animations/transitions/real-time updates, screenshots + debug-eval for data-flow features. Tell ship-proof what level you chose. Store proof in docs/features_proof/<ITER-N>-<slugified-title>/ and commit separately: ship-proof: <section-title>. If the skill doesn't exist or the item has no UI impact, skip.

  8. Human verification gate — Follow ../procedures/human-verification-gate.md with:

    • source: ITERATION.md
    • source-id: the iteration section's **Id:** ITER-N

    If an ACC-N entry was created, commit with subject: xp_work: queue ACC-N for ITER-N. Only stage work/ACCEPTANCE.md. Then continue to step 9.

  9. Confirm completion by saying "Marked as done and removed from iteration" and:

    • Whether CHANGELOG.md was updated
    • If ship-proof ran, where proof artifacts are stored
    • If ACC-N was created (and that accept: / xp_work accept should be used after the human verifies)