Loading...
Loading...
Found 68 Skills
Implement the tasks in a spec-driven change. Works through incomplete tasks one by one, marking each complete as it goes.
Diagnose and resolve common issues during spec-driven development and implementation. Learn strategies for handling spec-reality divergence, dependency blocks, unclear requirements, and other execution challenges.
Comprehensive testing and validation strategies for spec-driven development. Learn phase-specific validation techniques, quality gates, and testing approaches to ensure high-quality implementation.
Structured spec-driven workflow for planning and executing software projects with GitHub Copilot CLI.
Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
OpenSpec Spec-Driven Development Assistant - An AI-aided programming framework based on the OPSX workflow. Align requirements with AI before writing code, and manage changes using a Schema-driven artifact dependency system. Trigger Conditions: 1. User mentions "openspec", "opsx", or spec-driven development 2. User wants to start new feature development or refactoring 3. User needs to explore complex problems or clarify requirements 4. User complains about AI misunderstanding or frequent rework 5. User uses slash commands such as /opsx:new, /opsx:ff, /opsx:apply, etc. 6. During project initialization or preparation for major changes
Use this when planning new features, starting spec-driven development workflows, or when the user mentions OpenSpec, SDD, or spec-driven development. It also applies when the user asks about feature specifications, change proposals, or wants to organize development workflows.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.
Guide spec-driven development using collaborative interrogation and iterative Q&A to build production-ready specifications. Use when the user wants to build specifications, plan features, gather requirements, create technical blueprints, or asks about spec-driven development, requirements gathering, feature planning, or specification writing.
Enforces spec-before-code workflow for AI-driven development. Automatically selects Spec-Kit or OpenSpec mode, triages complexity (quick/standard/thorough), recovers session context, and applies quality gates (G0-G4) with automated review loops at every stage. Use this skill whenever the user says "/super-spec", "spec first", "规范先行", or starts any feature, bugfix, or refactor — especially in projects with .spec-mode, .specify/, or openspec/ directories. Even if the user doesn't explicitly ask for spec-driven workflow, activate this skill for any non-trivial code change to prevent skipping the design phase. Orchestrates: Spec-Kit/OpenSpec (OPSX) + planning-with-files + ui-ux-pro-max (v2.0, 67 styles, 161 palettes, 13 stacks) + Superpowers (TDD, code review, verification, debugging, spec/plan review loops, subagent model selection).