Set up a new OpenSpec change for a feature, fix, or modification. Create its working directory, show the document sequence and current status, and present the first template so drafting can begin.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Review the instructions the agent will receive before you install.
Start a new change using the experimental artifact-driven approach.
Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.
Steps
If no clear input provided, ask what they want to build
Use the AskUserQuestion tool (open-ended, no preset options) to ask:
"What change do you want to work on? Describe what you want to build or fix."
From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).
IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema
Use the default schema (omit --schema) unless the user explicitly requests a different workflow.
Use a different schema only if the user mentions:
--schema <name>openspec schemas --json and let them chooseOtherwise: Omit --schema to use the default.
Create the change directory
openspec new change "<name>"
Add --schema <name> only if the user requested a specific workflow.
This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
openspec status --change "<name>"
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact
The first artifact depends on the schema (e.g., proposal for spec-driven).
Check the status output to find the first artifact with status "ready".
openspec instructions <first-artifact-id> --change "<name>"
This outputs the template and context for creating the first artifact.
STOP and wait for user direction
Output
After completing the steps, summarize:
Guardrails
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement pending tasks from an OpenSpec change, a planned set of development work. The skill reads relevant specifications and design files, makes focused code changes, and updates task completion as work progresses.
Archive an OpenSpec change after checking its documents, task completion, and specification differences. The skill offers a choice about updating the main specifications, then moves the change into a dated archive and reports the result.
Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.
Continue an existing OpenSpec change by creating one next document. Check progress and dependencies, follow the workflow's template, and report what was completed and which documents are now available to create.
Explore development ideas and problems through conversation, code investigation, diagrams, and comparisons. The skill helps clarify requirements, weigh approaches, and surface risks before or during a change, with optional documentation of decisions when requested.
Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.