From Plan & Critique
Creates a new plan folder with a plan.md template, reading config for storage path and generating a filesystem-safe slug from the plan name.
How this skill is triggered — by the user, by Claude, or both
Slash command
/plan:createThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating a new plan folder for the user.
You are creating a new plan folder for the user.
To do this, follow these steps precisely:
+-------------------------------------------------+
| Plan Critique v2.0.1 - Creating new plan |
+-------------------------------------------------+
.claude/plan-critique-config.json and get plansFolder path from settings.
If the file doesn't exist or plansFolder is not set:
.planning):".
By default, the user should be presented with the option .planning.plansFolder in .claude/plan-critique-config.jsonarchived/ subfolder inside it$ARGUMENTS is the plan name. Use it directly.add-user-authentication[plansFolder]/[slug]/ already exists.
If it does: Respond with "A plan with this name already exists at [plansFolder]/[slug]/. Choose a different name."
Ask for a new name and repeat from step 4.[plansFolder]/[slug]/echo $PPID[plansFolder]/.sessions/[plansFolder]/.sessions/[PID] (plain text, just the slug)[plansFolder]/[slug]/plan.md using the template in
plan-template.md.Created new plan: [plansFolder]/[slug]/
Edit your plan at: [plansFolder]/[slug]/plan.md
When ready, run `/plan:critique` to review your plan.
Notes:
/plan:critique)plansFolder from settings as the base directorynpx claudepluginhub serbanghita/claude-code-plan-critique --plugin planCreates structured PLAN.md for software engineering tasks by interviewing user for intent, scanning project context, and outlining scope, success criteria, sequenced checklist. Use before implementation.
Replicates Claude Code plan mode in read-only fashion: explores codebase, designs changes, gets user approval, then writes plan to .claude/plans/<slug>.md without executing. Triggers on 'plan only' phrases.
Generates development plans and auto-creates PLAN.md, CONTEXT.md, CHECKLIST.md, .status files in .cwm/docs/plans/{date-task}/ before new tasks. Analyzes requirements, code; awaits approval.