spec-kitty-spdd-reasons

Generates and reviews REASONS canvases for Spec Kitty missions using structured prompt-driven development.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spec-kitty-spdd-reasons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kitty-spdd-reasons
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-spdd-reasons
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spec-kitty-spdd-reasons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven missions often lose the reasoning behind requirements, approach choices, and safeguards once implementation begins, making reviews unable to detect scope drift or safeguard violations. This Skill maintains a REASONS canvas alongside spec, plan, and tasks so agents and reviewers can trace diffs back to intent.

Core Features & Use Cases

  • Canvas Authoring: Generates or updates kitty-specs/<mission>/reasons-canvas.md from a seven-section template (Requirements, Entities, Approach, Structure, Operations, Norms, Safeguards), linking to source artifacts instead of duplicating them.
  • Charter-Gated Activation: Detects whether the SPDD/REASONS doctrine pack is active via .kittify/charter/governance.yaml, handling active, ad-hoc, and enforcement-demand scenarios differently.
  • Comparison-Mode Review: Traces implementation diffs against the canvas and classifies divergences using an eight-level drift taxonomy, blocking on scope drift or safeguard violations.
  • Use Case: A reviewer asks whether a work package diff matches mission intent; the Skill maps each changed file to canvas Requirements and Operations, flags uninvented entities, and records approved deviations in the append-only Deviations section.

Quick Start

Ask the agent to generate a REASONS canvas for the current Spec Kitty mission and confirm the SPDD doctrine pack is active in the charter.

Frequently Asked Questions about spec-kitty-spdd-reasons

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

FAQPage Schema
How do I generate a REASONS canvas for a Spec Kitty mission?

Invoke the skill on a mission whose charter selected the SPDD/REASONS pack. It reads spec.md, plan.md, tasks.md, and related artifacts, then writes kitty-specs/<mission>/reasons-canvas.md using the seven-section template, linking to sources rather than duplicating them.

How does REASONS canvas review detect scope drift in a diff?

The review traces every changed file to a Requirement and Operation in the canvas, detects entities absent from spec, plan, and glossary, then classifies each divergence with the drift taxonomy. scope_drift_block and safeguard_violation_block prevent landing.

Can I use the REASONS canvas without charter opt-in?

Yes, for ad-hoc requests the skill proceeds but stamps the canvas header noting it is not formally opted in via charter, making it advisory only. Enforcement as a gate requires running the charter workflow to add the paradigm or directive first.

Does the REASONS canvas duplicate my spec and code documentation?

No. The canvas links to source artifacts with references like spec.md sections instead of inlining content. Code remains the source of truth for behavior, and existing user-authored canvas content is merged, never overwritten.

What happens when the canvas conflicts with the charter?

The charter always wins as the governance source of truth. Any canvas claim contradicting a charter directive, tactic, or norm is classified as canvas_update_needed, and the canvas must be corrected rather than the charter.