Create an isolated workspace (worktree) for implementing a specific work package.
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI.
Execute the implementation planning workflow using the plan template to generate design artifacts. — from richfrem/Project_Sanctuary
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection.
Create or update the feature specification from a natural language feature description. — from richfrem/Project_Sanctuary
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.
Generate grouped work packages with actionable subtasks and matching prompt files for the feature in one pass.
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:…
Lists all spec GitHub Issues with their status and task counts. Use when the user wants to discover existing specs or get a project overview.
Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present that task for…
Используй при обновлении спецификаций модулей после реализации фич или изменений в дизайне — помогает прочитать текущую спецификацию, выявить изменения и обновить до актуального…
Install, configure, and verify the required harness runtime for spec-first workflows on Claude Code or Codex.
Normalize only human-confirmed reimplementation specifications into a provenance-rich, conflict-explicit intermediate for project planning.
Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations.
Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations.
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
Analyze and safely optimize OpenSpec main specifications. Use when asked to find semantically duplicate Requirements or Scenarios, cluster related capabilities, enforce spec…
Doorstop + Gherkin 仕様管理のドキュメントレビューと再編スキル。 増えたドキュメントが整合性をもって記述・配置されているかをチェックし、 必要があれば再整理（分割・集約・階層変更）を提案・実行する。 ユーザーが「仕様を見直したい」「ドキュメントが増えてきた」「構造を整理したい」…
在使用者要把模糊想法整理成可開發 spec 時使用。常見觸發像「整理需求成 spec」「補驗收條件」「拆分階段開發計畫」。輸出技術規格、白話規格與可直接貼用於 Codex / Claude Code 的分階段 instructions；不直接代替正式文件發布。
Turn a requirement or idea into an EPIC with vertical-slice TASKs. Use
Parse brief.md into brief.analysis.md with facts, assumptions, ambiguities, conflicts, questions, and source_sha256.
Use when a phase needs falsifiable requirements or ambiguity reduction before planning or building
Use when implementing a written spec into a reliable service with acceptance examples and observability. Triggers:
Look up, trace, and create spec requirements, and bootstrap a new SPEC.md.
Resolve a context bundle of relevant specs for a feature
Review an existing spec driving change before implementation or completion. Use when the user asks to review, verify, check readiness, confirm done, accept a change, or…
Review a canonical or change spec for inconsistencies, divergence, and implementation status, using semi-formal certificate templates.
Automatically activates when user has fuzzy ideas or incomplete requirements that need to be shaped into clear specifications.
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
当用户开始新的开发任务、需要启动完整 Spec 流程（需求对齐→探索→设计→实现→测试→收尾），或需要为一个新 Spec 创建协作上下文和 GitHub Flow 工作分支时使用。不要用于已有完成 Spec 的小迭代（用 spec-update）、项目首次初始化（用 spec-init）、运行期故障诊断与 bug 修复（用…
Report spec progress. Use when checking overall project state, viewing
The 4-file spec structure (1-description, 2-analysis, 3-solution, 4-status): what belongs in each file, the required sections, and the Tracking info fields.
あるドキュメント（実装計画・ADR・decision 等）で追加・詳細化された内容のうち、本来は別ドキュメント（spec / ADR / decision）に記載すべきものを反映し、変更履歴と相互参照を整える。ユーザーが「実装計画の内容を spec に反映」「ADR の決定を関連 spec…
Convert markdown specs to executable JSON format for autonomous task completion. Use AFTER spec-planner produces a complete spec to generate spec.json with verification steps.
Manage protocol/standard specifications that define what a system must do. Use to create, import, or update the contract that TASKs implement against.
仕様書作成を支援するテンプレートスキル。 docs/specs/ への仕様書作成時に自動適用され、 01_REQUIREMENT_MANAGEMENT.md に準拠した構造を提案する。 要件定義、機能仕様、API仕様の作成時に活用される。
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets.
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implement — from…
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…
Generate or update UI implementation from a screen spec in docs/product/screens/.
Decompose a confirmed specification, implementation plan, or settled conversation into independently executable and verifiable vertical work items with dependencies, safe…
Validate a `.specs/.md` against the schema, the body section rules, and the Constraints block. Writes the checksum and flips status from draft to approved when valid.
Validates implementation code against specification documents using YAML-based checklists and 4-dimension scoring.
Verify a spec against its implementation and repair violations
Compares specification documents against implementation code to find divergences. Use when implementation of a spec or design doc is claimed complete.
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…
Use when the user wants to run the full Specify → Plan → Implement → Deploy loop end-to-end in one shot. Accepts a free-form prompt that is passed to specify.
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 Agent needs to author or revise SpecDD `.sdd` specs in an existing SpecDD project.
Use when Agent needs to use the `specdd` CLI for setup, updates, spec discovery, inspection, or linting.
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…