writing-plans

# writing-plans ## Authoritative format boundary For a new full-lane HTML spec, load [includes/artifacts.md](../../includes/artifacts.md) and use the installed structured-artifact engine for every spec and plan read or write. The resulting pair is `.codearbiter/specs/<slug>.html` and `.codearbiter/plans/<slug>.html`. Missing or invalid HTML capability is a STOP before writing and must not fall back to Markdown. An existing authoritative Markdown spec continues through the legacy Markdown path without conversion. HTML `--farm` dispatch remains blocked. Turn an approved spec into an executable plan, or prepare a ready draft plan for initial combined HTML sprint review. Draft preparation is not execution authority. Routed to by `/feature` (after spec approval) and `/sprint` under its explicit call mode. ## Pre-flight Read these, or STOP and surface the gap. Missing specs always block. Ordinary planning requires approval; only initial full-lane HTML sprint-pair preparation accepts an exact ready draft: - The authoritative approved spec selected by `/feature`: for HTML, resolve it through the installed engine and verify its ready approval and exact identity; for legacy Markdown, read `<project-root>/.codearbiter/specs/<slug>.md`. Absent → STOP. Unapproved → STOP except the explicit initial sprint `draft_for_pair` mode, which verifies ready/current draft identity through the private preflight and never grants execution. Route a genuine missing prerequisite back to ...