spec-kitty.charter

# /spec-kitty.charter - Interview + Compile Charter ## User Input The content of the user's message that invoked this skill (everything after the skill invocation token, e.g. after `/spec-kitty.<command>` or `$spec-kitty.<command>`) is the User Input referenced elsewhere in these instructions. You **MUST** consider this user input before proceeding (if not empty). ## Repo Scope `/spec-kitty.charter` is a repo-scoped governance flow, not a per-mission flow. - Run it from the repository root. - Do **not** try to resolve a mission handle for this command. - For charter subcommands, `--mission-type` means the reusable mission blueprint (for example `software-dev` or `documentation`), not a mission instance in `kitty-specs/`. - The hidden `--mission` flag on `spec-kitty charter ...` is only a deprecated alias for `--mission-type`. If you need deterministic context before interviewing: 1. Confirm you are in the repo root. 2. Check whether a charter already exists: ```bash spec-kitty charter status --json ``` 3. If needed, inspect available mission blueprints: ```bash spec-kitty mission list ``` For this command, the default mission type is `software-dev` unless the user explicitly wants a different mission blueprint. ## Skill Load Before proceeding, load the `spec-kitty-charter-doctrine` skill for the charter lifecycle model, doctrine access patterns, and action-context rules. If the skill conflicts with this command contract, follow this command contract. ## ...