13.2K skills · sorted by relevance
Debug json-render interfaces with an inspector panel that shows screen specifications, editable runtime state, action history, and streamed updates. Select a rendered page element to locate its definition and investigate display or interaction problems.
Create UI-SPEC.md, a document defining interface design decisions for a frontend phase. The skill coordinates UI research and specification checks, using a chosen phase or automatically selecting the next unplanned one.
Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.
Set up a new OpenSpec change for a feature, fix, or modification. Create its working directory, show the document sequence and current status, and present the first template so drafting can begin.
Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "dev-screen-spec", "画面仕様を生成", "画面仕様を更新", "screen spec", "generate screen spec", "update screen spec", "画面仕様ドキュメント". ソースコードから画面仕様ドキュメントを自動生成・差分更新する。受け入れ条件から画面仕様を事前生成する from-plan モードも対応。
The English summary is being prepared. Showing the original description.
Intent-driven spec precipitation — state a constraint in natural language (加一条规范：禁止用 any / 记录架构约束：服务间走 gRPC / 质量规则：覆盖率≥80%) and the workflow infers the category and records a <spec-entry>. Spec = 项目约束规则（编码规范、架构约束、质量标准）；可复用知识文档走 /maestro-knowhow capture。Triggers on "maestro-spec add", "记录规范", "添加约束", "添加规则", "加一条规范", "spec add". Terminology：spec = project constraints/rules (<spec-entry>). Reusable knowledge documents use /maestro-knowhow capture. Learning discoveries from /maestro-learn use <learning-entry> tags in learnings.md (separate from spec entries).
The English summary is being prepared. Showing the original description.
Lightweight standalone design spec for AI coding agents: codebase scan → bounded clarify pass (3–5 questions, not a grill) → reviewed design doc written to docs/plans/ → independent scored review → stop. No task board, no build. Use when you want a spec to discuss, hand off, or review before committing to implementation. Chains into absolute-work when ready to build. Triggers on "absolute spec", "write a spec", "spec out this feature", "draft a design doc", "I want a spec to hand off / review, don't build it yet".
The English summary is being prepared. Showing the original description.
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user mentions "ralph loop", "ralph", "spec loop", "iterative spec runner", "run my spec tasks automatically", "kiro spec automation", "self-correcting agent loop", "implement spec tasks in a loop", "run kiro-cli in a loop", "automated task implementation", or wants to drive a Kiro spec to completion through repeated agent iterations. Also use when the user wants to set up, configure, troubleshoot, or understand the Ralph Loop workflow — including progress tracking, corrections, codebase patterns, timing logs, and the summary dashboard.
The English summary is being prepared. Showing the original description.
Use when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
The English summary is being prepared. Showing the original description.
Spec-driven development workflow. Interactive phase-by-phase confirmation from proposal to implementation. Trigger: 'spec-flow', 'spec mode', 'need a plan', 'structured development', 'write a spec', 'feature spec', 'technical spec', '需求文档', '技术方案', '任务拆解', '规格驱动', '写个方案', '做个规划', '结构化开发', 'plan this feature', 'break this down', 'design doc'. Creates .spec-flow/ directory with proposal, requirements, design, and tasks.
The English summary is being prepared. Showing the original description.
Inspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.
The English summary is being prepared. Showing the original description.
Detect and install the Spec Kit `specify` CLI that every other speckit skill depends on. USE FOR: checking whether `specify` is installed/on PATH, installing it when missing, fixing "command not found: specify", confirming the CLI is new enough (>= 0.11). DO NOT USE FOR: upgrading an already-installed CLI to a newer release (use speckit-self) or verifying project tools (use speckit-check).
The English summary is being prepared. Showing the original description.
要件定義と実装の間を埋める技術仕様書を体系的に作成するスキル。 画面設計、API設計、DB設計、シーケンス図、状態遷移図をMermaid形式で生成し、 IEEE 830/ISO 29148準拠の仕様書を出力する。Use when creating functional specifications, API design documents, database design documents, screen design specifications, or sequence/state diagrams from requirements. Triggers: "technical specification", "functional spec", "API design", "database design", "screen design", "画面設計書", "API設計書", "DB設計書", "技術仕様書", "シーケンス図", "状態遷移図"
The English summary is being prepared. Showing the original description.
Process GitHub issues submitted for Spec Kit community extensions. Validate release details and required files, add or update the catalog and documentation table, and prepare a pull request with a validation summary.
Turn an unclear feature idea into a structured specification with goals, boundaries, and testable success criteria. Split broader requests into independent modules when needed, then move through planning, task breakdown, and implementation with human review.
Create and maintain OpenAPI 3.1 specifications from existing code or initial designs. Use these API descriptions to prepare documentation, generate client SDKs—libraries for calling an API—and check whether implementations match their specifications.
Create, design, and validate agents for Microsoft 365 Copilot. The skill guides JSON configuration or TypeSpec definitions, a typed alternative, alongside local testing, enterprise requirements, and deployment planning with Microsoft 365 Agents Toolkit.
Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.
Continue an existing OpenSpec change by creating one next document. Check progress and dependencies, follow the workflow's template, and report what was completed and which documents are now available to create.
Review skill and agent definitions for structural issues and whether their instructions meet expected behavior. Four modes cover structure, test specifications, category criteria, and coverage reports that reveal missing specifications or checks.
Turn game design documents and character profiles into asset specifications and image generation prompts. Define appearance, dimensions, file formats, and naming rules, then maintain an asset list that tracks progress and identifies shared assets.
Add and configure an inspection panel for Vue json-render apps. This skill guides setup and troubleshooting so you can inspect UI definitions, edit state, review action and stream timelines, browse catalogs, and select page elements.