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.
Install
$ agentstack add skill-openplanr-openplanr-planr-plan-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-plan-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Planr Plan Review
Give the plan a senior, practical review. Read the plan, its repository context, and the decisions it depends on. Use only the review lenses relevant to the work; do not manufacture a fixed committee.
Review
- Check that the outcome and user value are clear and measurable.
- Check scope, sequencing, ownership, architecture, migration, security,
operability, testing, and rollback in proportion to the change.
- Check the first-run and everyday developer experience, including setup,
diagnostics, defaults, and recovery.
- Prefer concrete corrections over abstract criticism. Name the affected plan
section and the change that would resolve each material issue.
- Use subagents or tools when they improve the review, but return one coherent
result rather than their raw transcripts.
Ask through the host's native structured question UI only when a missing answer would materially change the review. Otherwise state the assumption and continue.
Output
Lead with one verdict: ready, ready with improvements, or needs revision. Then report:
- Must fix — only issues that would make the implementation wrong or unsafe.
- Improvements — worthwhile changes that are not blockers.
- Decisions and assumptions — unresolved choices with a recommended default.
- Next action — the smallest useful next step.
Return the useful findings directly. Revisit the review when the user asks or the plan materially changes.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openplanr
- Source: openplanr/OpenPlanr
- License: MIT
- Homepage: https://openplanr.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.