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. If writing a task makes you type "choose", "decide", "as appropriate", or "either" — stop, make that decision now, and write the decision into the task.

Steps

1. Clarify the goal. State what is being built, the acceptance criteria, and the stack (language, framework, DB). If the requester left a load-bearing choice open (stack, auth mechanism, data model), resolve it with them or state your chosen default explicitly in plan.md — the small model must never pick.

2. Wiki routing sweep. Read the wiki's INDEX.md, then the index.md of every domain the work touches. For each design decision in this work, find the page that owns it (match "load when" lines). Build the decision→page map, e.g. for a login feature:

   • users table shape → wiki/databases/schema-design/requirements-to-tables.md, naming-conventions.md, column-data-types.md
   • PK type → wiki/databases/schema-design/primary-key-choice.md
   • re-signup after delete → soft-delete.md + partial-and-expression-indexes.md
   • auth mechanism choice → wiki/security/authn/session-vs-token.md
   • server token handling → wiki/backend/auth/jwt-server-side.md
   • client token handling → wiki/frontend/auth/token-handling-client-side.md Apply those pages' directives NOW to make the decisions; record decision + page id in plan.md. A decision no wiki page covers → decide from your own judgment, mark it [no-wiki], and note it as an ingest candidate.