spec-kickofflisted

# /spec-kickoff The comprehension layer of the planwright pipeline (REQ-B2.4, REQ-B2.2): a section-by-section walkthrough of a spec bundle until human and agent hold the same understanding, recorded as `specs/<spec>/kickoff-brief.md` — the durable contract (two-brief model, D-3). Downstream skills (`/execute-task`, `/orchestrate`) operate from the brief, not the spec; what this walkthrough gets wrong, execution gets wrong. The agent probes, the human corrects. Sign-off is the first key of a two-key launch (D-44): it flips the spec Draft→Ready and, on a clean completion, marks the spec PR ready (D-6, D-7; the walkthrough is the bundle's review). The human's merge is the second key, making the Ready spec operational (the first dispatch derives Active, not this skill). This skill marks only the spec PR ready, never merges, never dispatches execution. ## Doctrine This skill is procedure, not doctrine. Resolve and read the run-start rule docs via the rule-doc resolution convention (`scripts/resolve-rule-doc.sh <doc-name>` under the resolved planwright root); their definitions govern wherever this skill names a concept: - `security-posture` — artifact data-hygiene: the brief and risk register are committed. **Invoking plugin scripts (REQ-D1.1, D-7).** Call `scripts/<name>.sh` by the **resolved literal absolute path**, never `$VAR/scripts/<name>.sh` — `doctrine/plugin-script-invocation.md`. `spec-format` (pre-flight step 2) — the meta-spec: bundle format, status lifecycle,