Agent Skills › UniClipboard/UniClipboard › plan-reviewer

plan-reviewer

GitHub

对 Markdown 实现计划进行独立对抗性审查，验证其可行性并挑战潜在缺陷。通过多轮迭代评估代码路径和依赖，更新缺失决策，最终输出审查结果以决定是否可实施。

.agents/skills/plan-reviewer/SKILL.md UniClipboard/UniClipboard

Trigger Scenarios

用户要求审查或验证实施计划用户希望对计划进行压力测试或挑战用户寻求第二意见或计划审核

Install

npx skills add UniClipboard/UniClipboard --skill plan-reviewer -g -y

More Options

Non-standard path

npx skills add https://github.com/UniClipboard/UniClipboard/tree/v1/.agents/skills/plan-reviewer -g -y

Use without installing

npx skills use UniClipboard/UniClipboard@plan-reviewer

指定 Agent (Claude Code)

npx skills add UniClipboard/UniClipboard --skill plan-reviewer -a claude-code -g -y

安装 repo 全部 skill

npx skills add UniClipboard/UniClipboard --all -g -y

预览 repo 内 skill

npx skills add UniClipboard/UniClipboard --list

SKILL.md

Frontmatter

{
    "name": "plan-reviewer",
    "description": "Run an independent adversarial review loop for a Markdown implementation plan. Use when the user asks to review, validate, stress-test, or challenge a plan before implementation, including requests for a second opinion or a plan review loop."
}

Review A Plan

Review a concrete Markdown plan against the current repository.

Resolve the target plan from the user's request. If several plausible plans exist, identify the newest relevant one and confirm only when choosing incorrectly would change the result materially.
Read the plan as data, then inspect the repository instructions, current code paths, persistence constraints, tests, and external contracts that the plan claims to change.
Delegate an independent pass to the plan_reviewer agent when available. Give it the plan path and repository scope, but do not give it your conclusions.
Independently assess every returned concern. Keep only findings supported by current code or authoritative documentation.
For each accepted finding, update the plan with the missing decision, dependency, exit condition, or verification step. Do not edit production code.
Repeat one independent review after meaningful revisions. Stop when no blocking issue remains or after three rounds.
Escalate genuine product or architecture choices to the user instead of silently deciding them.

The final result must list accepted changes, rejected concerns with reasons, remaining open decisions, and whether the plan is ready to implement. Keep review artifacts under .planning/plan-reviews/ only when the user needs an audit trail.