Fission-AI/OpenSpec
Spec-driven development (SDD) for AI coding assistants.
What it solves
OpenSpec addresses the unpredictability of AI coding assistants when requirements are stored only in chat history. It provides a lightweight specification layer that ensures humans and AI align on exactly what to build before any code is written, reducing vague prompts and unpredictable results.
How it works
OpenSpec integrates with over 30 AI assistants via slash commands (e.g., /opsx:propose) to create an artifact-guided workflow. It organizes development into a structured openspec/ directory containing plain Markdown files for proposals, requirements (specs), technical designs, and implementation checklists.
Key workflows include:
- Explore: Using
/opsx:exploreas a thinking partner to weigh options and shape a plan. - Propose: Using
/opsx:proposeto generate a dedicated folder for a feature containing the proposal, specs, design, and tasks. - Apply: Implementing the defined tasks.
- Archive: Moving completed changes to an archive to keep the active workspace clean.
- Stores: A beta feature allowing teams to maintain specifications in a separate repository, creating a single source of truth shared across multiple code repositories.
Who it’s for
It is designed for solo developers and engineering teams who use AI coding assistants (such as Cursor, GitHub Copilot, Amazon Q, or Codex) and want a more predictable, organized, and scalable way to manage feature requirements and implementation.
Highlights
- Tool Agnostic: Works with 30+ AI assistants through tailored slash commands.
- Artifact-Guided: Uses plain Markdown for requirements and scenarios, making specs easy to read and review.
- Cross-Repo Planning: Supports "Stores" to manage specifications for features that span multiple repositories.
- Fluid Workflow: Avoids rigid phase gates, allowing iterative updates to any artifact at any time.
Related
- Project
- Project
- Project
- Dispatch
- Project