Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.
Installs into .claude/skills of the current project.
Are you the author of Planr Land?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/openplanr-planr-land)
---
name: planr-land
description: Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.
license: MIT
---
# OpenPlanr Land
Use this skill after implementation and relevant checks are complete, when the
user wants to assess readiness or prepare a clear landing sequence.
1. Read the current branch, worktree status, requested target, completed checks,
and release constraints already available in the repository or conversation.
2. Inspect the installed CLI help, then use `openplanr land prepare`, `openplanr land
show`, or `openplanr land status` only when that command adds useful local state.
3. Identify blockers, missing checks, ordering constraints, recovery options,
and the exact merge, publication, or deployment commands the user would run.
4. 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.
5. Return this concise structure:
- **Readiness:** ready, conditional, or blocked, with one-sentence reasoning.
- **Blockers:** prioritized and actionable; write `none` when 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.
Lead with readiness and link any prepared landing record. Summarize checks that
actually passed and name missing verification; prepared commands are not executed
effects. Keep a long command sequence in the linked record and show the next
action in chat. Omit empty blockers, preserve useful partial preparation, and
give the smallest recovery step when blocked. The human summary does not create
a new result format or require a rerun for different wording.
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.
