spec-kitty.charter

Generate and validate repo-scoped charter artifacts from interview answers.

Updated May 13, 2026
One-click install
npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-charter-kimprobably
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kitty.charter
Source: https://github.com/kimprobably/maestro-os/tree/main/.agents/skills/spec-kitty.charter
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-charter-kimprobably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns project intent from a short interview into a persisted governance charter that the repo tooling can generate and validate.

Core Features & Use Cases

  • Repo-scoped charter setup: Ensures the charter workflow is run from the repository root and targets the correct mission blueprint (e.g., software-dev) rather than a mission instance.
  • LLM-led interview-to-persistence: Inspects the repo for high-signal context, asks focused questions, and synthesizes answers into .kittify/charter/interview/answers.yaml.
  • Generate + verify charter artifacts: Runs spec-kitty charter generate --from-interview --json and confirms results with spec-kitty charter status --json, committing charter changes when diffs are produced.

Quick Start

Run the charter interview by invoking /spec-kitty.charter and answer the questions to generate and verify .kittify/charter/charter.md.

Frequently Asked Questions about spec-kitty.charter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a project charter from interview answers?

To generate a project charter, run an interactive chat interview to collect user intent, synthesize answers into `interview/answers.yaml`, and execute `spec-kitty charter generate --from-interview --json` to produce the charter artifacts.

What is a repo-scoped charter workflow for project governance?

A repo-scoped charter workflow is a process that selects a mission blueprint, collects project intent through interviewing, and persists governance artifacts under the `.kittify/charter/` directory for end-to-end validation.

How do I verify project charter artifacts after generation?

You verify project charter artifacts by running `spec-kitty charter status --json` after generation, which checks the output and confirms whether charter diffs need to be committed to the repository.

Can I use project charter generation outside of the repository root?

No, charter generation must be run from the repository root to ensure the workflow correctly targets the mission blueprint and persists outputs under the `.kittify/charter/` directory structure.

What is the best way to compile project intent into a persistent governance charter?

The best way to compile a governance charter is through an LLM-led interview that inspects the repo for context, asks focused questions, and deterministically generates persistent charter outputs from the synthesized answers.

Why does charter generation require an interview instead of direct file creation?

Charter generation requires an interview because the workflow needs to collect high-signal user intent and repository context, synthesizing these focused answers into `answers.yaml` before deterministically generating the charter.