superpowers-test-driven-development
Skill0 starsChanged 22 days agoMITView on GitHub
Desenvolver um comportamento novo a partir de uma regressão que distingue erro e correção.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- christopherarter/superpowers-reasonixtheir own version, first seen Nov 1, 2026
- EvovexAI/EvoFlowtheir own version, first seen Oct 8, 2026
- host452b/polishtheir own version, first seen Sep 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- EvovexAI/EvoFlow★ 612same name
- christopherarter/superpowers-reasonix★ 101same name
- host452b/polish★ 2same name
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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- code-reviewSkill
- graphifySkill
- grill-meSkill
- integration-testsSkill
- java-spring-apiSkill
- postgres-flywaySkill
- superpowersSkill
- superpowers-systematic-debuggingSkill
- superpowers-verification-before-completionSkill
- superpowers-writing-plansSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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 17
No corretor, comandos continuam proibidos: escreva a regressão antes da mudança e deixe a execução para os jobs independentes.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Red → Green → Refactor
Comece pelo teste de um comportamento observável e pela entrada mínima que demonstra o erro. Quando comandos forem permitidos ao implementador, observe a falha antes de corrigir; se o teste falhar por infraestrutura, isso ainda não é o red do defeito.
Faça a mudança mínima e confirme a regressão e os testes relacionados. Refatore apenas depois, mantendo o contrato e sem aumentar o escopo. Não enfraqueça asserções para obter green.
No corretor, comandos continuam proibidos: escreva a regressão antes da mudança e deixe a execução para os jobs independentes. Não declare red/green observado por você nessa fase.
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.