sellke/writ
Agree what to build, let the model build it, and see proof it works. A workflow for product managers working with an AI coding agent.
Start here for any Writ work. Say what you want in your own words; Writ says it back, picks the right step (plan, research, prototype, spec, build, verify, ship), and begins. With no request it reports where the project stands and what is waiting on you. Use for "/writ", "what's next", "where are we", or any product request in a project that uses Writ.
Build what an agreed spec describes and come back with proof. The model plans and builds its own way, an independent verifier checks every acceptance criterion against the running product, and the person hears only about changes to the contract. Use with a spec, a roadmap item, or "build the next thing". Part of Writ.
Capture a bug, idea, or improvement in under two minutes without losing the thread of current work. Use for "note this", "file a bug", "remind me to", "add this to the backlog". Part of Writ.
Optional second reader for Writ, backed by TypeSafe's Jev. Flags unclear, contradictory, or incomplete acceptance criteria before a contract is agreed, and proof lines whose evidence does not show what they claim. Used by writ-spec and writ-verify; run directly to turn it on or off or to check its status. Part of Writ.
Plan or re-plan the product with the person - who it serves, the problem, the objective and how it is measured, and the roadmap of bets in order. Use for a new product, a change of direction, or to bring the plan back in line with what shipped. Part of Writ.
Try an idea as two or three real, working drafts that differ in ways that matter, so the person can pick a direction by looking instead of guessing. Use when the shape is unsettled, when it is about look and feel, or when a question can be answered by building something small. Part of Writ.
Answer a question with evidence and a recommendation - why something in this project is the way it is, what the options are, what others do, whether an idea holds up. Use before a decision, not for quick lookups. Part of Writ.
Look back after something ships - did it move the measure, what was learned, and what should change on the roadmap and in how the team works with the agent. Use after a release, at the end of a roadmap item, or when a measure comes due. Part of Writ.
Take proved work to a pull request and, on the person's word, merge it and release it. Writes the pull request in plain language with the proof attached, gets it ready to merge, and handles versions and release notes. Use for "ship it", "open the PR", "merge", "release". Part of Writ.
Agree what will be built before anything is built - the problem, the outcome and its measure, what is in and out, and the acceptance criteria - and write it as one spec file the person signs off. Also changes an agreed spec. Use for any capability users will rely on. Part of Writ.
Prove or disprove, independently, that what was built meets its spec - check each acceptance criterion against the real running product and write the Proof into the spec. Used by writ-build through a fresh helper, or directly for "does this work?", "prove it", "check this branch". Part of Writ.