writ

Survey an existing codebase and put an agent-first development process around it — area registers read off the code and its history, a debt register, an enforcement perimeter that starts empty, and the sixteen project skills. Use when adding this process to a repository that already has code, especially one other people are still working in.

Offer writ something this project built that other writ projects could use — find what the project changed or added to its process, judge honestly whether it is general, strip everything private, and file it as a GitHub issue on writ's repository for writ's maintainers to consider. Never a pull request, never code pushed. Use when the user says to contribute, push, send back or share an improvement with writ.

Interview one developer and generate their project's agent-first development process — specification, registry, slice queue, CI gate, coverage ledger and sixteen tuned project skills. Use when starting a greenfield project built by one person plus coding agents.

Interview a team and generate their project's agent-first development process with named roles, handoffs, WIP limits and CODEOWNERS on top of the solo kit. Use when starting a project that more than one person will build.

Offer a project that already runs writ's process the enhancements writ has gained since — read the kit's changelog past the project's baseline, check each entry against what the project already has, interview the user on which to take and how to adapt them, then port only those, in the project's own names and shape. Use when the user asks to update, sync or pull enhancements from writ into a project bootstrapped or adopted from it.