grimoire-plan

Installation
SKILL.md

Plan the implementation approach; do not implement production code or treat a saved plan as implementation authorization.

Invocation and permissions

Under orchestration, the caller's execution contract takes precedence over this skill's standalone defaults.

Standalone, return the plan in conversation by default. Write plan files only when the user explicitly requests a saved plan or the caller's execution contract authorizes persistence. Otherwise, do not create directories, files, or a viewer.

Source and destination

Accept conversation, spec, ticket, selected slice tickets plus their relationship README, or an existing plan. Preserve source paths or a concise intent/acceptance/constraints contract. User intent and acceptance criteria outrank incidental plan details.

Reuse an adequate existing plan; when persistence is authorized, revise the same file for the same goal. Keep unrelated goals separate. For a new persisted plan, use .grimoire/plans/NNNN-title.md, with a short kebab-case title and one more than the highest existing plan number (or 0001), ignoring viewer.html.

Persistence needs only .grimoire/plans/: create missing parent directories when authorized. Do not require grimoire-init or change registration, knowledge files, or Git configuration. A path/type conflict or denied write is a blocker to persistence, not permission to replace existing content.

Plan content

Read relevant repository code, integration surfaces, available domain knowledge, and applicable ADRs. Scan metadata before expanding unrelated history; missing optional knowledge files are not prerequisites.

Installs
23
GitHub Stars
3
First Seen
Jul 23, 2026