agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-tools-py/.claude/skills/plan_review/SKILL.md

plan_review

Skill21 starsChanged 3 months agoMITView on GitHub

Review implementation plan for completeness, simplicity, and risks

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].

    line 13
  2. Very specific:

    Use mcp__mcp-workspace__git with command "status" to check working directory state.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Review Implementation Plan

First, ensure we're up to date: Call mcp__mcp-workspace__git with command "fetch" and args ["origin"]. Use mcp__mcp-workspace__git with command "status" to check working directory state.

Confirm and display the current feature branch name.


Then review the plan:

Please review the project plan for a new feature in folder pr_info/steps. Please revise the project plan with a balanced level of detail. Please let me know if any complexity could be reduced. Please let me know any questions / comments or suggestions you might have.

Please consider the already discussed and decided decisions (if any) under decisions. We do not need to challenge them again unless absolutely necessary.

Focus on:

  • Completeness of implementation steps
  • Appropriate level of detail
  • Opportunities for simplification (KISS principle)
  • Test coverage strategy
  • Step granularity — each step should produce exactly one commit. Flag steps with multiple independent parts (A, B, C) that should be split.
  • Potential risks or blockers
  • Requirement changes — flag new dependencies (pyproject.toml) that should be applied during planning, not deferred to implementation

For planning standards, see .claude/knowledge_base/planning_principles.md.

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.