spec-charter
spec-charter
Own spec/charter.md (direction: what good looks like and why) and spec/system-map.md (system shape: boundaries, flows, invariants, pointers). Capability contracts in spec/capabilities.md belong to spec-grill. File roles, topology, the harness pointer, and the legacy root CHARTER.md fallback live in references/spec-axis.md. This skill ships no scripts: inspect the target repo directly and keep paths target-repo-relative.
The charter stays under a ~5-minute read; operational how-to belongs in harness files or an operational notes file (such as _context.md), not the charter. Absence is supported — projects opt in by creating the files.
Execution contract
Mode router
Explicit mode words win. Next, intent: map for system shape, architecture, runtime boundaries, flows, invariants, or spec/system-map.md; reassess for a report-only staleness or spec-health check. Only then file state: create when neither spec/charter.md nor a legacy root CHARTER.md exists, otherwise amend — taking the reset path when the user describes a concept change rather than an edit. Capability contracts route to spec-grill.
Completion contract
Every run names the files created or changed, what was refused or parked (a refused harness pointer counts), and one next action in plain language — never a memorized argument. Done means: