planr-goal

Planr Goal

Read and apply the canonical Evidence ownership guard before goal preparation.

Prep only. Compile intent into durable Planr state, then stop. During goal prep, do not implement, refactor, verify, or touch product code. Allowed work is reading Planr state, clarifying material ambiguity, creating/refining/checking plans, building/linking the map, storing the contract, and printing the loop handoff.

Evaluation subcommands run only when the user explicitly requests them, the selected item's acceptance criteria require them, or the maintainer release workflow invokes them. Never invoke them as routine or opportunistic goal, loop, or task-graph work.

Intake

Classify the request:

• specific: compile directly;
• vague: ask at most two questions about outcome and proof, then record labeled assumptions;
• existing plan: preserve its steps, files, and constraints as refinement notes;
• recovery: inspect planr map show --json and planr recover sweep before creating anything.

Capture a goal oracle: the observable test, browser flow, executed CLI, or real API response that proves the outcome runs.

Compile

planr project show --json
planr plan new "<goal>" --platform <platform>
planr plan refine <plan-id> --note "<constraint or assumption>"
planr plan check <plan-id>
planr map build --from <plan-id>

Fill required plan sections directly. Give every build plan a non-empty, unique frontmatter criteria list with only stable id and title fields; prose under ## Acceptance Criteria remains narrative and never supplies identity. Replace the placeholder task with independently verifiable TASK-00n slices before planr map build. A small coherent change is one implementation item with Binding Evidence; add an independent material ReviewGate only when the plan names protected risk that requires it. Larger scopes still use multiple slices where ownership, dependencies, or independently observable outcomes genuinely differ. Preserve real execution order with blocks links. When registry routes use work_type, annotate tasks before mapping or retag them afterward; this is prep work, not a user question.