KI Specifications repository structure
Apply the intentionally small repository-structure standard for KI Specifications. The repository remains a standard ki-repo in every general respect; this skill names its structural identity and protects only the stable top-level seams that distinguish a specification authority.
This is a governance skill. It deliberately governs repository structure without taking ownership of normative specification content.
The current floor is deliberately sparse. Detailed KIP/KIS content rules, numbering, lifecycle, conformance semantics, and publication formats remain canonical in the Specifications repository itself and should be promoted into this skill only after they prove stable and reusable.
Read the standard for the current floor, the rubric for checkable criteria, and the source list when refreshing it. The ki CLI runs the mechanical checker.
Canonical shape
ki-repo-specifications/
├── proposals/
├── specifications/
├── schemas/
├── templates/
├── examples/
├── docs/
├── tooling/
└── .ki.toml # [skills.ki-repo] + keyless [skills.ki-repo-specifications]
Operating modes
Mode AUDIT
- Run
ki repo audit --repo <repo> --skill ki-repo-specificationsand capture its findings. - Confirm the repository declares
[skills.ki-repo-specifications]; only that declaration selects this optional standard. The structural audit then observes the seven top-level areas without judging their evolving internal contents, freshness, or outcomes. - Apply the judgment criteria in the rubric, especially whether a proposed new invariant is mature enough to belong here.
Mode CONFORM
- Run AUDIT first.
- The selected repository declaration is owned by
ki-repo; this structural skill does not add it. Resolve a missing declaration through the repository configuration owner before running this standard. - Create a missing top-level area only after confirming its intended contents; an empty directory cannot be governed by git, so the conformer does not manufacture placeholders.
- Re-run AUDIT.
Mode EDUCATE
- Establish a normal
ki-repofirst. - Add this skill to the repository through
ki repo skill add ki-repo-specifications --repo <repo>. - Add the seven top-level areas with their first real artefacts, then run AUDIT.
Mode HELP
Explain the skill's purpose, modes, invocation, and boundaries without changing the target.
Mode REFRESH
Precondition: REFRESH writes only in ki-agentic-harness. When invoked from an installed copy, stop and redirect the work to the Harness source repository.
- Read the source list and inspect the live KI Specifications repository.
- Promote only stable, repeated structural constraints; leave changing specification-process detail in that repository.
- Update the standard, structured catalogue, tests, and source review together, then regenerate the rubric publication with
ki dev skill rubric ki-repo-specifications --write.
Boundaries
- Universal repository files, licensing, GitHub settings, and security belong to
ki-repo. - Markdown/TOML style belongs to
ki-authoring. - Decision collections belong to
ki-decision-records; non-KB planning belongs toki-work-roadmap. - Normative KIP/KIS meaning remains owned by KI Specifications, not by this structural checker.