create-plan

name	create-plan
description	Create an implementation plan for this repo. Use when the user wants a checked-in plan under README/Plans, wants the work scoped into phases, and expects the plan to be built from repo guides and notes first, with Context7 only when current external library or framework behavior materially affects the plan. Do not use for implementing the work, informal brainstorming, or lightweight notes.

Create Plan

Purpose

Use this skill to turn a concrete request into a repo-native implementation plan. The output is a real plan file under README/Plans/..., not a chat-only outline.

Use When

• The work is large enough to need a real implementation plan.
• The user wants a plan written into the repo.
• The implementation needs phases, verification steps, and concrete files.

Do Not Use When

• The user wants direct implementation instead of planning.
• The request is still too vague to scope honestly.
• The output should be a note, scratchpad, or brainstorm instead of a plan.

Procedure

1. Read references/index.md first.
2. Gather repo context in this order:
   • directly related README/Guides
   • directly related README/Notes
   • README/Skills when the work touches plan workflow, skills, or routing
   • neighboring plans in the target README/Plans/... subtree
3. Use Context7 only when the plan depends on current library, framework, or API behavior that may have changed.
4. If Context7 is insufficient, fall back to official vendor docs.
5. Choose the most specific existing README/Plans/... subdirectory that fits the work. If none fits cleanly, place the plan in the closest higher-level subtree instead of inventing a noisy new folder.
6. Write the plan with the repo's canonical template and make it implementation ready:
   • concrete phases
   • specific files where knowable
   • verification per phase
   • hard requirements
   • rollback or kill switch when relevant
7. Audit the draft before stopping:
   • no missing policy that an implementer would have to invent
   • no fake certainty where the repo context is incomplete
   • no implementation work performed while planning

Canonical Docs

Read references/index.md first. It maps the canonical workflow guide, the plan template, and the repo references to inspect before writing a new plan.

Handoff Rules

• Hand off to execute-plan only after the plan is checked in and the user wants implementation.
• Hand off to a domain skill only if the planning request narrows into a domain-specific technical question that must be answered before the plan can be completed.