Spec-before-code workflow framework: slash commands that guide you and your AI through proposals, specs, and task checklists before any implementation begins.
Before you start
Claude Code or any supported AI coding tool (25+ supported). OpenSpec works via slash commands, no separate install required beyond adding the SKILL.md or command definition to your tool.
Before writing any code, use /opsx:propose to create a structured proposal artifact in your project. OpenSpec stores it in a proposals/ folder. This is the alignment step. You and your AI agree on what is being built before implementation starts. The proposal is fluid: update it as requirements clarify.
OpenSpec creates a structured folder with the artifacts for this change: the proposal, a spec, a design doc, and a task checklist. Read all of them before moving to implementation. The spec is the source of truth, if anything in the folder does not match your intent, update it now.
Once the spec reflects your intent, run /opsx:apply. This signals to your AI that the spec is approved and implementation should begin. The AI works from the task checklist in the artifact folder, checking off items as it completes them. You can interrupt and update the spec at any point.
OpenSpec is explicitly not rigid. If requirements change mid-implementation, update the spec and re-run /opsx:apply. The checklist adjusts. You do not need to restart. The artifact folder becomes the living record of what was built and why.
Core OpenSpec slash commands and artifact types.
| Command / Skill | What it does | When to use it |
|---|---|---|
/opsx:propose | Create a change proposal artifact, starts the spec-before-code alignment process | Before any implementation, this is always step 1 in the OpenSpec workflow |
/opsx:apply | Begin implementation from an approved spec, AI works from the task checklist | After reviewing and approving the spec artifact, never before |
proposals/ folder | Artifact directory containing proposal, spec, design doc, and task checklist per change | Review every file in this folder before running /opsx:apply |
spec.mdadvanced | The source-of-truth artifact describing what is being built, editable at any time | Update when requirements change, /opsx:apply picks up the latest version |
25+ AI tool integrationsadvanced | OpenSpec slash commands work across Claude Code, Cursor, Copilot, and 22+ other tools | Switching AI tools mid-project, the artifact folder stays valid across tools |