Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
Install Ospec
$ npx skills add clawplays/ospec --skill ospec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install clawplays/ospec ospec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .claude/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add clawplays/ospec --skill ospec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install clawplays/ospec ospec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .agents/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add clawplays/ospec --skill ospec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install clawplays/ospec ospec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .cursor/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add clawplays/ospec --skill ospec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install clawplays/ospec ospec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .gemini/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install clawplays/ospec ospecInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add clawplays/ospec --skill ospec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .github/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add clawplays/ospec --skill ospec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install clawplays/ospec ospec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ospec" agent skill from https://github.com/clawplays/ospec/tree/main into .opencode/skills/ospec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ospec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ospec- GitHub stars
- 452
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,309 words
- Files
- 363 (incl. scripts, assets)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
- Works in 4 steps: .skillrc for layout, language, workflow… → the Table of Contents section of… → The current session brief, bootstrap,… → …
- Agent Workflows work in your project
- SKILL.md covers Default Entry, Workflow Router, Visibility And Decisions and Goal Controller Layer, plus 3 more sections
What it does
Ospec is an agent skill from clawplays/ospec. Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 370 other files, including scripts and assets (for example `.github/release.yml`, `.github/workflows/publish-npm.yml` and `.ospec/asset-sources.json`).
It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: Spec-driven, agentic workflow framework for AI coding agents. Turn a request into a verifiable goal loop — plan, act, verify — with durable specs and evidence in your repo. Works… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/ospec”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- .skillrc for layout, language, workflow policy, and model profiles.
- the Table of Contents section of .ospec/session-brief.md to see which archived changes and knowledge documents exist, then ospec docs…
- The current session brief, bootstrap, dispatch, review, or repair packet.
- Only the indexed project documents, change files, and target files named by that packet.
What it can do on your machine
Read from SKILL.md and the folder at commit be449f2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ospec loads about 2.6k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 1,309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from clawplays/ospec at commit be449f2, republished under its MIT licence (© clawplays). 1,309 words, ~2,616 tokens.
Download SKILL.mdSave it as
.claude/skills/ospec/SKILL.md (or your agent's skills folder). This skill also uses 362 other files; get the full folder from GitHub.- name
- ospec
- description
- Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
- tags
- cli, workflow, automation, ospec
OSpec Router
Use this root skill as a compact router. Keep invariant safety and workflow-selection rules here; load detailed commands and stage protocols from the initialized project's indexed files only when that stage is active.
Default Entry
When the user asks to initialize a project, run ospec init [path]. In AI-assisted initialization, pass the explicit or conversational language with --document-language. If useful context is missing, ask once for a short project summary or tech stack; if the user skips it, continue with placeholders. Verify the generated files on disk and stop before creating work unless the user explicitly asks for a change or goal.
Initialization is change-ready only when .skillrc, the managed .ospec/ or classic OSpec directory, active and archived change directories, SKILL.md, SKILL.index.json, the index builder (.ospec/tools/build-index-auto.cjs), for-ai/ protocol files, and baseline docs/project/ knowledge files exist. Verify those managed files on disk yourself and never claim initialization is complete before you have: a command that exited zero is not evidence that the files are there.
Do not hand-write an approximation of ospec init. Do not assume a web stack, apply business scaffold, generate docs/project/bootstrap-summary.md, create queue work, or create the first change without explicit intent.
Workflow Router
- Use
ospec change/ospec-changewhen the user selects a Change. Its source of truth ischanges/active/<change>/proposal.md,changes/active/<change>/tasks.md,state.json,verification.md, andreview.md;ospec newremains a compatibility alias. - Use
ospec goal/ospec-goalonly when the user selects a Goal. It additionally ownschanges/active/<change>/design.md,changes/active/<change>/implementation-plan.md,changes/active/<change>/artifacts/agents/task-graph.json, worker/reviewer artifacts, and evidence gates. - Never auto-promote, reject, or replace a user-selected Change because of complexity, risk, file count, parallelism, or batch size. The user's explicit profile choice is authoritative.
- Enter queue mode only when the user explicitly asks to queue or execute multiple changes.
For an initialized project, read in this order:
.skillrcfor layout, language, workflow policy, and model profiles.- the
Table of Contentssection of.ospec/session-brief.mdto see which archived changes and knowledge documents exist, thenospec docs locate --feature <slug>/--affects <path>to jump straight to the section that describes a behavior, andospec index query <keyword...>as the keyword router intoSKILL.index.json; never read the whole index file — it grows without bound as changes archive. - The current session brief, bootstrap, dispatch, review, or repair packet.
- Only the indexed project documents, change files, and target files named by that packet.
Do not load every historical change or every protocol file by default. for-ai/ai-guide.md is a router into the protocol that owns each profile, not a rule file — the ospec-change and ospec-goal skills carry the operating rules for their profile. Behind them: for-ai/change-protocol.md is the classic-change contract in full, and for-ai/execution-protocol.md is the goal controller reference, opened only when a named situation needs its detail and never by a classic change, which that file forbids. Use ospec help or subcommand help instead of carrying the complete CLI catalog in context.
Visibility And Decisions
Announce-Before-Act: before workflow actions, state the OSpec workflow and stage, the command and artifact it writes, and any blocking gate. Only in the goal controller layer, also state the native agent count and the actual native mechanism; the classic change flow launches no subagents and must not announce one.Brainstorm-First: before locking a goal design, surface open direction, architecture, API, data, UI, risk, and scope decisions one at a time. Prefer a durable required decision over a silent assumption.Zero-Setup: the user states the requirement; the AI runs OSpec controller commands and the user only answers decisions. Do not ask the user to operate routine setup commands.- Required pending decisions block worker dispatch. Preserve
PENDING,NEEDS_CONTEXT,BLOCKED,DONE_WITH_CONCERNS, andDONErather than hiding uncertainty.
Decision gates belong to the user on every harness: never auto-select a recommended option or resolve a gate yourself, present each gate through the capability ladder — a harness-native question UI (Claude Code AskUserQuestion, Gemini ask_user), else a plan/approval UI, else the decision report Chat Prompt in chat — and wait for the user's actual answer. You always ask; only the presentation differs. The full contract is stated where your profile is already sent: for-ai/change-protocol.md for a classic change, the ospec-goal skill and for-ai/execution-protocol.md for a goal.
In Claude Code, install the managed hook once with ospec session hook --target claude --apply when missing; PreToolUse(Task) is then a hard dispatch gate and prompt hooks stay silent unless a required decision is pending. That hook is a Claude-only, opt-in convenience — ospec session hook --target accepts no other harness and ospec init writes no .claude/ — so it never replaces the documented contract.
Show full SKILL.md (555 more words)Show less
Goal Controller Layer
Use the full ospec execute ... task-graph/controller layer only for Goal work. A classic Change may use the shared ospec execute decision command for durable user choices, but it must not enter Goal bootstrap, workspace, dispatch, review, evidence, or Loop commands.
A router routes: the controller invariants — preflight staging, the combined planning review and its repair allowance, worker profiles, dispatch and review binding, reviewer independence, evidence and archive gates — are not restated here. Load the ones you act on from the ospec-goal skill; for-ai/execution-protocol.md holds their authoritative detail, including the logical model-profile names, and is opened only when a named situation calls for it. Detailed goal artifacts live under changes/active/<change>/artifacts/agents/ and artifacts/reviews/; read the current dispatch, review, or repair packet for exact paths and commands.
Do not archive while task graph, review, decision, documentation, optional-step, worker-status, or verification gates are unresolved during normal closeout.
Documentation And Archive
Archiving a finalized change or goal writes its SKILL.index.json.archived_changes entry (carrying features and doc_updates), refreshes the affected docs/project/feature-catalog.md rows, and replaces each touched feature section's ospec:last-change traceability comment idempotently — the engine's only write into a human-owned document, and a comment failure warns instead of blocking. No file is generated under docs/project/changes/; render an archived change on demand with ospec changes show <archive>. Behavior, architecture, module, API, or operational changes must additionally update the relevant human-maintained docs/project/ files. When the task graph enables the documentation contract, every task declares documentation_updates; use [] only when no project documentation changes are needed, include each declared document in target_files, and preserve dispatch-to-completion evidence of a meaningful normalized-content change.
Use ospec verify for the active workflow. For normal closeout, use ospec finalize [changes/active/<change>]; use ospec archive --check only for preview. Finalize must verify completeness, archive, rebuild docs/project/feature-catalog.md, and rebuild SKILL.index.json so its documents and archived_changes sections locate the completed behavior and link declared durable project documents. Git commit remains separate.
Force archive requires explicit user acceptance and is never an automatic fallback. First report the failing gates and every NOT_VERIFIED item to the user, then take their explicit acceptance; the CLI enforces its own exact-name confirmation and reason flags. Never infer that authorization from urgency, a blocker, or a request to "finish". A forced archive bypasses completion gates only — it preserves failed checks and pending state, and must never be described as completed behavior. The full procedure lives on the path that needs it: for-ai/change-protocol.md for a classic change, for-ai/execution-protocol.md for a goal.
After archive, verify:
- the completed behavior is discoverable through
docs/project/feature-catalog.mdandospec docs locate; - the archived change renders from its index entry via
ospec changes show <archive>; - project docs and archived change records are present in
SKILL.index.json; - section offsets are stable under LF-normalized content;
- no required documentation update was omitted.
Use ospec docs generate for a docs-only repair or refresh. Do not create a change merely to repair project knowledge unless the user asks for one.
Compact Command Routes
Initialize: ospec init [path] -> verify generated project shell
Change: ospec change <name> -> implement -> ospec verify -> ospec finalize
Goal: ospec goal <name> -> preflights -> task graph -> combined planning review -> workers/task reviews -> final review -> verify/finalize
Docs: ospec docs generate [path] -> ospec docs status -> ospec index check
Resume: ospec session [path] -> read brief/index -> run the persisted next safe command
Troubleshoot: ospec status [path] -> ospec helpUse CLI commands for initialization, verification, index generation, and archive. Do not replace managed operations with ad hoc filesystem edits.
Completion Discipline
Before claiming completion:
- Verify the active workflow and fresh project checks.
- Confirm relevant docs and documentation contracts.
- Confirm worker/reviewer/decision/evidence gates for goals.
- Confirm skills and indexes when knowledge changed.
- After archive, confirm the feature and its documents are discoverable without replaying conversation history.
© clawplays, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 362 other files (scripts, assets) in the repository root of clawplays/ospec.
- SKILL.md
- .editorconfig
- .gitattributes
- .github/release.yml
- .github/workflows/publish-npm.yml
- .gitignore
- .ospec/asset-sources.json
- .ospec/templates/hooks/post-merge
- .ospec/templates/hooks/pre-commit
- LICENSE
- README.md
- agents/openai.yaml
- assets/for-ai/ar
- … and 350 more
Open the folder on GitHubat commit be449f2
Compare with similar skills
Ospec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ospec this skillclawplays/ospec | 452 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Orca Run Replayiflytek/skillhub | 5.2k | 4 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Ixix-infrastructure/Ix | 1.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| PicoClaw Agentsipeed/picoclaw | 30k | — | ~7.2k | Automated safety check: Notes | MIT | |
| Chatgpt AppsHaohao-end/openagent | 791 | 1 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Orca Run Replay
iflytek/skillhub
Answers questions about a past agent run from its recording, using causal graphs and replay, instead of reconstructing events from memory.
Ix
ix-infrastructure/Ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
PicoClaw Agent
sipeed/picoclaw
Answers questions about running and changing PicoClaw, from onboarding and model selection to MCP server setup, skill loading and scheduled jobs.
Chatgpt Apps
Haohao-end/openagent
Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.
Chatgpt App Builder
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins.
More from clawplays/ospec
Ospec Change
clawplays/ospec
Create or advance a lightweight OSpec change using the classic fast workflow.
Ospec Goal
clawplays/ospec
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
Related
Works with
Categories
Questions about Ospec
What does Ospec do?
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge. Ospec is an agent skill from clawplays/ospec. Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
When should I use Ospec?
Ospec fits situations like: agent Workflows work in your project.
How do I install Ospec in Claude Code?
Run `npx skills add clawplays/ospec --skill ospec -a claude-code`. Or copy the skill folder (the clawplays/ospec repository) into .claude/skills/ospec in your project. Claude Code loads it when a task matches its description.
How do I install Ospec in Codex?
Run `npx skills add clawplays/ospec --skill ospec -a codex`. Or copy the skill folder (the clawplays/ospec repository) into .agents/skills/ospec in your project. Codex loads it when a task matches its description.
Can I use Ospec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add clawplays/ospec --skill ospec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ospec, .gemini/skills/ospec, .github/skills/ospec and .opencode/skills/ospec in your project.
What does Ospec need to run?
SKILL.md names no scripts, command-line tools or credentials: Ospec is instructions for the agent only.
Does Ospec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ospec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Ospec use?
Ospec is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ospec use?
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ospec?
Skills that share tags, products or a category with Ospec: Crush Configuration (charmbracelet/crush, 29k stars), Orca Run Replay (iflytek/skillhub, 5.2k stars), Ix (ix-infrastructure/Ix, 1.1k stars) and PicoClaw Agent (sipeed/picoclaw, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ospec?
clawplays (a GitHub user) maintains it in clawplays/ospec, which has 452 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 26, 2026.
Source: clawplays/ospec on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.