Loading...
Loading...
Found 97 Skills
Setup and configure Minikube for local Kubernetes development
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
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.
Structured spec-driven workflow for planning and executing software projects with GitHub Copilot CLI.
Spec-driven development orchestration with context engineering for solo developers. Prevents context rot through fresh subagent contexts and atomic task execution. Use when: starting projects, planning features, executing development phases, or when user says "gsd", "plan", "new project", "execute phase". Triggers: /gsd init, /gsd plan, /gsd execute, /gsd status, /gsd verify
Spec-driven E2E test creation: plan what to test through structured discovery phases, then scaffold a local Shiplight test project and write YAML tests by walking through the app in a browser.
The root skill of the easysdd workflow family — introduces the workflow system and routes users to the correct sub-skill. Trigger scenarios: Users mention "easysdd", "sdd", "spec-driven", "how to use this set of processes", "which skill should I use", "where to start", or describe a new feature but haven't decided on the entry stage. Known intents (brainstorm/design/implementation/acceptance/BUG/exploration, etc.) will trigger the corresponding sub-skill first instead of this skill.
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).
Refactoring workflow — test coverage gate, DRY + SOLID analysis, SRP decomposition, pattern discovery, spec-driven user review, and execution planning
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
Transform reverse-engineering documentation into GitHub Spec Kit format. Initializes .specify/ directory, creates constitution.md, generates specifications from reverse-engineered docs, and sets up for /speckit slash commands. This is Step 3 of 6 in the reverse engineering process.