Use when an existing Spec Kit `spec.md` has high-impact ambiguity (for example `[NEEDS CLARIFICATION]`, unresolved scope decisions, or unquantified requirements) that must be…
Use when creating or amending a Spec Kit project constitution, especially when `memory/constitution.md` is missing, contains `[PLACEHOLDER]` tokens, or principle changes must be…
Capture workflow usage data for spec-kit optimization. Auto-activates when: (1) completing a spec-kit workflow (/speckit.review, final commit), (2) encountering friction or…
Use when approved Spec Kit `tasks.md` must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
Use when specification drift is discovered at any stage and existing Spec Kit artifacts (`spec.md`, `plan.md`, `tasks.md`) must be reconciled in-place without creating a new…
Use when a Spec Kit feature needs `spec.md` authored or rewritten from natural-language requirements, especially when the feature has no usable specification or requirements are…
Use when an approved Spec Kit `plan.md` + `spec.md` must be decomposed into dependency-ordered `tasks.md`, or when `tasks.md` is missing/stale after planning or reconciliation…
Curate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift",…
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI.
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection.
Full-cycle install or update of the Spec-Kitty framework - upgrades the CLI, refreshes templates, syncs the plugin, reconciles custom knowledge, and bridges to agent environments.
Standard operating procedures for the Spec Kitty agentic workflow (Plan -> Implement -> Review -> Merge).
承認済み Spec ファイルを起点に、Isolate → Plan → Implement → Verify → Code Review → ship の 6 ステージ遷移を制御する skill。本ワークフロー (docs/workflow.md) の Spec Review 以降を担当します。 spec-review skill が verdict:…
Используй при обновлении спецификаций модулей после реализации фич или изменений в дизайне — помогает прочитать текущую спецификацию, выявить изменения и обновить до актуального…
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag…
Create a single TASK or REQ file from a template. Use for one-off artifact
Turn a requirement or idea into an EPIC with vertical-slice TASKs. Use
Use when a phase needs falsifiable requirements or ambiguity reduction before planning or building
Resolve a context bundle of relevant specs for a feature
Mark a spec shipped and move it to `docs/specs/archived/`. Stamps the frontmatter with `status: shipped`, `shipped: `, and optional PR URL.
Subdivide a mature spec into a parent + child sub-domain specs
Report spec progress. Use when checking overall project state, viewing
仕様書作成を支援するテンプレートスキル。 docs/specs/ への仕様書作成時に自動適用され、 01_REQUIREMENT_MANAGEMENT.md に準拠した構造を提案する。 要件定義、機能仕様、API仕様の作成時に活用される。
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or…
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, accepta — from…
Verify a spec against its implementation and repair violations
Implement the next ready task. Use when starting a development session
仕様駆動開発（SDD）ワークフローを自動発動で強制。Subtask開始時にAC確認、TDD実行、完了時にACチェックを実施。スコープ外実装を禁止。Use when implementing features, creating new functionality, or when "実装して", "作成して", "開発して" keywords appear.
Orchestrate comprehensive planning phase from ideation to development-ready specifications using 4 specialized agents
Register a spec file in the manifest and validate it
Clarifies and refines EARS specifications through interactive dialogue. Use when reviewing specs, adding missing conditions, validating requirements, or improving specification…
Work with Spec Canvas specifications using the original Spec Canvas format files plus local schema validation.
Use when Claude Code needs to create, add, restructure, or improve SpecDD `.sdd` contract files, define ownership or write authority, clean up missing or unclear specs, or…
Use when Claude Code needs to diagnose or fix a bug in a SpecDD project by reproducing or inspecting failure, comparing observed behavior to active `.sdd` contracts, and applying…
Use when Claude Code needs to implement a requested code, docs, tests, task, or spec change in a SpecDD project by following Resolve, Read, Authorize, Change, Verify, and Report…
Use when Claude Code needs to write or update user, developer, release, onboarding, or operational documentation from SpecDD specs while preserving source contract boundaries and…
Use when Claude Code needs to explain a SpecDD `.sdd` file, feature contract, or effective spec chain in succinct human language, covering purpose, scope, behavior, boundaries,…
Use when Claude Code needs to get oriented in a SpecDD project by reading `.specdd/bootstrap.md`, project/local bootstraps, root specs, explicitly applicable or requested spec…
Use when Claude Code is explicitly asked for a plan, or must resolve unclear SpecDD scope, write authority, public-contract risk, affected files, or verification before safe…
Use when Claude Code needs to review a diff, branch, pull request, changed files, or proposed changes against active SpecDD contracts, focusing on spec violations, behavioral…
Use when Claude Code needs to find, add, interpret, organize, or update `Tasks` entries in SpecDD `.sdd` files, including task status changes after implementation and verification…
Use when Claude Code needs to derive, add, update, or assess focused tests from active SpecDD `Must`, `Scenario`, `Handles`, `Returns`, `Raises`, `Tasks`, or `Done when` contracts.
Use when Claude Code needs to map SpecDD specs to code, tests, docs, changed files, public behavior, references, verification coverage, or gaps while preserving the distinction…
Generates SpecFlow BDD tests for C#/.NET with Gherkin feature files and step bindings. Use when user mentions "SpecFlow", "C# BDD", ".NET Gherkin", "[Binding]",…
Identifies and classifies GDPR Art. 9 special category data including racial origin, political opinions, religious beliefs, trade union membership, genetic, biometric, health, and…
Cook a slice with the customer's specifications on the spot — add new features mid-flight to an existing project.
Validate specialization completeness across all 7 phases, score each phase, identify gaps, and generate validation reports.
Comprehensive legal document review specialist for contracts, litigation documents, and real estate agreements — summarizing documents, flagging risk clauses, comparing contract…
Migrate from OpenClaw, Hermes, Manus, and other assistant species into Vellum by inspecting their exports, files, prompts, memory, tools, workflows, integrations, and…
Specific integration. Manage data, records, and automate workflows. Use when the user wants to interact with Specific data.
Drafts a Complaint for Specific Performance compelling contractual fulfillment through equitable relief.
Specification-mode prompt scaffold. Use when the decision is made and you need a buildable, testable, reviewable spec.
Specify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Specify data.
Read requirements markdown and generate detailed technical specifications. Analyzes requirements, clarifies ambiguities, and updates the specs document.
Writes, reviews, and refines Specification by Example (SBE) artifacts — Gherkin scenarios, example mappings, rule-example tables, and scenario outlines.
Generate a custom checklist for the current feature based on user requirements.
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress.
Test coverage quality analysis — behavioral coverage, critical gap identification,
Mandatory completion gate. Bridges an installed obra/superpowers verification-before-completion
Spec Kit SDD 操作指引精靈。當使用者意圖使用 Spec Kit、提及 SDD 開發並選擇 Spec Kit、 或要求以規格驅動開發方式定義功能規格時觸發。 以選單方式呈現所有步驟，引導使用者完成從初始化到實作的完整流程， 並將每步操作記錄保存為 log 檔案。 — from github/spec-kit.git