Reference

The short operating manual.

Install commands, terms, runtime fit, and recovery checks in one place for quick handoff and review.

Primary install.

This is the command most Codex app users should start with. The reference tables below include preview and opt-out variants.

Codex install

npx skills add jddelia/software-factory \
  --agent codex \
  --global \
  --yes

Primary install: npx skills add jddelia/software-factory --agent codex --global --yes
Preview detection: npx skills add jddelia/software-factory --list
Telemetry opt-out: DISABLE_TELEMETRY=1 npx skills add jddelia/software-factory --agent codex --global --yes

Project record: The repo-local docs that describe current state, ownership, proof, blockers, and next action.
Handoff: A compact transfer bundle with objective, scope, files changed, proof commands, known risks, and resume notes.
Baton: The explicit ownership marker used in deeper factory workflows. It should only move when the next owner is clear.
Acceptance evidence: The checks, screenshots, review notes, logs, or deployment proof behind a done claim.

Primary runtime: Codex app, because it supports delegated threads, tool permissions, browser QA, goals, checkpoints, and long-running handoffs.
Alternative runtimes: Use the docs-first protocol manually when another runtime has fewer orchestration primitives.
Companion control plane: Agentic Factory adds durable state and controls when seeded docs are not enough.

Inspect before cleanup: Read git status, diffs, process state, ports, worktrees, and recent proof before deleting or reverting anything.
Preserve useful work: Move valuable artifacts into an explicit location before removing abandoned branches or worktrees.
Resume only with ownership: Assign a clear owner and next action before implementation continues.

Words like baton and acceptance evidence are useful once defined. The public pages introduce them where they can be understood, not in the hero.

The reference keeps recovery close to install and runtime guidance because messy state is one of the core problems the skill solves.

The standard is evidence-backed completion: commands, screenshots, review notes, logs, deployment proof, or an honest blocker.