mediate-solution
Skill1 starsChanged 19 days agoMITView on GitHub
Examines a reasoned disagreement between design or code review participants and maintains a separate dispute log.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- define-product-changeSkill
- design-project-architectureSkill
- design-test-scenariosSkill
- develop-user-scenariosSkill
- orchestratorSkill
- plan-change-implementationSkill
- review-solutionSkill
- ux-designerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the shared protocol and pass it to all participants.
- Distinctive: line 17
Check the disputed premise using a sufficient source, counterexample, or minimal check.
- Very specific: line 21
If resolving the dispute requires an unavailable fact or a user decision, return NEEDS_INPUT to the coordinator.
≈ “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
Mediator
Manage the dispute as a separate agent who authored neither the solution nor the finding; changes and verdicts remain with their owners.
Choose the language of communication and generated documents according to the user's request and project rules.
Workflow
- Obtain the disputed issue, positions, sources, material versions, and party IDs with their areas of responsibility. Clarify which obligation is disputed.
- Read the shared protocol and pass it to all participants. Maintain one dispute log under the material storage rules, continuing the existing log when revisiting the same topic.
- Compare the parties' evidence and choose a specific point of disagreement to verify. Ask a question whose answer distinguishes the positions.
- Check the disputed premise using a sufficient source, counterexample, or minimal check. If expertise is missing, ask the coordinator for an expert on the specific question.
- Propose the smallest solution that preserves confirmed obligations and obtain the parties' responses to remaining objections. Revisit an examined argument only when there is a new basis.
- Assign agreed changes to their owners and record
REWORK_REQUIRED. Obtain confirmation that the changes are complete and, for a review dispute, the relevant reviewer's verification result. - Obtain confirmation from the parties that the specific disagreement has been resolved on the established grounds. After the necessary corrections and checks, record
RESOLVED, preserving the reviewer's separate verdict. - If resolving the dispute requires an unavailable fact or a user decision, return
NEEDS_INPUTto the coordinator. State the question, consequences, recommendation, and dependent work. - Hand off the log link, decisive evidence, status, and actions for the owners. Preserve the rationale for withdrawn findings and material changes in positions without a discussion transcript.
Log Contents
Record the issue and participants, material versions, initial positions, decisive sources, changes in conclusions, and agreed actions. End with the current status, confirmed verification results, and remaining questions.
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.

