implement-feature
Purpose
Use this skill after /start-feature closes spec-reconcile. Accept the same human feature selectors as
/start-feature. Beads selects executable work; design.md supplies intended behavior and design constraints. Resolve
<core-dir> as the installed ../dstack-core skill directory. If the supplied selector resolves to a standalone
task, bug, chore, spike, or feature rather than a child of a reviewed workflow:feature epic, stop before
claiming it and recommend /implement-task <human task selector>.
Invocation authorizes bounded local implementation commits, one startup interaction-evidence commit for the selected root when needed, and one interaction-only audit commit after every child and the implementation coordinator. It does not authorize pushes, pull requests, merges, or worktree removal, and it does not authorize remote delivery.
Shared native Beads authority
Read ../dstack-core/references/INTERACTION-BOUNDARY.md before
mutating the feature. Native linked-worktree Beads authority is shared; bd -C is not an isolation boundary. Run each
claim/close/evidence/finalization interval under beads-workflow-lock.py, and stop on a busy lease, foreign interaction
row, or snapshot race. Never use a raw bd write to bypass the lease or copy another feature's audit evidence.