spec-kitty-spdd-reasons
SolidDrive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. 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 doctrine pack (escalate to charter workflow instead). Does NOT mirror code as prose; code remains the source of truth for current behavior.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- Priivacy-ai
- Repository
- Priivacy-ai/spec-kitty
- Created
- 7 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
speckit-coach
Helps with SpecKit / Spec-Driven Development problems. Use when the user is stuck on: a failing simplicity gate or gate-validator rejecting acceptance criteria, deciding which checklist domains apply (api, security, observability, data-integrity, resilience), writing testable acceptance criteria the gate accepts, decomposing a large feature into multiple specs, creating a multi-spec technical roadmap, understanding the consensus protocol or how phase gates work, the difference between specify plan and specify tasks, what each /speckit-<command> does, how the tdd-mandate preset changes the workflow, where grill-me or clarify fit in the SDD process, repairing an existing speckit-pro project, making template customizations upgrade-safe, or browsing, installing, configuring, or removing SpecKit community extensions, presets, hooks, or catalog entries (verify, doctor, review, archive, retrospective, jira, azure-devops, and the rest of the upstream catalog). Not for actually running autopilot ($speckit-autopilot),
speckit-scaffold-spec
Prepare a SPEC-ID from the technical roadmap for autonomous execution in Codex. Creates or reuses the spec branch and worktree, copies the workflow template, fills the phase prompts, commits the workflow artifacts, and updates roadmap status.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter", "sync charter", "use doctrine", "set up governance", "charter status", "extract governance config", "load doctrine", "agent profile", "DoctrineService", "action index". Does NOT handle: generic spec writing not tied to governance, direct runtime loop advancement, setup/repair diagnostics, or editorial glossary maintenance.
spec-driven-development
Specification-driven development index. Defines spec structure, REQ format, Status semantics, three autonomy modes, and routes to sub-command skills (sdd-init for bootstrap, sdd-clean for rescue). Holds the small sub-commands (edit, add, mode), Plan Mode integration, test discipline, templates. Invoked via /sdd.
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 5-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior. Triggers: "what missions are available", "how do missions work", "which mission should I use", "explain the mission system", "what is a mission", "change the mission", "mission templates", "step contracts", "action index", "mission procedures". Does NOT handle: runtime loop advancement (use runtime-next), setup or repair (use setup-doctor), governance (use charter-doctrine), or glossary curation (use glossary-context).