Menu
Write or update specifications for a change using the openspec CLI. Trigger: When the orchestrator or user needs specs created or updated for a change.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Create a technical design document for a change using the openspec CLI. Trigger: When the orchestrator or user needs a design document created or updated for a change.
Initialize OPSX in a project. Runs `openspec init` to scaffold the openspec/ directory and config. Trigger: When user wants to initialize OPSX in a project, or says "opsx init", "iniciar opsx", "openspec init".
Guided end-to-end walkthrough of the OPSX workflow using the real codebase. Trigger: When the user wants to learn OPSX or do a guided first change.
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.
Create an implementation task checklist for a change using the openspec CLI. Trigger: When the orchestrator or user needs tasks created or updated for a change.
| name | openspec-spec |
| description | Write or update specifications for a change using the openspec CLI. Trigger: When the orchestrator or user needs specs created or updated for a change. |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"gentleman-programming","version":"2.0"} |
Write delta specs for a change. Specs define WHAT the system must do — they are your acceptance criteria for implementation.
Get instructions from the CLI
openspec instructions specs --change "<name>" --json
Parse outputPath, template, instruction, context, rules, and dependencies.
Read dependencies
Read any files listed in dependencies (typically the proposal).
Write the spec
Use template as the structure. Follow instruction for content guidance.
Apply context and rules as constraints — do NOT copy them into the file.
Specs should use:
Verify
openspec status --change "<name>" --json
Confirm the spec artifact shows status: "done".
# Spec: <capability-name>
## Overview
<Brief description of what this capability covers>
## Requirements
### REQ-001: <Requirement Name>
The system MUST <specific behavior>.
**Scenarios:**
**Scenario: <scenario name>**
- Given: <precondition>
- When: <action>
- Then: <expected outcome>
rules.specs from openspec/config.yaml