implement-feature

Implement Feature (SAM Workflow Execution)

This workflow continues from add-new-feature. It executes tasks from the selected provider until complete or blocked.

<plan_ref>$ARGUMENTS</plan_ref>

Load dh:dh-cli-usage before using <sam_cli/> or <dh_scripts/> below.

---

Where task state lives: every command that moves a task — ready, dispatch, settle, read, accept, reclaim, state, status — runs through the <sam_cli/> command above, against the work ledger. The sam_plan and sam_task MCP tools answer from the content store, which holds the plan's authored content and none of the attempt, lease, or outcome state this loop turns on, so this workflow reaches task state through the CLI.

MCP server availability: This skill uses mcp__plugin_dh_backlog__* tools for backlog items and artifacts. The server initializes in ~1–2 seconds after a session restart, and Claude Code handles connection waiting automatically. If a tool is unavailable, load dh:dh-cli-usage and follow its MCP connection check.

Resolve Plan

Treat the value from the plan_ref key as an opaque reference. Pass it unchanged to every SAM operation and delegation prompt.

Confirm the plan exists:

<sam_cli/> plan status --plan-address "{plan_ref}"

Put the Plan in the Ledger

The loop below opens an attempt per task, and an attempt is a ledger row. A plan authored through the SAM plan operations lives in the content store, where there is nothing to open — plan dispatch on such a plan answers no task {plan_ref}/{task_id} in the ledger and the wave cannot start. Bring the plan across before the first dispatch:

<sam_cli/> plan import --from content --plan-address "{plan_ref}"

This is safe to run when you are unsure: a plan the ledger already holds answers exists and changes nothing. Once it has run, every plan command naming this address reads and writes the ledger — including the status command above, which then reports the ledger's own columns.