Planr Status

Use this skill to answer "are we actually done with this scope?" without silently turning a status check into implementation work or a full audit.

A planr-status is invalid if it skips explicit scope, trusts checked boxes without evidence, or says complete while in-scope blockers or unverified items remain.

CLI-First Rule

• Read ../planr-shared.md first.
• Start with ./.planr/tooling/planr status show, open, and next before reading raw status JSON by hand.
• Only use ensure-scope, set-checklist, set-blocker, or set-verification when the user explicitly asked for status reconciliation and the command surface fits.
• Drop to plan files, path-scoped Git diff, and implementation files only when the CLI output and recorded verification are insufficient.

Required Inputs