Prompt · Plan
Pin down acceptance criteria before planning
Turn loose requirements into observable criteria with stable IDs before anyone plans the work.
/spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.$spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.@planr-spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.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
Spec writes requirements and acceptance criteria that can be observed, each criterion with a stable AC-NNN ID. Plan later maps every ID to a task and to a check in that task's test requirements.
Related prompts
Turn a rough idea into a spec
Start every feature with a specification your agent can check its work against.
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.