spec-draftlisted

# /spec-draft The authoring entry point of the planwright pipeline (REQ-B1.1): a Socratic, interactive elicitation that turns an idea plus its seed material into a compliant four-file bundle at `specs/<spec>/`, Status Draft, committed on the spec branch. Drafting ends where comprehension begins: `/spec-kickoff` walks the Draft to sign-off and flips it Ready. This skill never pushes, never opens a PR, and never flips a status to Ready — sign-off is a reserved human control it has no business near. ## Doctrine Resolve and read the run-start rule docs via the rule-doc resolution convention (`scripts/resolve-rule-doc.sh <doc-name>` or the documented `PLANWRIGHT_ROOT`/`CLAUDE_PLUGIN_ROOT` chain): `interaction-style` (governs every exchange in the flow), `research-rigor` (REQ-D1.5 wires its triggers into drafting), `security-posture` (artifact data-hygiene for everything committed), and `proportionality`. Four more are read point-of-use, at the step that applies them: the elicitation reads `spec-format` at its start (the meta-spec the bundle must conform to — its structural conventions govern every phase's output and the Completion bundle write; the gists the earlier steps need are stated inline — the extend-mode terminal-state refusal at Pre-flight, the append/supersede discipline at Extend mode — so only the full law defers, and no bundle write happens before the load); the design phase reads `engineering-decisions` (governs design-phase recommendations) and `customization-bou