Template repository · use with Claude, Codex, or any AI assistant
A pattern language for running the full software development lifecycle with AI assistants — as a team of one.
One thread runs through it all: spec → plan → commit → gate → release → QA charter — walkable in both directions, for every shipped feature.
The model in the loop will change. The harness is what compounds.
You are one person. Your “engineering team” is you plus one or more AI assistants — and the thing that makes that work is not the model. It is the harness: the repo conventions, commands, gates, and documents that let any assistant pick up work, verify its own output, and ship, without you re-explaining the project every session.
A solo developer’s constraint is no longer typing speed; it is verified attention — how much shipped change you can actually stand behind. Each pattern here converts something you would have to remember, repeat, or manually check into something the repository enforces — and add-on layers extend the same loop to corporate trackers, security, privacy, and on-device debugging.
What is true about this project?
How does the assistant know it’s done?
How does work land safely — even with many agents at once?
What persists between sessions, where does everything live, and who is working on what right now?
How does work flow in from the org’s tracker, and how much autonomy does each ticket get?
How does security knowledge become permanent, and what must never leave your control?
How do unfinished features ship safely, and how do old clients keep working?
How does an assistant see details instead of the gist?
How do juniors become seniors when AI does junior-shaped work?
Click Use this template on GitHub. You get the module skeleton — backend/, web/, mobile-app/, webservices/ — and the full pattern language in the README.
Open the repo in Claude Code, Codex, Cursor — whatever you use. Paste the kickstart prompt from the README.
Constitution, docs tree, justfile verbs, CI gate, memory index, session ledger, sitemap — then it stops, and feature work begins with a spec you approve.