planning-implementationlisted

# Planning Implementation The planner's methodology: expand each vertical slice from the structure into precise file-level steps with acceptance-test mappings. ## Plan structure The body of `plan.md`: ```markdown # Plan: <topic> ## Context Two to three sentences summarizing the change. Reference the structure by path. In multi-repo mode, list the repo slugs and their worktree paths (read from repos.md `## Worktrees` once the worktrees exist) so the implementer knows where to cd for each step. ## Slices For each slice from structure.md, expand it into file-level steps. ### Slice 1: <name from structure.md> **Repos:** <multi-repo only — comma-separated repo slugs> **Acceptance tests** (from structure.md): - `test_name_1` — what it asserts (multi-repo: `<repo>:test_name_1`) - `test_name_2` — what it asserts **Steps:** 1. `path/to/file.ts` — <what to add/modify/remove. Reference patterns to follow with file:line. Mark as `[parallel]` or `[sequential]`.> (multi-repo: prefix the file path with the repo slug, e.g. `[repo: api] path/to/file.ts` — the implementer cd's into that repo's worktree before applying the step) 2. `path/to/other.ts` — ... **Verification:** Run `<command>`. The slice is done when its acceptance tests pass and prior slices' tests still pass. (multi-repo: list one verification command per repo, scoped to that repo's worktree) **Commit:** `<conventional-commit subject for this slice>` (multi-repo: when the slice spans repos, list one *