spec-system

Docs Spec System v2

Run all docs-spec operations through the phase-gated v2.4 system.

Runbook

1. Read ../../references/spec-system-rules.md for mandatory schemas and gate invariants.
2. Select the workflow in ../../references/workflows.md that matches the requested change.
3. Use specctl as the primary interface (feature, contract, epic, oneshot, impact, codex, lint, render, check, approve, migrate-v1-to-v2, report).
4. Keep requirements, design, tasks, and verification artifacts synchronized per feature.
5. Enforce R -> D -> T -> S -> evidence traceability before completion.
6. Use ../../references/release-and-pr.md and ../../assets/docs-system-pr-template.md to assemble release/PR outputs.

Required Output For Every Task

• List impacted IDs by type (E, F, R, D, T, S) and operation type.
• Report phase transitions performed (if any).
• Report specctl check result and blocking errors/warnings.
• Call out unresolved traceability gaps or deferred follow-ups.
• For epic work, include one-shot/agentic status details when applicable.

Out-of-Scope Handling

• Do not infer implementation status from source code without explicit evidence.
• Do not run legacy v1 script workflows.
• Do not bypass phase gates unless the user explicitly requests a policy exception.

Skill Resources

• ../../references/spec-system-rules.md: v2 schema, ID grammar, and quality gate rules.
• ../../references/workflows.md: phase-driven execution playbooks.
• ../../references/release-and-pr.md: PR assembly and release validation.
• ../../assets/docs-system-pr-template.md: v2 PR template.
• ../../assets/templates/*.md: canonical feature and governance templates.

Arguments

$ARGUMENTS