spec

# Specification Authoring Use this skill to create or update durable specifications. Requirements define observable behavior. System designs define the technical path that satisfies requirements. The canonical rules are in `docs/specs/guide/`. Read these files before you write an artifact: - Always read `structure-and-ownership.md`. - Read `requirements.md` for requirement work. - Read `system-design.md` for system-design work. - Read `traceability-and-lifecycle.md` for IDs, statuses, references, or migration work. Use the templates in `docs/specs/templates/`. ## Artifact routing Route the request before you write: | Request | Artifact | | --- | --- | | Kandev-wide purpose, actors, principles, measures, or constraints | `docs/specs/product/` | | Observable behavior for one owning system | `<system>/requirements/` | | Technical contracts, models, boundaries, or control flow | `<system>/system-design/` | | Durable choice with meaningful alternatives | `/record` and an ADR | | Delivery sequence and implementation tasks | `/plan` | | Incident or behavior-preserving refactor | No product requirement | | Bug | `/fix`, which checks the existing requirement first | Do not create a generic `spec.md` file. When routing to `docs/specs/product/`, read `docs/specs/product/README.md` before editing. Treat its **Product document index** as the local index: read every linked product document and any co-located `INDEX.md`, `AGENTS.md`, `CLAUDE.md`, or other instruction file when pr...