implement-action-items

Prompt file imported from ryusoh/fund (.claude/commands/implement-action-items.md). Fill in {{arguments}} before use. Copyright stays with the author.

Implement action items

Execute the work orders in {{arguments}} (or the doc from the conversation) mechanically, one at a time, in order. You are an implementer, not a designer: the doc's anchors and snippets were verified by the authoring agent — follow them literally.

Pre-authorization: Invoking this skill (including via /goal) explicitly authorizes staging and committing each verified work order locally as part of its workflow without pausing to ask for acknowledgement on each commit. Pushing to remote remains strictly forbidden without explicit instruction.

Per work order

1. Read the tags. [skip] → skip the item entirely and record it as skipped (it is routed to a stronger model). [visual] → implement normally, but flag "visual — human review required" in your final report.
2. Match the Find anchor. Locate the exact Find string in the named file. If it does not match — even slightly — stop that item, record the mismatch, and move to the next item. Do not improvise an alternative anchor, and do not "fix" the work order.
3. Make exactly the stated change. Nothing more: no drive-by edits, no refactors, no comment rewording, no touching data/.
4. Verify. Run the item's Verify commands plus the doc's preamble formatting/lint commands. If verification fails and the item gave a fallback instruction, apply it once; otherwise revert your edit for that item (git checkout -- <files>), record the failure, and move on.
   • A verification that cannot fail proves nothing — sanity-check that it would actually go red on the unfixed state (e.g. a layout/measurement assertion must first confirm the measured element is actually constrained, or scroll == client passes vacuously).
   • Cover every file type the session touched: a docs-only markdownlint error (MD040/MD038) has broken CI on this repo even when all JS/CSS checks were green. make precommit-fix is the CI-identical gate; scoped runs must include npx markdownlint-cli2 <changed .md files>.
5. Commit that item only:
   • git add <the specific files you changed> — never git add -A or git add . (other agents' work may share the tree).
   • Commit with a Conventional Commits subject (type(scope): summary, lower-case imperative, ≤ 72 chars), referencing the work-order number in the body.
   • Never push, never amend, never rebase. Pushing is the human's call.

Final report

List each work order as done / skipped ([skip] tag) / failed (anchor mismatch or red verification), with the commit hash for each done item and the failing command's output for each failed item. Do not claim anything you didn't verify this run.

Resume protocol

When resumed, invoked on an in-progress task, or recovering from context compaction:

1. Never trust conversation memory for progress tracking.
2. Inspect authoritative ground truth:
   • Run git status --short and git log -n 5 --oneline.
   • Read the external task state artifact or findings doc.
3. Locate the Program Counter:
   • Identify the first work order where the corresponding commit/verification is missing.
4. Re-anchor working memory:
   • State the current work order number, target file, and entry verification command explicitly before calling tools.

Unattended runs

For a hands-off sweep, the user may wrap this skill in a goal-mode session (e.g. a /goal whose completion criterion is "all non-[skip] items committed, each item's Verify commands green"). That wrapping is the user's choice per run — this skill itself stays harness-agnostic and must not require goal tooling.