spec-kitty
- 138 skills
- 0 followers
- 1.7k repo stars
- last month last updated
- ▌ Spec Kitty Design 2 · spec-kitty bundleUse this skill to generate, review, or work with Spec Kitty branded interfaces and design system artifacts. Triggers on: UI component work, CSS token usage, brand copy writing, Storybook story authoring, doctrine artifact authoring, or any request to produce SK-branded visual output. Also triggers for: "add a component", "write brand copy", "check token usage", "create a story".
- ▌ Spk Doctrine Glossary · spec-kittyCurate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests.
- ▌ Spec Kitty Glossary Context · spec-kitty bundleCurate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency", "shape a domain model's terms", "validate domain language against code". Does NOT handle: runtime loop advancement, setup or repair requests, agent configuration, or direct code implementation tasks.
- ▌ Spec Kitty Design · spec-kitty bundleUse this skill to generate well-branded interfaces and assets for Spec Kitty, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
- ▌ Spec Kitty · spec-kittyStandalone Spec Kitty governance invocation: run Spec Kitty when the user indicates they want Spec Kitty involved, load governance context, open an Op, do the work under that context, and close the Op with the real outcome. Documents dispatch, profiles list, invocations list, and profile-invocation complete. Triggers: "use spec kitty to", "hey spec kitty", "spec kitty <anything>", ad-hoc requests that are not part of a running full mission workflow.
- ▌ Spk Team Auth · spec-kittyHandle Spec Kitty team authentication, hosted credentials, account selection, and auth-related recovery.
- ▌ Spk Team Sync · spec-kittyOperate Spec Kitty team sync, hosted SaaS sync, offline queue, diagnostics, and recovery flows.
- ▌ Spk Start Here · spec-kittyStart here for Spec Kitty. Orient CLI users and supported agent-harness users; choose the right command, skill family, and recovery path.
- ▌
- ▌
- ▌
- ▌ Spk Mission Plan · spec-kittyOperate the Spec Kitty plan phase: convert a completed spec into architecture, data flow, risks, and implementation strategy.
- ▌ Spk Team Tracker · spec-kittyOperate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery.
- ▌ Adversarial Squad · spec-kittyDeploy a bounded, profile-loaded adversarial review squad at an SDD point-cut (post-spec, post-plan, post-tasks, pre-merge, or an ad-hoc decision) so independent doctrine lenses converge on findings one reviewer would miss. Triggers: "deploy a squad", "adversarial squad", "post-tasks anti-laziness pass", "pre-spec investigation squad", "brownfield check", "second opinion on this design", "review squad", "run a multi-lens review". Does NOT handle: the implement-review loop (use spec-kitty-implement-review), spec/plan/tasks generation, or direct code editing by the orchestrator. It is an optional, charter/memory-activated enrichment — it never gates a mission.
- ▌
- ▌
- ▌
- ▌ Spk Run Review Wp · spec-kittyReview a Spec Kitty work package through the runtime review surface and approve or reject with structured feedback.
- ▌
- ▌
- ▌
- ▌ Spk Meta Skill Map · spec-kitty bundleDiscover the Spec Kitty 3.2.0 spk skill hierarchy, naming convention, legacy aliases, and the correct skill for a user intent.
- ▌
- ▌ Spk Admin Dashboard · spec-kitty bundleOpen or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.
- ▌ Spk Mission Specify · spec-kittyOperate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.
- ▌
- ▌
- ▌ Spec Kitty Runtime Next · spec-kitty bundleDrive the canonical spec-kitty next --mission <handle> control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the next task", "continue the workflow", "what step comes next". Does NOT handle: setup or repair requests, purely editorial glossary or doctrine maintenance, or direct code review.
- ▌
- ▌ Spk Run Implement Review · spec-kittyOrchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
- ▌ Spec Kitty Mission Review · spec-kitty bundleReview a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review", "is this mission releasable", "final review before tagging", "cross-WP coverage audit". Does NOT handle: per-WP review during implementation (use spec-kitty-runtime-review), implement-review loop orchestration (use spec-kitty-implement-review), setup or repair (use spec-kitty-setup-doctor), or glossary maintenance (use spec-kitty-glossary-context).
- ▌ Spec Kitty Mission System · spec-kitty bundleUnderstand 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).
- ▌ Spec Kitty Runtime Review · spec-kitty bundleReview runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only repair requests, direct implementation work, editorial glossary maintenance, or runtime loop advancement.
- ▌ Spec Kitty Tasks Finalize · spec-kittyValidate dependencies, finalize WP metadata, and commit all task artifacts.
- ▌
- ▌ Spec Kitty Charter Doctrine · spec-kitty bundleRun 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 Kitty Implement Review · spec-kitty bundleOrchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop", "orchestrate WP implementation", "dispatch agents for WPs", "coordinate implement and review", "sprint through WPs". Does NOT handle: specify/plan/tasks phases, setup or repair, glossary maintenance, or direct code editing by the orchestrator.
- ▌ Spec Kitty Bulk Edit Classification · spec-kittyRecognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request that touches the same identifier/path/key in many files. Also triggers on gate errors mentioning "change_mode", "occurrence_map.yaml", "Bulk Edit Gate: BLOCKED", or "Bulk Edit Review: Diff Compliance". Does NOT handle: line-level semantic refactors inside one file, adding a new feature that creates new identifiers without changing existing ones, or reviewing finished missions for fidelity.