implementlisted

Turn features described in the PRD and designed in TDDs into code and tests, unattended. With no argument, implements every TDD that has been merged to the integration branch and is not yet `implemented`, as a batch (a batch of one is fine). Pass a TDD path to build just that one. Confirms the queue, then launches the build itself as a detached background job so can do further PRD and TDD updates while it builds. Invoke with /implement.
cahenesy/throughline · ★ 2 · AI & Automation · score 75

Install: claude install-skill cahenesy/throughline

# Implement The single entry point for turning TDDs into code. ## Scope - `/implement <tdd-path>` → build just that TDD. - `/implement` (no argument) → build every TDD that has been merged to the integration branch (origin's default / `main` / `master`; override with `THROUGHLINE_INTEGRATION_BRANCH`) and is not yet `implemented`, in numeric order. **The design-PR merge is what makes a TDD buildable** — merging lands it on the integration branch at `draft`, and that is the go-signal. An un-merged draft on a design branch is not on integration, so the PR stays the gate. TDDs at `Status: implemented` are skipped — that flip is the done-signal. - Re-run safety: the flip to `implemented` is committed on the build branch, not on the integration branch, until you merge. So a re-run before merging would otherwise see the TDD as still buildable and rebuild it. The runner prevents that — a TDD already `implemented` on an existing un-merged branch is treated as done-but-awaiting-merge and SKIPPED (it points you at the branch), so re-running never duplicates work or PRs. `--rebuild` forces a fresh build anyway. ## Detect interrupted run (TDD 0011 / FR-39) Before showing the queue, check whether a prior `/implement` run was interrupted and left a *paused* TDD in the state record. If it did, the user must decide whether to **resume** or **start fresh** before any build work begins; the runner stays headless, so this is the only stage that asks. 1. Run `bash "${CL