Prompt · Plan
Break a spec into stories and tasks
Get user stories and tasks with acceptance criteria and file-level changes.
/planr:plan SPEC-001$plan SPEC-001@planr-plan SPEC-001These examples use CLI-managed direct skills. With the plugin, use $planr:plan; with individual source skills, use $planr-plan.
These examples use CLI-managed Cursor rules. With individual source skills, select planr-plan in the skill picker.
Why this works
Plan reads the saved spec, so every story keeps its acceptance criteria and every task names its files, its dependencies, and the checks that prove it is done. It stops after the plan and never starts building on its own.
Related prompts
Plan straight from a clear request
When the request is already clear, skip the spec and get stories and tasks from it.
Plan UI work from a finished design
Turn a design and its design spec into UI tasks that carry the screens, states, and frames.
Audit the plan for drift
Check that stories, tasks, statuses, and references in the planning folder still agree.