debate-me
Skill1 starsChanged 44 days agoMITView on GitHub
Pressure-test an idea or project and recommend an MVP, technology, delivery workflow, and prototype checkpoint for human selection.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rikilamadrid/lorekeeperword for word, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 1
- rikilamadrid/lorekeeper★ 1100% 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 repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blog-post-redactorSkill
- challenge-meSkill
- debate-meSkill
- debug-issueSkill
- handoffSkill
- hooksmithSkill
- kickstart-pathfinderSkill
- learn-codebaseSkill
- learn-featureSkill
- learning-reviewSkill
- map-systemSkill
- orchestrateSkill
- prototypeSkill
- quiz-meSkill
- reflectSkill
- render-artifactSkill
- reverse-engineerSkill
- roleSkill
- setup-trackerSkill
- skillsmithSkill
- teach-architectureSkill
- teach-featureSkill
- ticketSkill
- to-specsSkill
- to-ticketsSkill
- whereamiSkill
- blog-post-redactorSkill
- challenge-meSkill
- debug-issueSkill
- handoffSkill
- hooksmithSkill
- kickstart-pathfinderSkill
- learn-codebaseSkill
- learn-featureSkill
- learning-reviewSkill
- map-systemSkill
- orchestrateSkill
- prototypeSkill
- quiz-meSkill
- reflectSkill
- render-artifactSkill
- reverse-engineerSkill
- roleSkill
- setup-trackerSkill
- skillsmithSkill
- teach-architectureSkill
- teach-featureSkill
- ticketSkill
- to-specsSkill
- to-ticketsSkill
- whereamiSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill before implementation when important product or technical choices deserve challenge.
- Distinctive: line 12
Read the user's idea and the smallest relevant project context.
- Distinctive: line 40
Only unresolved questions with real consequences.
- Distinctive: line 70
Ask the user to choose:
- Very specific: line 75
leave specific items TBD
- Distinctive: line 78
Do not write approved context until the human responds.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Debate Me
Use this skill before implementation when important product or technical choices deserve challenge.
Inputs
Read the user's idea and the smallest relevant project context. Inspect an existing repo only enough to respect its constraints.
Debate Areas
- user/problem clarity and first useful outcome
- MVP cuts and differentiation
- product, UX, operational, data, integration, security, and maintenance risks
- architecture and technical complexity
- team, budget, deadline, platform, and learning constraints
- testing, deployment, and supportability
- need for an experience or technical prototype
Output
Strongest Version of the Idea
A sharper restatement.
Keep in MVP / Cut from MVP
Protect the first useful version.
Biggest Risks
3–7 risks with practical mitigation.
Questions That Materially Change the Build
Only unresolved questions with real consequences.
Recommended Project Setup
Recommend, when relevant:
- product shape and architecture
- platform/runtime and language
- UI/presentation approach
- backend, database/data access, auth/authorization, APIs
- testing and observability
- deployment/environments
- Git workflow, branching, commits, reviews, CI/CD, versioning, releases
For each choice, explain why it fits and label it recommended, not approved.
Prototype Recommendation
State one of:
- no prototype needed
- experience prototype
- technical proof of concept
- architecture/data-flow prototype
- mixed prototype
Define the assumption to validate, cheapest useful format, review criteria, and what must not be mistaken for production code.
Human Choice
Ask the user to choose:
- accept the recommendations
- modify selected choices
- compare alternatives
- leave specific items
TBD - prototype before deciding
Do not write approved context until the human responds.
Recommended Next Move
Choose prototype, kickstart-pathfinder, to-specs, or pause.
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.