AgentSkillsCN

lazy-plan-reviewer

在实施前，对技术计划文档（PLAN-*.md）与当前代码库进行严格审查。在被要求审查计划、验证计划、检查计划是否存在问题、审计实施计划，或评估计划是否已具备实施条件时使用。能够及时发现设计缺陷、代码库不匹配，以及潜在的风险假设。

SKILL.md
--- frontmatter
name: lazy-plan-reviewer
description: Critically review technical plan documents (PLAN-*.md) against the current codebase before implementation. Use when asked to review a plan, validate a plan, check a plan for issues, audit an implementation plan, or assess whether a plan is ready to implement. Catches design flaws, codebase mismatches, and risky assumptions.

Lazy Plan Reviewer

Review plan documents against the codebase before implementation to catch design flaws, mismatches, and risky assumptions.

Review Process

  1. •Load plan context — Read plan file, identify goals, architecture, assumptions
  2. •Check repo state — git status, git branch -vv, git log --oneline -20
  3. •Plan vs codebase alignment — Map plan items to existing code, check feasibility
  4. •Architecture critique — Evaluate modularity, coupling, backwards compatibility
  5. •Risk assessment — Security, performance, migration complexity
  6. •Implementation readiness — Milestones, test coverage, validation criteria

Focus Areas

Critical (Must Fix)

  • •Conflicts with existing codebase
  • •Security/data integrity risks
  • •Breaking changes without migration strategy
  • •Infeasible or underestimated changes

Important (Should Fix)

  • •Vague requirements
  • •Misaligned architecture patterns
  • •Unclear module boundaries
  • •Missing performance considerations

Suggestions (Nice to Fix)

  • •Plan clarity and structure
  • •Additional diagrams/examples
  • •Documentation improvements

Output Format

markdown
## Plan Review Summary
[Overall assessment of feasibility]

## Critical Issues
- [Issue with file:line reference]
- [Recommendation]

## Important Issues
- [Issue with reference]
- [Suggested fix]

## Suggestions
- [Non-blocking improvements]

## Codebase Alignment
- [Plan section] -> [Relevant files]
- [Gaps where no mapping exists]

## Approval Status
**READY TO IMPLEMENT** / **NEEDS REVISION**

Guidelines

  • •Reference specific plan sections and code locations (path/file.ext:line)
  • •Propose actionable alternatives, not just problems
  • •Prioritize by real-world risk and implementation cost
  • •Use ask_questions tool for ambiguous sections or critical decisions

Usage

Provide the plan file path, or run without arguments to auto-detect PLAN-*.md files in the project root.