Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows.
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
OpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation.
# Install globally npm install -g @fission-ai/openspec@latestInitialize in a project
cd /path/to/project openspec init --tools claude
Update after CLI upgrade
openspec update
Each change follows: new → plan → apply → verify → archive
# Create change folder with default schema openspec new change <name>With specific schema
openspec new change <name> --schema tdd-driven
Use the CLI
instructions# Get instructions for next artifact openspec instructions --change <name> --jsonCheck progress
openspec status --change <name> --json
Artifact sequence (spec-driven schema):
proposal.mdspecs/design.mdtasks.mdRead
tasks.md[x]openspec validate --change <name> --json
Checks completeness, correctness, and coherence.
openspec archive <name> --yes
Merges delta specs into main
openspec/specs/When the user asks to build/migrate/refactor something with OpenSpec:
Check project state:
openspec list --json # Active changes openspec list --specs --json # Current specs openspec schemas --json # Available schemas
Create the change:
openspec new change <name> [--schema <schema>]
For each artifact, get instructions and create the file:
openspec instructions <artifact> --change <name> --json openspec status --change <name> --json
Then write the artifact file to
openspec/changes/<name>/Implement tasks from
tasks.mdValidate and archive:
openspec validate <name> --json openspec archive <name> --yes
| Command | Purpose |
|---|---|
| List changes or specs |
| Show change/spec details |
| Artifact completion status |
| Get enriched creation instructions |
| Validate changes/specs |
| Archive completed change |
| List available schemas |
| Show template paths |
| View/modify settings |
Always use
--jsonSchemas define artifact sequences. Create custom ones for different workflows:
# Fork built-in schema openspec schema fork spec-driven my-workflowCreate from scratch
openspec schema init my-workflow
Validate
openspec schema validate my-workflow
Schema files live in
openspec/schemas/<name>/schema.yamltemplates/For schema structure details, see references/schemas.md.
project/ ├── openspec/ │ ├── config.yaml # Project config (default schema, context, rules) │ ├── specs/ # Source of truth — current system behavior │ ├── changes/ # Active changes (one folder each) │ │ └── <change-name>/ │ │ ├── .openspec.yaml │ │ ├── proposal.md │ │ ├── specs/ # Delta specs (what's changing) │ │ ├── design.md │ │ └── tasks.md │ └── schemas/ # Custom schemas └── .claude/skills/ # Auto-generated Claude integration
Specs use RFC 2119 keywords (SHALL/MUST/SHOULD/MAY) with Given/When/Then scenarios:
### Requirement: User Authentication The system SHALL issue a JWT token upon successful login.Scenario: Valid credentials
GIVEN a user with valid credentials
WHEN the user submits login form
THEN a JWT token is returned
Changes don't rewrite specs — they describe deltas (ADDED/MODIFIED/REMOVED) that merge into main specs on archive.
openspec/config.yamlschema: spec-driven # or tdd-driven, rapid, custom context: | Tech stack: TypeScript, React, Node.js Testing: Jest rules: proposal: - Include rollback plan specs: - Use Given/When/Then format
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions
1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.