agentleFS
mab-gomab-go/trello-mcp/.agents/skills/review-plan/SKILL.md

review-plan

Skill0 starsChanged 6 months agoMITView on GitHub

Review implementation plans for accuracy, correctness, and clarity, including any associated task items. Use when reviewing a plan before implementation or when the user asks for plan review.

37 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-plan, review-design and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JasonPaffSkill

    implement-plan

    Execute implementation plan with structured tracking and validation using subagent architecture

    Also in 5 projects that use this

  • dirkkok101Skill

    review-design

    Use before /plan, after /technical-design, when user says "review design", "check the design", or when design quality is uncertain.

    Also in 3 projects that use this

  • SvampenSkill

    review-implementation

    Reviews implementation against session/work stream goals before committing. Identifies shortcuts, hacks, incomplete work, and validates accomplishments match actual changes. Use before /session-end to ensure implementation quality.

    Also in 3 projects that use this

  • NVIDIASkill

    review-code

    Review a code repository for concrete issues in correctness, robustness, security, maintainability, tests, and integration. Use for repository-wide or focused code review where practical engineering judgment and strict scope control matter.

    Also in 7 projects that use this

  • PydanticSkill

    review-security

    Security review of the current branch against its merge base — sandbox escapes, memory errors, panics and resource-limit bypasses. Use when reviewing changes for security risk, or before merging anything touching the heap/ module, path_security.rs, the wire protocol or the pool.

    Also in 3 projects that use this

  • am-willSkill

    planner

    Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the project's agent instructions (e.g.

    line 8
  2. Distinctive:

    After producing or updating a plan and wanting a self-check

    line 14
  3. Very specific:

    File paths: Run ls or find to confirm referenced files exist.

    line 26
  4. Distinctive:

    API behavior claims: Read the relevant source to verify.

    line 28
  5. Very specific:

    Dependency claims: Check the dependency manifest (e.g.

    line 29
  6. Distinctive:

    If the plan has associated task items (YAML frontmatter todos, a checklist, or structured tasks), review each item for:

    line 58
  7. Distinctive:

    Ambiguous: No clear completion criterion.

    line 62
  8. Distinctive:

    If required context is missing, ask targeted clarifying questions before proposing fixes.

    line 83
  9. Distinctive:

    If the plan is solid, say so briefly.

    line 84
  10. Very specific:

    After plan approval and implementation, run /verify-changes to confirm the build passes.

    line 92

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plan Review

Read the project's agent instructions (e.g. AGENTS.md) before applying this skill to ensure conventions are followed.

When to apply

  • User asks to review a plan before implementation
  • User invokes /review-plan
  • After producing or updating a plan and wanting a self-check

Review directive

The agent implementing this plan may not be you -- it may be an agent without your context. The plan must be rock-solid: accurate, unambiguous, and complete enough to execute without guessing. But do not over-explain for its own sake. Assume a capable implementer.

Verification procedures

For each category, here is how to verify -- not just what to check.

Accuracy

  • File paths: Run ls or find to confirm referenced files exist.
  • Function/type names: Grep the codebase to confirm they exist and have the expected signature.
  • API behavior claims: Read the relevant source to verify.
  • Dependency claims: Check the dependency manifest (e.g. go.mod, package.json).

Correctness

  • Execution simulation: For each step, mentally simulate: does the preceding step produce what this step needs as input?
  • Contradictions: Does step N undo or conflict with step M?
  • Missing steps: Would the plan leave the project in a broken state if stopped after any given step? (e.g. a tool defined but not registered, a struct field added but not in the codec allowlist)

Clarity

  • Different-agent test: Could someone without the surrounding conversation context follow each step unambiguously?
  • Vague language: Flag uses of "appropriate," "relevant," "as needed," "properly" that lack specifics about what they mean concretely.

Completeness

  • Does the plan include a verification step (build/test/lint)?
  • Does it include documentation or config updates if structural changes are made?
  • Does it follow established patterns visible in the codebase?

Severity levels

Classify each finding:

  • Blocker: Plan will fail or produce incorrect results if executed as-is. (e.g. wrong file path, missing step that breaks the build)
  • Warning: Plan will work but has a gap that could cause problems. (e.g. missing test step, vague wording an agent might misinterpret)
  • Suggestion: Plan is correct but could be improved. (e.g. reordering for efficiency, noting an edge case)

Task item review

If the plan has associated task items (YAML frontmatter todos, a checklist, or structured tasks), review each item for:

  • Incomplete: Lacks enough detail to implement unambiguously. A capable agent should not need to make assumptions.
  • Composite: Covers multiple distinct changes that could succeed or fail independently. Should be split.
  • Ambiguous: No clear completion criterion. You cannot tell when it is done.
  • Trivial: Will be completed automatically as a side-effect of another item, or is so self-evident it adds no value.
  • Misordered: Sequenced in a way that creates a blocker (a step depends on a later step).
  • Coverage gap: A significant section of the plan body has no matching task item.

Task item examples

Incomplete: "Update the handler" -- which handler? What change? Better: "Add validation for the title argument in CreateTopicHandler"

Composite: "Add tool and write tests" -- split into "Define tool in tools.go" and "Add handler tests"

Ambiguous: "Clean up the code" -- no completion criterion. Better: "Extract duplicate path-validation into a shared helper"

Trivial: "Import the uuid package" -- this happens automatically when writing the code that uses it. Remove.

Misordered: "Write handler tests" before "Implement handler" -- swap.

Output

  • Summarize what you verified and list findings with severity levels.
  • For errors, vagueness, or ambiguity: state the issue clearly, suggest a concrete fix. Do not edit the plan yet.
  • If required context is missing, ask targeted clarifying questions before proposing fixes.
  • If the plan is solid, say so briefly. No need to repeat it.

Applying changes (only after user approval)

Edit the plan document in-place. If the plan needs a fundamentally different approach (not just fixes), propose a replacement rather than a series of edits that would be harder to review. Proceed only after the user explicitly approves.

Related skills

  • After plan approval and implementation, run /verify-changes to confirm the build passes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.