Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From planr
Audits Planr items against map state, acceptance criteria, logs, changed files, and verification evidence. Emits findings-first verdicts with actionable next steps.
npx claudepluginhub instructa/planr --plugin planrHow this skill is triggered — by the user, by Claude, or both
Slash command
/planr:planr-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this when a task needs a correctness and completion audit.
Orchestrates parallel architecture and experience reviews of implementation plans, scores findings across dimensions like data flow and UX, consolidates ranked fixes for user approval and auto-application. Use after planning, before non-trivial coding.
Execute one Planr map item from pick through evidence-backed completion, including implementation, testing, review, and approval steps.
Audits post-implementation plans against changes by parsing checkboxes for completeness and accuracy. Supports autonomy modes (Autopilot, Critical, Verbose) and file-review. Invoke via /verify-plan.
Share bugs, ideas, or general feedback.
Use this when a task needs a correctness and completion audit.
planr trace item <item-id>
planr log list --item <item-id>
planr map show --json
Inspect the actual changed files and verification evidence. Then close the review:
planr review close <review-id> --verdict complete
or:
planr review close <review-id> --verdict not-complete --findings "specific actionable finding"
--verdict unclear rather than complete.The target item may close only after required review items are closed. Use the map as the source of truth. Pending or denied approval is also a close blocker; treat an attempted close through that gate as a finding, not as completion.