planr-plan-review
Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 6
- Forks
- 1
01 前言 Front Matter
- name
- planr-plan-review
- license
- MIT
- description
- Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.
02 资源文件 3
- 参考文档agents/openai.yaml388 B
- 参考文档openplanr.skill.json698 B
- 参考文档references/return-contract.md676 B
03 SKILL.md 正文
OpenPlanr Plan Review
Review the plan as a senior engineer would before implementation. Read the plan
and the files it names, plus AGENTS.md and CLAUDE.md when tracked, in one
batch. Expand only for a missing contract, a dependency or a contradiction, and
stop when each claim has evidence or a named gap.
Lead with one verdict: ready, ready with improvements or needs revision.
Use needs revision only while a must-fix remains.
- Must fix: what would make the implementation wrong or unsafe. Give each one its evidence (the plan section plus the file and line, or the quoted text, that shows it) and the change that resolves it. A concern without evidence is an improvement or an open question, never a must-fix.
- Improvements: worthwhile, non-blocking changes.
- Decisions and assumptions: unresolved choices, each with a recommended default. Ask only when a missing answer would change the verdict; otherwise state the assumption and continue.
End with the smallest useful next step. Link the reviewed plan. Follow the shared return rules.
04 同仓库更多 Skills
design
暂无简介
planr-sync
Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.
planr-status
Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.
planr-sprint
Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status.
planr-spec
Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.
planr-ship
Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository. Use when the user asks to build, implement, fix, finish, or ship local work, or to plan and implement an accepted change. Invoke before editing files for the requested change. Not for planning only, landing, release, or work handed to another coding agent.