planr-summary
Planr Summary
Use this skill when the user wants the end result in plain language, not a verdict-only status report or a findings-first audit.
A planr-summary is invalid if it invents outcomes, hides blockers, collapses into planr-status, or turns into a findings list that belongs in planr-review.
CLI-First Rule
- Read ../planr-shared.md first.
- Start with
./.planr/tooling/planr status show [--scope ...]for live scope context before reading raw status JSON. - There is no summary command today. Build the recap from the recorded
.planrevidence, then drop to plan files, diff, and code only when the recorded state is insufficient.
Required Inputs
- the user's summary request
- the live scope entry
- the governing
.planr/plans/*.plan.mdwhen one exists - any explicitly referenced historical source doc still in scope
- the recorded verification commands and results for the scope
More from regenrek/codex-planr
planr-review
Review agent-owned implementation scope in this repository against `.planr` plans or live status, path-scoped Git evidence, and acceptance criteria. Use for findings-first audits of completion, correctness, architecture, hard-cut cleanup, and test sufficiency. Not for implementing fixes (`planr-fix`), writing a new execution contract (`planr-plan`), or giving a verdict-only status answer (`planr-status`).
1planr-plan
Create or update executable `.planr/plans/*.plan.md` contracts in this repository. Use when scope, ownership, phase breakdown, verification, or acceptance criteria must be defined before implementation, including bug-to-plan conversions and review-finding follow-up plans. Not for executing fixes (`planr-fix`), giving a verdict-only status answer (`planr-status`), or running a findings-first audit (`planr-review`).
1planr-fix
Implement remaining scoped work in this repository to verified completion. Use for direct bug fixes, regressions, failing tests, `planr-review` findings, or unfinished `.planr` plan phases when the next step is to change code, tests, or docs, keep live `.planr` status honest, and prove the result. Not for writing a new execution contract (`planr-plan`), giving a verdict-only status answer (`planr-status`), or running a findings-first audit (`planr-review`).
1planr-status
Assess the honest current state of a scoped `.planr` task in this repository. Use when the user asks what is done, what remains, what is blocked, whether a scope is complete, which scopes are open, or what should come next. Start with the deterministic `.planr` CLI where it has command coverage. Not for implementing fixes (`planr-fix`) or running a findings-first audit (`planr-review`).
1