Loading...
Loading...
Found 44 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.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
SOC II triage workflow for creating Linear tickets, branches, OpenSpec proposals, commits, and PRs. Use when asked to triage an issue, create a triage ticket, or start SOC II 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.
Use when implementing a planned OpenSpec change by applying tasks and validating all artifacts.
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
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
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.
OpenSpec artifact-driven workflow. Covers OPSX commands, schemas, project config. Keywords: OPSX, artifact graph, /opsx:.
Use when OpenSpec is not initialized in the current project or the superspec-rpi schema is missing.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.