ossify

Adopt an existing project into ossify — six fail-closed gates, six conversions (journey re-marked shipped|next|later, the current cut as a present-tense clean-checkout test, bones back-derived from ADRs, Release 0 closed retroactively, artifacts reconciled, demo-ledger seed candidates recorded), and an adoption record. For the codebase that already has code, tests, history, and decisions; /ossify:start refuses it.

Stress-test a plan or design by interview, or run an adversarial audit of a written spec or plan with an optional external fresh-frame adversary. Activate on "grill me", "stress-test this", "pressure-test this", "challenge my design", "poke holes", "what am I missing", "audit this spec", "adversarial review", "deep audit", "fresh-frame review", or /ossify:challenge. Ossify's lifecycle moments call both modes internally — the bone grill gate, the spec-core close audit, the release class veto, the spine plan and close audits.

Run the ossify close ceremony — one skill, three scopes, routed from the id shape (a work item r1.s2.w3, a spine r1.s2, a release r1). Use when the user says close work item r1.s2.w3, close the spine, close spine r1.s2, close the release, run the close ceremony, run the impl-check gate, or /close <id>. Not spine decomposition or spec/demo-criteria authoring (/plan-spine), not release selection or the bone/flesh declaration (/plan-release), not executing a work item (/work-item).

Diagnose an ossify project and name the remedy for what it finds — state health and state-vs-repo drift, rotting demo lines, outstanding fakes, patch records, orphan worktrees, lean-spec validation, machine-checkable-rule authoring, the Claude/Codex interop check, the skill budgets, and plugin provenance. Use when the user says run doctor, check project health, validate the spec, add a project rule, check Codex interop, find orphan worktrees, check plugin provenance, or /ossify:doctor. Not the close gates (/close), not onboarding (/start).

Ship a defect in shipped behaviour, or a small request from another project that it cannot fake, as a versioned patch off the default branch — reproduce-first for a defect, acceptance-criteria-first for a request, then a PR and a tag. Use when handed issue numbers or a described defect to fix outside any spine, or on /ossify:patch. Not new scope (the intake queue), not a large request (/plan-spine), not a change nothing observes (close's direct-commit patch lane).

Plan an ossify release — groom the feature map into spines, phrase exit criteria as user journeys, sequence spines by DAG, declare each spine bone or flesh under a fail-closed internal critic veto, and emit RELEASE.md. Use when the user wants to plan a release, groom the feature map, pick spines for the next release, plan Release 0 (the skeleton), or runs /plan-release. Requires a project onboarded via /start. Not spec-core onboarding (/start) or spine decomposition (/plan-spine).

Plan one ossify spine — decompose it into 1-5 work items, identify rounds via a DAG, author a spec per round, and author the cumulative-demo criteria under the journey-line floor. Use when the user wants to plan a spine, decompose a spine into work items, author demo criteria, start building a spine, or runs /plan-spine. Requires a release planned via /plan-release. Not release selection or the bone/flesh declaration (/plan-release), not spec-core onboarding (/start).

Drive ossify spec-core onboarding for a new project — the Patton journey map, the skeleton cut that fixes Release 0, the bones registry, and the privacy posture with its moat channels — producing a lean MASTER-SPEC, memory bank, bones ADRs and a seed feature map. Use when the user wants to start a new project, onboard a project into ossify, kick off a skeleton-first build, or runs /start. Resolves or authors the topology declaration; halts only if it still fails to resolve. Not release planning (/plan-release), spine decomposition (/plan-spine), or amending an existing spec (/amend-spec).

Decision-ticket maps on an issue tracker — chart a question into a map plus its research/smoke-test/spike/prototype/grilling/task tickets, or work an existing map's frontier one ticket per session. Activate on a wayfinder map name, number, or URL, a loose decision-shaped question too big for one session, or /ossify:wayfinder. Not release or spine planning — those stay build-slice DAGs (/ossify:plan-release, /ossify:plan-spine).

Execute one ossify work item end to end from its handoff doc — pre-flight gates, a RED gate per command-bearing AC, the TDD loop, a report.md, then stage-never-commit and one structured JSON return. Also drives a spine's rounds. Use when the user says execute work item r1.s2.w1, implement the work item, run the handoff at <path>, run the rounds, execute the spine, dispatch the work items, or /work-item. Not spec or demo authoring (/plan-spine); not the work-item gate, demo, harvest or retro (/close).