Loading...
Loading...
Found 62 Skills
Create structured change proposals and specification differences using an OpenSpec specification-driven approach. It is used for feature planning, proposal creation, specification writing, introducing new capabilities, or initiating development processes. Trigger words include "openspec proposal", "planning", "create proposal", "plan change", "specify feature", "new feature", "new characteristic", "new requirement", "add feature planning", "design specification"
Apply OpenSpec OPSX in a strict one-task-at-a-time loop. Use when the user asks to execute work as single-task changes, wants spec-first implementation per task, or says to use OpenSpec method for each task from a task list. Supports both native /opsx command environments and manual fallback by creating OpenSpec artifact files directly.
Creates structured change proposals with specification deltas for new features, breaking changes, or architecture updates. Use when planning features, creating proposals, speccing changes, introducing new capabilities, or starting development workflows. Triggers include "openspec proposal", "create proposal", "plan change", "spec feature", "new capability", "add feature planning", "design spec".
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Implements approved specification proposals by working through tasks sequentially with testing and validation. Use when implementing changes, applying proposals, executing spec tasks, or building from approved plans. Triggers include "openspec implement", "implement", "apply change", "execute spec", "work through tasks", "build feature", "start implementation".
Execute and implement approved specification proposals in sequence with testing and verification as the priority. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "openspec development", "development", "implementation", "implement proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation"
Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
This is intended for use when OpenSpec workflows require dependency-aware parallel subagents that are compatible with OPSX commands, legacy OpenSpec commands, and Codex CLI prompt aliases.
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.