continuelisted

# Continue Project ## Instructions ### Step 1 — Read state in order of specificity 1. **`wiki/_current.md`** — session goal, active task, last decisions. Hook already injected this at session start; re-read if you need detail. 2. **`wiki/plan/` summary** — already in context via `session-start.mjs`. If you need a task's full details: read `wiki/plan/<id>-<slug>.md`. 3. **`wiki/_map.md`** — project-wide picture. 4. **`wiki/architecture/stack.md`** — tech stack. 5. **`wiki/pitfalls.md`** — don't repeat old mistakes. ### Step 1.5 — Pipeline state check (v4.9.0+) If project follows the 7-step pipeline (`$start` was used, or `$pipeline` invoked), run: ```bash node scripts/check-pipeline-state.mjs ``` This shows: - Which steps are complete ✓ - Where you are now → (current step) - What's required for the next step - Suggested command для invoke Use this output to **confirm** what `_current.md` says — иногда они расходятся (file timestamps вне sync с manual status block). The verifier reads filesystem reality. Skip this step if: - Project не следует pipeline (e.g. just bug fix sessions, no plan structure) - `wiki/architecture/metrics.md` doesn't exist (means no formal pipeline started) ### Step 2 — Identify where to resume - If `_current.md` has an unchecked item → continue it. - Else if any `wiki/plan/*.md` has `status: in_progress` → resume that task. - Else → pick first task from `wiki/plan/` with `status: planned` whose `deps` are all `done`. Flip it to `in_pro