Browse 182,820 skills across 14 categories.
Review an implementation spec for contradictions, redundancy, and completeness. Use when asked to review or check a spec...
Validate a specification document's numbering and cross-references — duplicate or out-of-order headings and requirement...
Audit spec/plan documents against the codebase. Ensures every spec section has implementing code, tests, and matching lo...
This skill should be used when the user asks to 'check spec alignment', 'verify requirements coverage', 'detect drift',...
Check a task against the project's specs before implementing it, and again before declaring it done. Produces the requir...
Perform specification-to-code compliance analysis. Determine whether a codebase implements exactly what the documentatio...
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "check...
Ask targeted questions to clarify scope, edge cases, and acceptance before coding.
Resolve ambiguities and markers in validation.yaml interactively. Updates spec docs directly with full audit trail.
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived...
Verify smart contract implementations comply with EIP/ERC standards and protocol specifications. Use when checking ERC-2...
驗證規格檔案的完整性與一致性，確保所有必要的規格元素都已定義且符合標準格式。
When work would produce 2+ related specs, prefer initiative-first composition over `/design` × N siblings. Carries the c...
Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks abou...
The content contract for a design doc — what must be IN it, as against make-spec which owns how it LOOKS. Synthesised fr...
Iteratively review an instar-development spec with multi-angle internal reviewers (security, scalability, adversarial, i...
Generate a visual spec-to-code coverage map showing which code files are covered by which specifications. Creates ASCII...
Create a new numbered spec file from the template with auto-incremented SPEC-NNN numbering
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use...
Create spec documents (spec.md, context.md, tasks.yaml, dependencies.yaml, validation.yaml). Receives validation data fr...
Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decision...
Self-critique specification documents using extended thinking. Use when a spec is complete and needs validation before i...
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for cons...
Decompose large unified specifications into agent skills with progressive disclosure. Use when converting documentation,...
Analyze specifications and decompose into independent changes.
Turn an idea into a buildable specification by working it through with the person. Frames the problem, explores options,...
仕様（Why）と設計（How）を記録し、Living Documentation原則でコードと常に同期させる
Cross-consistency review of a drafted spec's diagrams. Verifies that C4 components appear in the dependency graph, class...
技术方案文档的方向确认关卡。在 specs/<id>/TECH.md 草稿完成、进入实施之前，先确认方向、再确认内容，两次确认分开且有序；把关卡结论写回 TECH.md 作为批准状态的显式记录。拒绝语义：没有人在场就停止并报告，绝不自动放行...
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Standard format for spec documents.
外部模型草稿的摄入关卡。把下载的外部技术方案草稿当作不可信输入，逐条与仓库实际状态对账，产出一份经审的 specs/<id>/TECH.md。草稿是候选不是权威：不因草稿存在而跳过研究，也不把草稿的断言直接升格为文档结论。用于"外部模型写了...
Standalone plan-vs-code audit on any branch: runs /ship Step 8's plan-completion section from disk (hash-pinned) against...
Audits a WP brief for drift against current code — extracts claims, verifies each, emits PROCEED/STOP verdict. Use when...
Use when writing specs before code.
Rule under the project-documentation law. Load when editing specs, laws and any skill. Names the three layers — law, rul...
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phas...
Write a structured spec before writing code. Use when starting a new project or feature, requirements are unclear, or th...
Assimilated Tech Lead's Club spec-driven workflow (tlc-spec-driven 3.3.0). Use for specify/design/tasks/execute feature...
Full lifecycle spec-driven development methodology across three gated phases - Requirements (EARS-format acceptance crit...
给任务建立统一的 spec-driven 工作目录，约束共享工作面和 align 纠偏机制，不内置阶段路由。
Create DevForgeAI-aware Claude Code subagents with structural anti-skip enforcement (Execute-Verify-Record pattern) acro...
Orchestrate session data mining operations through a 7-phase workflow with structural anti-skip enforcement. Analyzes Cl...
Expert in the Spec-Kit Plus lifecycle (Specify -> Plan -> Tasks -> Implement). Use this when the user needs to define ne...
Creates immutable context files and architecture documentation through spec-driven workflow with structural anti-skip en...
Spec-driven brainstorming and product discovery expert. Helps teams ideate features, break down epics, conduct story map...
Interactive question-driven discovery skill that transforms vague business problems into structured AI-consumable docume...
Methodology for transforming a technical specification into a verified implementation plan. Use when starting non-trivia...
Expert knowledge base for Claude Code Terminal — the CLI tool itself, not coding tasks. Implements 4 knowledge-retrieval...
Generate CI/CD pipeline workflows through spec-driven workflow generation with structural anti-skip enforcement. Impleme...
Generate self-contained collaboration documents for sharing issues with external AI systems (Gemini, ChatGPT, etc.) with...
Validate epic-to-story coverage with gap detection and batch story creation using structural anti-skip enforcement. Impl...
Implements user stories through spec-driven TDD workflow (Red-Green-Refactor) with structural anti-skip enforcement. Rep...
Spec-Driven Development (SDD) agent for maintaining synchronized specifications, code, and documentation.Core principle:...
Feature planning with 4 phases - Specify requirements, Design architecture, break into granular Tasks, Implement and Val...
Mandatory default entry point for any non-trivial build/add/fix/implement/refactor request — drives work through explici...
Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements a...
Use when user wants to write a spec, create a PRD, or plan a new feature before implementation begins, when .forge/idea-...
An "AI-Spec-Driven" workflow for complex tasks, triggered ONLY when explicitly requested. It aligns agent execution with...
Forces writing a specification before any code changes. Defines goals, inputs/outputs, constraints, edge cases, and acce...
Spec-driven development workflow that turns specifications into working implementations through structured planning.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists...
기능 구현을 위한 테크스펙과 구현 계획 문서를 작성합니다. 스펙 주도 개발 워크플로우를 지원합니다.
Use this when intake extracts FRs from a TPRD, when design maps FRs to symbols in the API stub, when impl verifies every...
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Formal specification authoring with exit criteria and acceptance conditions. Use when requirements need to be captured p...
Resolves ambiguities and gaps in the specification through structured questioning. Use after specification to ensure com...
Creates foundational governance principles and development guidelines for the project. Use when starting a new project o...
Generates code and assets by executing the task breakdown. Use when ready to build the feature.
Creates technical implementation strategy including architecture and technology choices. Use after specification is clar...
Defines functional requirements as user stories without technology choices. Use when starting to design a new feature.
Converts the implementation plan into actionable, ordered development tasks. Use after plan is validated.
Automated documentation generation, auditing, and remediation with structural anti-skip enforcement. Supports 3 workflow...
Pattern of rule spec-driven. Load when creating or editing a domain spec in docs/specs — the mandatory sections, the sce...
Scores how completely an implementation fulfills a PRD/spec, case by case, and produces a single comparable final grade....
Retrospective feedback system with Execute-Verify-Gate structural anti-skip enforcement for DevForgeAI operations. Captu...
Transform business ideas into structured requirements through guided discovery with structural anti-skip enforcement (Ex...
Use when ready to implement designed features - breaks design into TDD tasks (Red-Green-Refactor), tracks progress with...
Assimilated Tech Lead's Club lean spec workflow (tlc-spec-lean 1.0.0). Freeze obligations in plan + proof-backed checks,...
Coordinates spec-driven development lifecycle from Epic -> Sprint -> Story -> Architecture -> Development -> QA -> Relea...
Convert any MCP (Model Context Protocol) server into a standalone CLI utility and auto-generate companion skill document...
Use when planning new features or need structured requirements - creates feature structure, elicits EARS requirements th...
Validates code quality through spec-driven QA validation with structural anti-skip enforcement. Replicates all 6 phases...
Process QA gap files and create remediation user stories with structural anti-skip enforcement (Execute-Verify-Gate patt...
Unified root cause analysis with 4-layer anti-skip enforcement for both tactical (dev workflow diagnosis) and strategic...
Orchestrates production releases through spec-driven deployment workflow with structural anti-skip enforcement. Implemen...
Apply automated and guided fixes to story, epic, and context files based on structured audit findings with 4-layer anti-...
Capture, persist, and query research findings across sessions through a 7-phase workflow with structural anti-skip enfor...
Pattern of rule spec-driven. Load when creating or editing a law in docs/constitution, a rule or a pattern in .claude/sk...
Create user stories with acceptance criteria, technical specifications, and UI specifications through an 8-phase workflo...
Pattern of rule spec-driven. Load for a full sweep of a domain's binding — five passes, three of them done by the machin...
A workflow that drives development from requirements refined into observable behaviors (AC/EC) through requirement defin...
Spec-driven source translation & modernization workflow for codebases.Use when asked to migrate/translate a project (e.g...
Generate front-end UI specifications and code for Web, GUI, or Terminal interfaces through a constraint-aware 9-phase wo...
W3 compliance scanning with structural anti-skip enforcement. Detects auto-skill chaining violations (skills/commands th...
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, gene...
SPEC-First planning workflow - explore codebase, gather requirements, create execution plan through dialogue (read-only)