adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so…
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
$ npx -y skills add spec-kitty/spec-kitty --skill spk-charter-spdd-reasons --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/spk-charter-spdd-reasonsContext 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
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.
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`.
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.
refining.
charter; escalate to the charter workflow.
`spk-charter-glossary`.
canvas authoring and review, charter precedence, glossary discipline, and reference paths.
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.
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so…
Understand how Spec Kitty manages git: what git operations Python handles automatically, what…
Orchestrate the implement-review loop for Spec Kitty work packages using any configured…
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify…
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define…
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows…