菜单
Report honest Planr project, map, item, or review state without implementing changes. Use when the user asks what is done, what remains, what is blocked, what is ready, or what should be picked next.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Drive one feature or scope to verified completion without per-step human prompting. Use when the user says build until done, loop on this, or finish autonomously. Sequences plan, map, work, live verification, and independent review until the map is clean and evidence proves the feature actually runs.
Live verification for web features. Use when a web map item needs proof it actually runs in a browser before review, including planr-loop step 4. Discovers the host's existing browser capability, runs the changed flow against the dev server, and logs replayable evidence. Ships no browser tooling of its own.
Prepare a long-running goal for autonomous execution on Planr. Use when the user states a broad goal, wants to start a /goal run, or asks to set up a goal. Compiles intent into a checked plan, a linked map, and a durable goal contract, then prints the starter command for the host's loop driver without implementing anything.
Create or refine Planr product plans and build plans before implementation. Use for app ideas, PRDs, architecture slices, scoped implementation contracts, and converting broad work into map-ready items.
Execute one Planr map item to evidence-backed completion. Use after a task has been picked or when the next step is implementation, docs, tests, scripts, integration work, or a fix item.
Review a Planr item or scoped implementation against map state, plan acceptance criteria, logs, changed files, and verification evidence. Use for findings-first audits and review gates.
| name | planr-status |
| description | Report honest Planr project, map, item, or review state without implementing changes. Use when the user asks what is done, what remains, what is blocked, what is ready, or what should be picked next. |
Use read-only Planr commands first:
planr project show --json
planr map show --json
planr map lane --critical
planr map pressure
For one item:
planr trace item <item-id>
planr log list --item <item-id>
For active work, include runtime and approval state from trace item, map status, or:
planr approval list --open
planr pick stale --older-than-seconds 900
When a loop or /goal run asks whether its stop condition holds, use the one-call verdict:
planr plan audit <plan-id> --json
It reads the stored contract, evaluates every clause with evidence (items settled, reviews complete, approvals clear, verification logged), and answers holds: true/false with the open items listed per clause. Report contract holds or contract open plus the exact unmet clauses straight from the audit output. Use planr search "GOAL CONTRACT" only to read the contract text itself.
Use one:
complete: closed with evidence and no open required child/review/approval work.in progress: concrete work remains and the next step is available.blocked: progress needs an external decision or prerequisite.unclear / partially verified: evidence is incomplete or inconsistent.Never treat checked Markdown boxes or optimistic summaries as proof. Map state and log evidence decide.