Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Implement tasks from an OpenSpec change.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_zjqdtovksu2henow
GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/openspec-apply-change
GET https://markdownregistry.com/api/v1/blob/d5e68d5e22653df7fc6f9b699ac30329a72cd8f277f126052a69bd41c7037ff5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
uze-sh/uze · .agents/skills/conformance-debug/SKILL.md · Fast, targeted debugging of the Harness Conformance Lab (conformance/) — use whenever a conformance check fails…
uze-sh/uze · .agents/skills/design-system/SKILL.md · The design system for everything UZE draws or prints - the workspace TUI (src/ui/), the CLI's output and help…
uze-sh/uze · .agents/skills/harness-watch/SKILL.md · Surveying what the supported harnesses (Claude Code, Codex, OpenCode, Antigravity CLI) shipped since UZE last looked…
uze-sh/uze · .agents/skills/journey-author/SKILL.md · Writing, changing or debugging a product journey (journeys/) — use whenever you are adding a scenario for a user-facing…
uze-sh/uze · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…
uze-sh/uze · .agents/skills/openspec-explore/SKILL.md · Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying…
uze-sh/uze · .agents/skills/openspec-propose/SKILL.md · Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe…
uze-sh/uze · .agents/skills/openspec-sync-specs/SKILL.md · Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from…
uze-sh/uze · .agents/skills/openspec-update-change/SKILL.md · Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use…
monid-ai/monid · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
mememeow-studio/mememeow · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
mememeow-studio/mememeow · .agents/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
mememeow-studio/mememeow · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
partcad/partcad · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
partcad/partcad · .cursor/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
asymmetric-al/core · .agents/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
