Every verb the binary carries.
This page is generated from the CLI itself — the same snapshot sporo docs --json emits, kept in sync by a build gate. Read the authoring rules with sporo genre.
sporo-recipe — the authoring skill
sporo init writes this skill into your agent. It walks the agent through the cycle below — reading the project's record, not its own memory — and leaves you one file to review.
Write a recipe from the record, gate it against the genre, and hand it over.
Print one recipe (or, with --bundle, a composed set) as a single self-contained file
--bundle=falsetreat <slug> as a bundle manifest and compose its members into one document--root=.project root (searched for this repo's own recipes before the official corpus)File and list report-backs — the channel a recipe's next version comes from
Validate a reader's report-back against the protocol and file it (`-` reads stdin)
List the filed report-backs, per recipe
Gather a recipe's raw material from a revision range of the project's own record
--outwrite the harvest here (default: stdout)--root=.repository to harvest--sincestarting revision, exclusive (a tag: the release before the work)--until=HEADending revision, inclusiveCheck a recipe corpus against the genre — shape, acceptance, scars, and neutrality
--root=.project root (its config names the recipes home and the forbidden product vocabulary)List the recipes available here — this project's own, and the official corpus
--root=.project root (its own recipes are listed alongside the official corpus)Scaffold a draft recipe — coached section stubs, optionally pre-seeded from a harvest
--from-harvesta `sporo harvest --out` file; its scar candidates pre-seed the scars section--root=.project root (the draft lands in its recipes home)--titlethe recipe's title (defaults to a TODO)Build a self-contained review pack for any agent, and verify the verdicts it returns
--root=.project rootValidate returned verdicts and record the tally beside the recipe's seal
Record a recipe's version and content hash in the registry — a sealed recipe never silently mutates
--root=.project root (its registry records the seal)The reader's side: record what you built from, and hold an output to a recipe's exact contracts.
Record a handed-over recipe this repository builds from — the reader-side seal
--root=.repository that adopts the recipe--sourcewhere pull re-fetches this recipe from later — a path or an http(s) URL (default: the file argument)Check an output file against a recipe's exact-bound contracts
--contract=0check against one exact contract by its index (default: all)--root=.project root (searched for the recipe when a slug is given)Check adopted recipes against their sources — loud when an exact contract moved
--apply=falserefresh the stored copy and record for each update (default: report only)--root=.repository whose adopted recipes are checkedPut the authoring surface into a repository and keep it current.
Print this binary's command surface — the source the docs page is built from
--json=falseemit the surface as JSON (what the docs page consumes)--outwrite the JSON snapshot to this file (used by `go generate`)Print the recipe genre spec — the authoring rules this binary enforces
Install the recipe-authoring surface into this repository (skill, AGENTS.md block, seeds)
--root=.repository to initializeList the repositories on this machine that sporo was installed into
Re-sync the managed authoring surface from this binary — never clobbering your edits
--root=.repository to updateKeep the tool itself up to date.
Update this binary to the latest release — then run `sporo update` in each repo
--check=falsereport the latest release and its notes; change nothing