Skip to content

/implement (L3)

Execute a beads issue by ID. Marks in_progress, makes changes, validates, commits, closes.

Usage

Text Only
/implement <issue-id>
/implement agentops-abc

What's Different from L2

At L3, implementation is issue-driven: - Specify which issue to work on - Issue marked in_progress automatically - Issue closed after successful commit - Dependencies enforced (blocked issues can't start)

Steps

  1. Claude marks issue in_progress
  2. Claude reads issue details and makes changes
  3. Validation runs (tests, lint)
  4. Changes committed with issue reference
  5. Claude closes issue with bd close

Output

Text Only
Implementing: agentops-abc "Add theme context provider"

[Read, Edit, Test...]

$ git commit -m "feat: add theme context provider

Closes: agentops-abc"

$ bd close agentops-abc --reason "Theme context implemented"

✓ agentops-abc closed
Next ready: agentops-def (was blocked by abc)

Example

Text Only
You: /implement agentops-abc

Claude: Working on agentops-abc: "Add theme context provider"

$ bd update agentops-abc --status in_progress

[Reads requirements, creates src/theme/context.tsx...]

$ npm test
4 passed

$ git commit -m "feat: add theme context provider"
$ bd close agentops-abc

✓ Done. Run `bd ready` for next issue.

Session Close Protocol

Before ending, always run:

Text Only
bd vc status   # Optional Dolt status check
git push

Next

  • bd ready - See newly unblocked issues
  • /implement <next-id> - Continue through the plan