Skip to content
Agentic Levels
Start hereLevelsTracksPromptsAbout
Get my levelGet my level

  • Start hereYour first useful task with AI.
  • Level quiz8 questions. No AI needed.
  • Fluency ScoreYour Level and a score, from your own AI.

  • LevelsThe 11 levels, in order.
  • LessonsShort lessons, filter by level.
  • TracksGuided paths by tool, role or goal.
  • Set up your AI tool
  • Starter packFree files that help AI remember.

  • PromptsReady prompts to copy and adapt.
  • ChatGPT vs Claude vs GeminiPick the right one for the job.
  • How-tos
  • ReferenceCommands for Claude Code, Codex, Antigravity.
  • ResourcesHand-picked reading and tools.

  • Your progress
  • Your next moveAn interview that picks your next skill.
  • Your next lessonsThe next lessons at your level.
  • Updates

  • Pricing
  • About
  • FAQ & Feedback
  • Work with us
  • How we handle your data
Sign inPreferences
AboutPricingHow-tosPromptsStarter packMy stackHow we handle your data

© 2026 Fuentes Studio

PrivacyTermsRefundsAccessibilityAI content policyCredits
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

←How-to guides
  1. Resources
  2. ›How-to guides

How to use OpenSpec

Spec-before-code workflow framework: slash commands that guide you and your AI through proposals, specs, and task checklists before any implementation begins.

Levels 3 to 5On GitHub

AI coding assistants jump straight to code when you ask them to. OpenSpec breaks that habit by establishing a spec-before-code discipline through structured artifact folders and slash commands. You and your AI go through proposal → spec → design doc → task checklist before any implementation starts. The workflow is fluid, not rigid. Any artifact can be updated as requirements change. OpenSpec supports 25+ AI tools via /opsx:propose and /opsx:apply, works at personal and enterprise scale, and is designed to be the alignment layer between human intent and AI execution.

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.

  1. 1Run /opsx:propose to create a change proposal
  2. 2Review the generated artifact folder
  3. 3Use /opsx:apply to begin implementation from the spec
  4. 4Update any artifact iteratively: the workflow is fluid

Steps

01

Run /opsx:propose to create a change proposal

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.

Create a proposal
/opsx:propose [CHANGE_DESCRIPTION]
[CHANGE_DESCRIPTION]What you want to build or change e.g. Add email/password authentication to the existing Next.js app
02

Review the generated artifact folder

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.

03

Use /opsx:apply to begin implementation from the spec

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.

Apply the spec to implementation
/opsx:apply [PROPOSAL_ID_OR_PATH]
[PROPOSAL_ID_OR_PATH]Proposal identifier or path to the artifact folder e.g. proposals/2026-05-add-auth
04

Update any artifact iteratively: the workflow is fluid

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.

Update the spec and re-apply
# Edit the spec in proposals/[PROPOSAL_ID]/spec.md # Then re-apply: /opsx:apply [PROPOSAL_ID]
[PROPOSAL_ID]Your proposal folder name e.g. 2026-05-add-auth

How do you know it worked?

  • /opsx:propose created a proposals/ folder with at least a proposal and spec artifact.
  • The spec matches your actual intent: you read it and confirmed it before running /opsx:apply.
  • Implementation started from the task checklist, not from a freeform instruction.
  • You updated the spec mid-implementation without restarting from scratch.

If something looks off

Skipping the proposal step
The whole value of OpenSpec is the alignment step before coding. If you run /opsx:apply without a reviewed spec, you are back to vibe coding with extra folder structure.
Treating artifact folders as read-only
The artifacts are yours to edit. If the generated spec does not match your intent, fix it. OpenSpec's 'fluid not rigid' design means you are expected to update artifacts as requirements evolve.
One proposal per change, not one per project
Create a new proposal for each meaningful change, not one giant proposal for the whole project. Small proposals complete faster, create cleaner audit trails, and are easier to update.

Skills & Commands Reference

Core OpenSpec slash commands and artifact types.

Command / SkillWhat it doesWhen to use it
/opsx:proposeCreate a change proposal artifact, starts the spec-before-code alignment processBefore any implementation, this is always step 1 in the OpenSpec workflow
/opsx:applyBegin implementation from an approved spec, AI works from the task checklistAfter reviewing and approving the spec artifact, never before
proposals/ folderArtifact directory containing proposal, spec, design doc, and task checklist per changeReview every file in this folder before running /opsx:apply
spec.mdadvancedThe source-of-truth artifact describing what is being built, editable at any timeUpdate when requirements change, /opsx:apply picks up the latest version
25+ AI tool integrationsadvancedOpenSpec slash commands work across Claude Code, Cursor, Copilot, and 22+ other toolsSwitching AI tools mid-project, the artifact folder stays valid across tools

What you'll do, 4 steps

  1. 1Run /opsx:propose to create a change proposal
  2. 2Review the generated artifact folder
  3. 3Use /opsx:apply to begin implementation from the spec
  4. 4Update any artifact iteratively: the workflow is fluid

Was this helpful?