Skip to content
Agent Orchestration
Skill

/spk-charter-spdd-reasons

Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection, and review structured prompt rationale. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured

BOOST
From plugin
spec-kitty
1.7k45 skills1 command
Install
$ npx -y skills add spec-kitty/spec-kitty --skill spk-charter-spdd-reasons --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/spk-charter-spdd-reasons

Context preview

The summary Claude sees to decide when to auto-load this skill.

Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection, and review structured prompt rationale. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured

SKILL.md

spk-charter-spdd-reasons.SKILL.md
name: spk-charter-spdd-reasons
description: >-
  Drive REASONS Canvas authoring and review for Spec Kitty missions that
  opted in to Structured-Prompt-Driven Development (SPDD) via charter
  selection, and review structured prompt rationale.
  Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas",
  "apply structured prompt driven development", "make this mission SPDD".
  Does NOT handle: enforcing SPDD on projects whose charter has not
  selected the SPDD/REASONS artifacts (escalate to charter workflow instead).
  Does NOT mirror code as prose; code remains the source of truth for
  current behavior.

spk-charter-spdd-reasons

Use this skill when a mission opts into SPDD, REASONS Canvas work, or structured prompt rationale review. The canvas is a thin, agent-curated reasoning layer next to the spec, plan, and tasks, stored at `kitty-specs/<mission>/reasons-canvas.md`.

Flow

1. Confirm SPDD is selected by charter or mission context (`is_spdd_reasons_active` in `src/charter/offering/spdd_reasons/activation.py`). 2. Author or review the REASONS Canvas before downstream prompts depend on it, using its seven sections: Requirements, Entities, Approach, Structure, Operations, Norms, Safeguards. 3. Keep rationale tied to mission decisions, not generic process commentary. 4. In review, trace the diff against the canvas and classify divergences with the drift taxonomy. 5. Return approved rationale to specify, plan, or implementation steps.

Boundaries

  • Do not mirror the code as prose; reference source artifacts instead.
  • Do not overwrite user-authored canvas content; merge by appending or

refining.

  • Do not silently enforce SPDD on a project that did not opt in through its

charter; escalate to the charter workflow.

  • The charter wins over the canvas; escalate glossary conflicts to

`spk-charter-glossary`.

References

  • `references/reasons-canvas-workflow.md` -- Activation rules and detection,

canvas authoring and review, charter precedence, glossary discipline, and reference paths.

Read more
Ships withspec-kitty

Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and consistent engineering standards across AI coding agents and harnesses.

Get the whole plugin

Other skills on spec-kitty.