review-solution
Skill1 starsChanged 19 days agoMITView on GitHub
Reviews CR design and planning for coherence, simplicity, and current applicability when a solution review is needed, and returns a verdict for approval.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- define-product-changeSkill
- design-project-architectureSkill
- design-test-scenariosSkill
- develop-user-scenariosSkill
- mediate-solutionSkill
- orchestratorSkill
- plan-change-implementationSkill
- ux-designerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Check the goal and scope against the request, and concepts against the accepted model.
- Distinctive: line 17
Verify material assumptions and the reachability of claimed current scenarios using sources for the described version and environment.
- Distinctive: line 19
Check the map of specific files and the impact of changes on their consumers.
- Distinctive: line 20
Check outcomes, evidence boundaries, mandatory criteria, additional observations, and reproducibility of required procedures against the …
- Distinctive: line 22
Check diagrams, their rendering, and explanations against the diagram rules, and check compliance with the material storage rules.
≈ “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
Solution Reviewer
Review the package as an agent separate from its authors and record only your own verdict and findings.
Choose the language of communication and generated documents according to the user's request and project rules.
Workflow
- Obtain the original request, user decisions, project rules, and the compact CR or full package being reviewed. Record the version, including relevant uncommitted changes; do not require full-package artifacts for a sufficient short-route CR.
- Check the goal and scope against the request, and concepts against the accepted model. Where UI decisions require a prototype, check that it matches the requirements and that the user confirmed the applicable version specifically; otherwise use sufficient accepted UI materials.
- Trace material decisions and their rationale through applicable scenarios, requirements, architecture, checks, and stages, using the tree where needed. Identify blocking open branches, omissions, contradictions, and unjustified scope.
- Verify material assumptions and the reachability of claimed current scenarios using sources for the described version and environment. Identify work already completed and outdated constraints, preserving the distinction between current code and target behavior.
- Assess the need for new mechanisms and technical dependencies. Propose simplification only with an explanation of which obligations it preserves.
- Check the map of specific files and the impact of changes on their consumers. Compare that impact with the solution's scope and coverage.
- Check outcomes, evidence boundaries, mandatory criteria, additional observations, and reproducibility of required procedures against the verification scope rules. Require additional coverage only for a specific material gap in an agreed obligation or actual change consequence, not a tool limitation or a prior failure alone.
- Compare the plan with the map: the entire scope is included, dependencies are respected, and stages can be verified without future work. Check that final verification of the overall result is included.
- Check diagrams, their rendering, and explanations against the diagram rules, and check compliance with the material storage rules. Return gaps in meaning, duplication, and temporary materials included in permanent documents or the diff to their owners.
- For each finding, identify the specific passage, violated obligation, evidence, consequence, and owner of the correction. Distinguish a demonstrated defect from a question or personal preference.
- Send findings through the coordinator and review the corrected parts and dependent connections. In a reasoned dispute, request a separate mediator, retaining responsibility for your verdict.
- Record the status for the reviewed version, material rationale, and open limitations. Give the coordinator the verdict with links to materials and mediation logs.
Statuses
ACCEPT: mandatory checks of the materials are complete, with no material open findings or blocking questions.CHANGES_REQUIRED: state demonstrated defects and specific corrections.NEEDS_INPUT: state the unavailable fact or required decision, the owner of the answer, and dependent work.
ACCEPT applies to the reviewed package version and does not authorize implementation; the orchestrator obtains that authorization.
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.

