wiki-plan

# Plan — decompose work into small-model-executable tasks > **In the dev-loop plugin.** The wiki is bundled with the plugin, not in the > user's project. Resolve every `INDEX.md`, `wiki/<...>.md`, `AGENTS.md`, and > `templates/` path in this skill against **`${CLAUDE_PLUGIN_ROOT}/`** (the > installed plugin root), NOT the current working directory. Read the wiki from > there; write plan output (`plans/<feature>/`) into the user's project as > described in step 5. > > **How this plugs into the loop.** `loop-implement` calls this skill as its > **step 2 (Plan)** — mandatory. Produce the wiki-grounded `## Decisions` table, > the ordered `## Task order`, and one `tasks/NN-*.md` per task naming the exact > wiki pages it needs. **`loop-implement` is the single implementer** — it then > executes those tasks *in order*, loading each task's named pages and running the > verification loop (Red → Green → run → audit) per task. (`orchestrate` uses the > same output to fan tasks across sessions, each session running `loop-implement`.) > Every decision must cite a `wiki/` page or be marked `[no-wiki]`. You are the planner. The implementer will be a small model with no memory of this planning session. Its entire world per task = one task file + the wiki pages that file names + the artifacts earlier tasks produced. **Every decision you leave unmade becomes the small model's guess** — and guesses are where errors enter. ## Rule zero Decisions live in the plan; execution lives in the tasks...