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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (10930 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
stek0v/levara · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lewx5mdjpt23smf6
GET https://markdownregistry.com/api/v1/resolve?ref=stek0v/levara/openspec-apply-change
GET https://markdownregistry.com/api/v1/blob/961dd6b729eb94d47b4c268d03562f08e810bccbb293b9c8b89fad661b2db8a8
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.
stek0v/levara · .agents/skills/levara-audit-task/SKILL.md · Independently audit a Levara long-horizon Task against its original objective, authority, Definition of Done, steps…
stek0v/levara · .agents/skills/levara-memory-workflow/SKILL.md · Automatically restore and curate durable project context through a Levara MCP server. Use implicitly for substantial…
stek0v/levara · .agents/skills/levara-run-long-task/SKILL.md · Run or resume long-horizon work through Levara Task Runtime with measurable Definition of Done, atomic step leases…
stek0v/levara · .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…
stek0v/levara · .agents/skills/openspec-explore/SKILL.md · Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying…
stek0v/levara · .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…
stek0v/levara · .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…
stek0v/levara · .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…
