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
- MarcusJellinghaus/mcp-workspaceword for word, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 1
- MarcusJellinghaus/mcp-workspace★ 49100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement_directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_createSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_review_supervisorSkill
- plan_updateSkill
- rebaseSkill
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
- Very specific: line 13
Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].
- Very specific: line 14
Use mcp__mcp-workspace__git with command "status" to check working directory state.
≈ “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.
Files
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.
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
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.

