emergent-spec-review
Skill1 starsChanged 3 months agoNo licenceView on GitHub
Dual-axis review of one frozen spec document — two context-isolated reviewers judge the same text in parallel: one holds the complete conversation and checks decision fidelity in both directions, one holds no conversation and checks whether an implementer could build and verify it. Each returns its own mechanically validated blocker findings without touching the reviewed file. Use when a spec needs review before implementers receive it, when a spec-production pipeline dispatches a review round, or when the user asks to review a spec document from any source.
In this repository14 other files it gives its agents.
- emergent-adrSkill
- emergent-designSkill
- emergent-grillSkill
- emergent-implementSkill
- emergent-implement-ticketsSkill
- emergent-to-specSkill
- emergent-to-ticketsSkill
- extract-grill-sessionSkill
- extract-transcriptSkill
- forge-agentSkill
- forgeSkill
- git-commitSkill
- run-long-iterationSkill
- transcript-pathSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.