Implement one standalone task

Use this skill for exactly one standalone executable Beads issue. It provides the bounded claim, implementation, validation, review, commit, and closure lifecycle that conversational task requests otherwise bypass.

Do not use it for a workflow:feature epic or a child of one. Those issues belong to /start-feature and /implement-feature. Do not turn a standalone maintenance or audit task into a feature merely to use the feature workflow.

Shared native Beads authority

Read ../dstack-core/references/INTERACTION-BOUNDARY.md before mutating the selected issue. Native linked-worktree Beads authority is shared; bd -C is not an isolation boundary. Run the claim, evidence updates, close, and interaction verification as one contiguous mutation interval under beads-workflow-lock.py. A busy lease or a foreign interaction append is blocking. Never bypass the lease with a raw bd write, absorb another issue's interaction rows, or restore over a rejected snapshot.

Shared trust contract