Loading...
Loading...
Found 653 Skills
Research, discuss, and write specs. Use this when creating or refining specs.
Use this when you need to initialize a new Spec Pack in the AI SDLC workflow of this repository (create a three-digit numbered branch and the `.aisdlc/specs/{num}-{short-name}` directory), or when you are unsure about input parsing, short name rules, UTF-8 BOM file path parameter passing, script invocation methods, or output artifacts when executing `spec-init`.
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
Manage project tasks with docs/task/index.md and docs/task/PREFIX-NNN.md, including claim-before-work multi-agent coordination and immediate status sync. Use when users ask to create tasks, track progress, update task status, or coordinate implementation work. Supports English and Chinese content.
Эксперт по интеграционным спецификациям. Используй для документирования интеграций, webhooks, event schemas и data flows.
Эксперт по OpenAPI документации. Используй для создания Swagger спецификаций, API schemas и автогенерации документации.
Améliorer un Prompt avec le Contexte du Projet, Techniques Avancées et Skills Spécialisés
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
Loads the full ***plain language reference into context: syntax, section types (definitions, implementation reqs, test reqs, functional specs, acceptance tests), concept notation, frontmatter (import/requires/required_concepts/exported_concepts), templates, linked resources, module model, and authoring best practices. Use whenever authoring, editing, reviewing, or debugging .plain files, or before invoking any other skill that reads or writes .plain content.
Break down a functional spec that is too complex into smaller specs that each imply ≤ 200 lines of code. Use when analyze-if-func-spec-too-complex flags a spec as TOO COMPLEX, or when a spec is suspected of being too large.
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
Transform raw brain dumps (dictated freestyle) into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts and implementation specs written to ./docs/ideation/{project-name}/.