LABSCO SUMMARY
OpenSpec is a spec framework: you and your AI assistant agree on a written plan for each change before any code is written. These twelve skills are its workflows, the same files its command-line tool writes into a project.
npx skills add Fission-AI/OpenSpec installs the skills on their own. The full setup is npm install -g @fission-ai/openspec@latest (Node.js 20.19.0 or newer), then openspec init in your project, which creates the openspec/ folder and installs the default six with their slash commands; add the other six with openspec config profile, then openspec update.
In a project without it, a skill stops before writing anything and asks how to proceed.
WHAT'S INSIDE
Showing all 12 skills
Builds a planned change from its task checklist: it works through the tasks one at a time, makes the code edits each one calls for and ticks it off. It stops to ask when a task is unclear, an error blocks it, or the work would go beyond what the plan says; when every task is done, the next step is openspec-archive-change.
Closes out a finished change: it warns about unchecked tasks or unfinished documents, offers to merge the change's spec updates into the main specs, then moves the change folder into a dated archive. Anything unfinished is put to you before it goes ahead, and it ends with a summary of where the change went.
Archives several finished changes in one go: you pick which ones, it shows a status table for all of them, and a single confirmation covers the batch. Where two changes edited the same spec, it checks the code to see which was actually built and merges those oldest first.
Writes the next document in a change's plan and stops, so you can review each one before the next is written. It re-reads the documents already there, picks the first that is ready, and reports what that unlocks; once the plan is complete it says so and points you to building it.
A thinking partner for before anything is decided: it reads your code, lays out options and tradeoffs, often as plain-text diagrams, and writes no code. When an idea firms up, it offers to save it as an OpenSpec change, and saves only what you ask for or agree to.
Fast-forwards a new change to ready-to-build: it writes every planning document implementation needs, back to back, without stopping for review between them. It reads the relevant code first so the plan fits what is there, asks only when something is critically unclear, and tells you about any optional document it skipped.
Opens a new, empty change and stops there: it creates the change folder, lists the documents the workflow needs in order, and shows the template for the first one. Nothing is drafted until you say what the change is about; openspec-continue-change then writes the documents one at a time.
A guided first run of OpenSpec on your own codebase: it suggests a few small real tasks, then takes the one you pick from idea to plan to working code to archive, explaining each step. It makes real changes to your project, pauses for your go-ahead along the way, and takes about 15 to 20 minutes.
Turns one description of what you want built into a complete written plan before any code: with OpenSpec's default workflow, a proposal, requirement specs, a design and a task checklist. It asks first when the request is unclear in a way that would change the scope, and it never starts building in the same run.
Copies what one change decided into the project's main specs, the standing description of how the software should behave, while the change itself stays open. It merges requirement by requirement, adding, editing, renaming or removing only what the change lists, then checks the result with OpenSpec's validator.
Revises a planned change after the fact, such as a new decision or a changed requirement, then checks that the plan's other documents still agree with it. It shows each revision and writes only the ones you approve, never touches code, and points you to openspec-apply-change if the code was already built from the old plan.
Checks a built change against its own plan before you archive it: are all tasks done, does the code cover each requirement and scenario, does it follow the design. Problems come back as critical, warning or suggestion, each with a fix and a file reference, and the skill itself changes nothing.
INSTALL
SINGLE SKILL
Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.
Install checklist
Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.Installing to: for your intended tool. Stop if it names a different tool.Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.npx skills add Fission-AI/OpenSpec --skill <YOUR_SKILL_NAME> --full-depthPick the skill name from the Skills tab. A single skill needs the same two things first: OpenSpec's command-line tool, and an openspec folder made by running openspec init in your project.