workflow-contractslisted

# How the workflow is wired One job: say where things are and which file settles a disagreement. Every rule this skill points at lives in the file named, not here — a second copy is a copy that drifts. ## The skills are global; the facts are per project The skills in this suite are shared by every project. Nothing in them names a project. They take project-specific facts from **`.claude/workflow.json`** in the working directory — which records to write, which commands to run, which branch integrates and which publishes. **A project without a manifest still works.** Skills fall back to conventional filenames, skip what they cannot resolve, and **say in one line that they did**. A skipped step announced is a step the user can overrule; a skipped step inferred from a fallback is one nobody sees. When a skill reports falling back, the fix is `--adopt` (`adopt-workflow`), which writes the manifest. ## The three files that settle disagreements Relative from any skill file, which is what makes them resolve in both install forms: - [`../../workflow/ownership.md`](../../workflow/ownership.md) — **who may write what.** The invariant: every record file has exactly one writer. An orchestrator that needs a record written calls the primitive that owns it, even when the edit is one line and obviously correct. - [`../../workflow/record-contract.md`](../../workflow/record-contract.md) — **what each record holds, and what it must never hold.** - [`../../workflow/manifest.md`](..