spec-factory / specs
CLAUDE.md1 starsChanged 40 days agoMITView on GitHub
Each spec's ## Examples are exact input-to-output cases the tests reproduce verbatim, and each names the source its expected value comes from. An older spec may also carry an ## Acceptance Anchors section a human ratified with RATIFIED <ISO date> by <email>; that section is frozen, a hook blocks any edit to it, and changing it takes a change proposal under docs/factory/changes/.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- sf-grillSkill
- sf-handoffSkill
- sf-ideaSkill
- sf-improveSkill
- sf-ingestSkill
- sf-prdSkill
- sf-reviewSkill
- sf-specSkill
- sf-tddSkill
- sf-uxSkill
- specfactorySkill
The file
Files
specs/
Each spec's ## Examples are exact input-to-output cases the tests reproduce verbatim, and each names the source its expected value comes from.
An older spec may also carry an ## Acceptance Anchors section a human ratified with RATIFIED <ISO date> by <email>; that section is frozen, a hook blocks any edit to it, and changing it takes a change proposal under docs/factory/changes/.
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.