Trigger HAS_DOCS flag in template_recommendations.md (recon detects non-empty DOCS_PATH - whitepaper, spec, or design doc provided) - Agent Type general-purpose (standalone nich...
Merge multiple model-generated specs into one implementation-ready consensus spec.
Produces a suite of coordinated, self-contained implementation prompts and a master integration contract table from a set of interconnected specs.
Use when a team wants to create or update specs/constitution.md to define durable principles that govern spec-skills runs, especially when starting a new workflow, revising shared…
Create spec documents (spec.md, context.md, tasks.yaml, dependencies.yaml, validation.yaml). Receives validation data from spec-validate.
Create, expand, or change formal design specifications for an app, package, or codebase. Triggers on "create/write a spec", "document the design", "promote to a global spec", or…
Adversarially review a draft spec before the human gate; kill vague criteria and hidden scope.
Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.
Audit a codebase for specification debt — claims that live at the wrong altitude (a cross-module rule buried in a code comment) and claims stated more strongly than they are known…
[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications
Interview the user about a rough idea or brief with sharp, non-obvious product and technical questions, then write a concise implementation-ready spec.
Erstellt einen vollständigen, bijektiven Vergleichsreport zwischen zwei Versionen einer technischen Spezifikation (PDF, DOCX, Markdown, HTML, XML/XSD oder Textdateien).
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Verifies that SPECS.md, NOTES.md, TESTS.md, BENCHMARKS.md, and documentation cross-reference cleanly against each other and against the actual code
ユーザー体験側の設計（要件定義・シナリオ・ページ構成など）が完了済みの状態から、 ドメイン設計以降の技術設計を行うスキル。 上流の成果物はシナリオ、ページ設計、要件定義書、ユーザーストーリー、フロー図、 サイトマップなど形式を問わない。何らかの体験設計・要件が存在する前提で、 ドメイン設計 → ユースケース設計 → DB設計 → テストケース定義 →…
Mark a task complete with evidence. Use when finishing a task, discovering
Use when planning and implementing a new feature or service end-to-end using the Specify→Design→Tasks→Implement workflow
为 spec-driven-dev 提供流程中断保存与恢复能力。在任意阶段触发 checkpoint 保存当前 Git 快照、迭代状态、Session 元数据和上下文重建包；rollback 命令可将 Git 仓库和 Agent 上下文恢复到任意历史 checkpoint。支持 save_checkpoint-{us_id} 和 rollback…
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation…
specialized protocol for spec-driven project initiation using Karpathy's Method — interview for the real goal, decompose into small compartmentalized specs, verify key decisions…
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first…
FAPI（Financial-grade API）機能の開発・修正を行う際に使用。FAPI 1.0 Baseline/Advanced, FAPI CIBA, mTLS, PAR, JARM実装時に役立つ。 — from general/finance-personal
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request.
Requires a 5-line spec (inputs, outputs, edge cases, failure modes, acceptance) before writing tests or code. The spec becomes the prompt anchor for the whole task.
Specification-First Agentic Development methodology guide. Triggers when a project has a .yourproject/ directory structure (context.yaml, phases/, decisions.md) or when the user…
管理跨会话、可恢复、可验收、可归档的 spec 生命周期工作流，围绕 explore、plan、implement、accept、archive 五个 action 维护持久化 `.specs/` 状态。用于复杂功能开发、研究任务、运维或流程改造、文档与规范编写等需要长期跟踪、独立验收、变更留痕或后续归档的场景；不适用于一次性小改动、即时问答或无需持久化…
Use this agent when you have a specification, plan, feature description, or technical document that needs user flow analysis and gap identification.
SPEC format for structured requirements, acceptance criteria, and technical specifications. Use when writing requirements, defining acceptance criteria, or creating technical…
Elicit Scope/Decisions/Context for a plan slice and generate its OpenSpec-formatted feature spec. Use after a slice is approved but before promote-slice, or any time a slice needs…
Use when comparing spec, blueprint, or requirements documents against actual implementation. Detects MISSING features (documented but not implemented), PARTIAL features…
コードからspecを生成するスキル。As-Is spec（現状仕様）を根拠付きで抽出し、3層構造（インターフェース/振る舞い/業務意味）で整理。 使用タイミング:…
Generate structured spec files for Choo Choo Ralph. Use when running /choo-choo-ralph:spec or creating task breakdowns.
Ensure features are developed according to specifications by validating implementation against API docs, database schemas, and acceptance criteria.
Continue an approved Spec-backed workflow when the user says "implement", "go", "start", or "do it". After Codex Plan Mode, persist the next missing design.md or plan.json…
Implementability assessment — 13-criteria production-readiness gate. Use when the user says 'is this implementable', 'ready to code', 'spec completeness', 'can we implement this',…
[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under…
当项目首次接入 Spec 驱动开发 / R&K Flow，需要创建 AGENTS.md、.agents/rules/、 .agents/skills/、spec/ 目录、记忆系统和 Obsidian Vault 时使用。 典型信号：用户说"初始化项目"/"搭建 Spec 环境"/"创建开发环境"，或项目根目录缺少 AGENTS.md / spec/。…
Use BEFORE infra specs (CI/runner routing/deploy config). Confirm key behavioral decisions explicitly; flag infeasible numeric targets as STOP.
Conducts a deep, multi-round interview to clarify ambiguous requirements and produces a structured specification document.
Realiza entrevistas profundas para extraer especificaciones completas de proyectos
Brainstorm requirements, propose approaches, and write a spec to a GitHub issue or a local markdown file.
Use when work involves Spec Kit and you need to choose the correct `spec-kit-*` sub-skill, enforce artifact-order gates, or route remediation work (for example sequence violations…
Use when `spec.md`, `plan.md`, and `tasks.md` exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution…
Use when a Spec Kit feature has `spec.md` and you need a requirements-quality checklist (clarity, completeness, consistency, measurability, coverage), not implementation/runtime…
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…
Use when installing, upgrading, bootstrapping, or repairing spec-kit-extensions in a project. Triggers on requests like "install spec-kit-extensions", "set up speckit workflows",…
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…
按 spec-kit 对齐版本进行发布与重发的标准流程。用于需要发布本项目、重跑同版本发布、删除并重建同名 tag/release、校验 GitHub Actions 与 release 资产清单一致性的场景。
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement).
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…
Standalone 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…
Combined Spec-Kitty agent: Synchronization engine + Spec-Driven Development workflow. Auto-invoked for feature lifecycle (Specify → Plan → Tasks → Implement → Review → Merge) and…
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. — from richfrem/Project_Sanctuary
Curate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift",…