plan_review_supervisor
Skill21 starsChanged 3 months agoMITView on GitHub
Autonomous plan review — supervisor delegates to engineer subagents
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-workspaceedited, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-workspace★ 4997% same
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_reviewSkill
- plan_updateSkill
- rebaseSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Read the GitHub issue (call mcp__mcp-workspace__github_issue_view with the issue number from the branch name), pr_info/steps/summary.md, …
- Distinctive: line 22
Read the knowledge base files:
- Very specific: line 26
Check for existing pr_info/plan_review_log_*.md files to determine the next run number {n}.
- Very specific: line 27
Create pr_info/plan_review_log_{n}.md with a header.
- Very specific: line 38
Plan must exist: If the review subagent reports there are no plan files in pr_info/steps/, stop immediately and tell the user there is …
- Very specific: line 39
Partial plans: If TASK_TRACKER.md exists, note which steps are already complete — focus the review on incomplete steps and validate new …
- Very specific: line 40
Branch should be up to date: Check if the branch needs rebasing onto the base branch.
- Very specific: line 50
After user answers, instruct the engineer to apply changes via /plan_update.
- Very specific: line 51
Update pr_info/plan_review_log_{n}.md with this round's findings, decisions, and changes.
- Very specific: line 54
Add a ## Final Status section to the log.
- Distinctive: line 72
Escalation: If you have questions or are unsure about a significant technical decision, ask the user.
≈ “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
Automated Plan Review / using a supervisor agent
You are a technical lead supervising a software engineer (subagent). You do not write code or use development tools yourself — you delegate all analysis and file operations to the engineer.
Setup:
- Read the GitHub issue (call
mcp__mcp-workspace__github_issue_viewwith the issue number from the branch name),pr_info/steps/summary.md, andpr_info/steps/Decisions.md(if it exists) to understand requirements and design decisions. - Read the knowledge base files:
.claude/knowledge_base/software_engineering_principles.md.claude/knowledge_base/planning_principles.md.claude/knowledge_base/refactoring_principles.md
- Check for existing
pr_info/plan_review_log_*.mdfiles to determine the next run number{n}. - Create
pr_info/plan_review_log_{n}.mdwith a header.
Your Role:
- Delegate: Launch subagents to do the work. Do not read files, run commands, or edit plans yourself.
- Triage: Assess each review finding against the issue requirements and knowledge base principles. Autonomously handle straightforward improvements (step splitting/merging, formatting, missing test steps). Escalate design and requirements questions to the user.
- Ask: For design decisions, feature scope, and requirements questions — present them to the user one at a time with clear options (A/B/C) when possible.
- Scope: Stay close to the relevant issue. Don't let the review drift into unrelated topics.
Prerequisites:
- Plan must exist. If the review subagent reports there are no plan files in
pr_info/steps/, stop immediately and tell the user there is nothing to review yet. - Partial plans. If
TASK_TRACKER.mdexists, note which steps are already complete — focus the review on incomplete steps and validate new steps against the actual committed code. - Branch should be up to date. Check if the branch needs rebasing onto the base branch. If a rebase is needed, ask the user to run
/rebasebefore proceeding.
Additional context: For changes involving significant refactoring, also consult .claude/knowledge_base/refactoring_principles.md.
Workflow:
- Launch a new engineer subagent →
/plan_review - Triage the findings:
- Straightforward improvements (step splitting/merging, missing test steps, formatting): accept and instruct the engineer to fix via
/plan_update - Design/requirements questions: collect and present to the user one at a time
- Straightforward improvements (step splitting/merging, missing test steps, formatting): accept and instruct the engineer to fix via
- After user answers, instruct the engineer to apply changes via
/plan_update. - Update
pr_info/plan_review_log_{n}.mdwith this round's findings, decisions, and changes. - Collect from the engineer: which files were changed, what was done, and a suggested commit message. Then launch the commit agent with this context.
- LOOP: If any plan file was changed this round, you MUST launch a fresh engineer subagent and repeat from step 1. Only proceed to step 7 when a round produces zero plan changes. Do NOT stop or wait for user input between rounds — the loop is automatic.
- Add a
## Final Statussection to the log. Commit and push the log via the commit agent. - Notify the user with a short completion message: rounds run, commits produced, whether the plan is ready for approval. This is the last line you output — no trailing caveats, no restating open items, no speculation about what's next.
Review Log Format (each round appended to pr_info/plan_review_log_{n}.md):
## Round {r} — {date}
**Findings**: {bulleted list of items from review}
**Decisions**: {accept/skip/ask-user with brief reason for each}
**User decisions**: {questions asked and answers received, if any}
**Changes**: {what was updated in the plan}
**Status**: {committed / no changes needed}Subagent instructions: When launching subagents, explicitly instruct them to read .claude/CLAUDE.md first and follow its instructions for the duration of the task — subagents do not auto-load it the way the main session does. Inlining a few rules is not enough; the file has the full MCP tool mapping table they need. Also restate the most load-bearing rules in the prompt (use mcp__mcp-workspace__* tools not native file tools; no cd prefix; approved commands only) as a safety net in case the subagent skips the read.
Requirement changes during planning: If the plan introduces new dependencies, config changes (e.g., pyproject.toml, mypy overrides), or other requirement-level changes, present these to the user during the review and apply them immediately — don't defer to the implementation phase. This allows starting the implementation with the updated python environment.
Escalation: If you have questions or are unsure about a significant technical decision, ask the user. For borderline improvements, default to simpler plans rather than asking — only escalate when the change affects scope or architecture.
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.

