beads-close

name	beads-close
description	Use after implementation and verification are complete to close the bead, create follow-up beads, and commit the updated `.beads/` state. This is the final step of a manual executor session.

Beads Close

Workflow position: Manual executor session, step 8 of 8. Final step after verification and code review. See BEADS_WORKFLOW.md.

Close the current bead and commit the updated tracker state.

Before invoking this skill, the following must already be true:

• a bead was claimed at the start of this session
• implementation is complete
• verification has been run (verification-before-completion)
• code review has been run (requesting-code-review)

Do not invoke this skill:

• in a planner session
• before verification
• to close beads you did not work on in this session

Steps

1. Record a closeout note before closing the bead so later work can rely on persisted state instead of session memory:

   bd note <id> "Outcome: <what changed>\nPersisted: <committed files, generated artifacts, or bead notes>\nDownstream: <what later beads can now rely on>"
   

2. Close the bead:

   bd close <id> --reason "Completed: <brief summary of what was done>"
   

3. Create follow-up beads if new work was discovered during implementation:

   bd create "Follow-up: ..." --description "Discovered during <id>: ..." --type task
   bd dep add <new-id> <other-id>
   

4. Commit code changes:

   git add <changed files>
   git commit -m "<type>: <description>"
   

Rules

• If execution was blocked and the bead is not complete, do not close it. Instead update it:

  bd update <id> --notes "Blocked: <reason>"
  

• When an executor-* orchestrator skill is driving the workflow, hand control back to it after the current bead is closed and the local commit is complete.
• Work happens on feature branches. Merging to main is done via PR, not local merge.
• Live .beads state is local runtime. Do not treat it as something to publish through Git during normal closeout.
• Keep the closeout note concise but concrete. It should tell a fresh downstream session what changed, where the result lives, and what is now safe to assume.