Planr Land
Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.
Install
$ agentstack add skill-openplanr-openplanr-planr-land ✓ 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-land) 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 Land
Use this skill after implementation and relevant checks are complete, when the user wants to assess readiness or prepare a clear landing sequence.
- Read the current branch, worktree status, requested target, completed checks,
and release constraints already available in the repository or conversation.
- Inspect the installed CLI help, then use
planr land prepare, `planr land
show, or planr land status` only when that command adds useful local state.
- Identify blockers, missing checks, ordering constraints, recovery options,
and the exact merge, publication, or deployment commands the user would run.
- If a real release choice is missing, use the host's native structured question
UI; otherwise continue with the safest explicit assumption and label it.
- Return this concise structure:
- Readiness: ready, conditional, or blocked, with one-sentence reasoning.
- Blockers: prioritized and actionable; write
nonewhen empty. - Landing sequence: ordered commands or actions, including preconditions.
- Recovery: rollback or retry guidance for the first meaningful failure.
- Next action: the single most useful step for the user.
When the OpenPlanr dashboard is running, readiness context is browsable at its #/overview and #/list views. This is navigation only.
This skill prepares and inspects the sequence; it does not perform merge, publication, or deployment effects. When a local command fails, report the failing command, what remains known, and the shortest practical repair.
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.