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>

<sam_cli> uv run "${CLAUDE_PLUGIN_ROOT}/sam_schema/cli.py" </sam_cli>

<mcp_server_scripts> SAM server: uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/run_sam_server.py" Backlog server: uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/run_backlog_server.py" --project-dir . </mcp_server_scripts>

---

MCP server availability: This skill uses both mcp__plugin_dh_backlog__* and mcp__plugin_dh_sam__* tools. Both servers initialize in ~1–2 seconds after a session restart. Claude Code handles connection waiting automatically. If a tool is unavailable, see the troubleshooting steps at ${CLAUDE_PLUGIN_ROOT}/docs/mcp-connection-check.md — its commands use the <sam_cli/> and <mcp_server_scripts/> values above.

Resolve Plan

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

Confirm the plan exists:

uv run "${CLAUDE_PLUGIN_ROOT}/sam_schema/cli.py" plan status --plan-address "{plan_ref}"

Record the Implementation Base SHA

Read sam_plan(plan="{plan_ref}", config={"action": "read"}).context. If it already contains a line matching **Implementation base SHA**: <sha>, skip this step — a prior run already recorded it, and re-running this step now would capture a later commit instead of the true starting point.

Otherwise, before the Progress Loop makes its first commit: run git rev-parse HEAD and prepend **Implementation base SHA**: {sha}\n\n to the existing context (do not replace it — sam_plan(action='update', context=...) overwrites the whole field), then write it back via sam_plan(plan="{plan_ref}", config={"action": "update", "context": "{updated context}"}).

---

Progress Loop

1. Query status:

uv run "${CLAUDE_PLUGIN_ROOT}/sam_schema/cli.py" plan status --plan-address "{plan_ref}"