implement-changelisted

# Implement change (one repo) Implement one repo's approved work and tests. **Kind** procedure · **Used by** [backend-dev](../../agents/backend-dev.md) · [frontend-dev](../../agents/frontend-dev.md) · **When** the plan passes review (develop-flow step 3) · **Ends with** code written, tests written and **collected but never executed**, and every verification command the profile lists for the touched areas green — **not** a commit or PR; [release-pr.md](../release-pr/SKILL.md) does that after review, tests, and QA Set `TROIKA_WORKSPACE`; scratchpad paths are absolute. ## 1. Read the plan Read `$TROIKA_SCRATCHPAD/plans/<TICKET>.md`. Take only your repo. Missing or contradictory work stops; never re-plan. Read the workspace's memory too — `ls $TROIKA_MEMORY/*.md`, there is no index file ([memory](../memory/SKILL.md)). These entries are written by dev and test roles about exactly this work: a repo mid-migration, a suite that only fails in parallel, a green result that did not mean what it looked like. ## 2. Branch in a worktree — one per repo, not one per role Check for the repo lane first: ```bash git worktree list | grep "<repo>-<TICKET>" ``` - **Exists:** join it, read prior work log, stay in owned paths. Never create a second repo lane. - **Missing:** create from profile `<BASE>` with the contractual name: ```bash git fetch <remote> git worktree add "$TROIKA_WORKTREES/<repo>-<TICKET>" -b <branch, per the profile> <BASE> ``` Use profile dependency symlinks; do not r