A method for building software with agents, packaged as a single binary. Every rule that matters is written twice — once as prose that says why, once as a check that fails — and every check has a mutation that proves it fires.
This repository also configures its own agents. See what software-factory tells them →
Skill Claude CodeCodex
Turn a requirement into machine-checkable policy for the software factory — gates, activation paths, required assertions, and new catalog rules. Use when starting a phase of work that needs a completion gate, when a convention keeps being re-explained in review, or when someone asks "how do we stop this from happening…
Skill Claude CodeCodex
Create or run the proof behind a software-factory L3 gate and seal evidence that survives re-verification. Use when a feature needs its first gate, when a gate is red for missing or stale evidence, or when asked to prove a change actually works end to end.
Skill Claude CodeCodex
Interview someone about their project's architecture and stack, then generate the software-factory rules those answers imply. Use when setting up sf in a repository for the first time, when someone asks what rules their project should have, or when an architectural decision changes and the policy should follow it.
Skill Claude CodeCodex
Read a software-factory report, explain what actually broke, and fix it. Use when sf check or sf verify is red, when CI fails on a factory rule, or when someone asks whether a rule is worth keeping.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: