Prompt · Plan
Turn a rough idea into a spec
Start every feature with a specification your agent can check its work against.
/spec add passwordless sign-in for existing accounts. Users drop off at the password step.$spec add passwordless sign-in for existing accounts. Users drop off at the password step.@planr-spec add passwordless sign-in for existing accounts. Users drop off at the password step.If /spec runs another command, use /planr:spec.
With the OpenPlanr plugin for Codex, use $planr:spec.
Cursor applies the planr-spec rule when you mention it in chat.
Why this works
Name the change and the problem it solves. The skill reads your repository for the rest, and when a missing decision would change the scope, it asks at most 3 short questions at a time. Requirements and acceptance criteria come out observable, so the work can be checked against them.
Related prompts
Pin down acceptance criteria before planning
Turn loose requirements into observable criteria with stable IDs before anyone plans the work.
Audit the plan for drift
Check that stories, tasks, statuses, and references in the planning folder still agree.
Pick the next sprint against the real code
Refine the open backlog and select what fits capacity and the release cut.