Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Draft or update OpenClaw Enterprise RFCs and implementation plans with repository numbering and lifecycle rules.
$ npx skills add openclaw/openclaw-enterprise --skill spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/openclaw-enterprise spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec .claude/skills/spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .claude/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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.
$skill-installer install https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openclaw/openclaw-enterprise --skill spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/openclaw-enterprise spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/spec .agents/skills/spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .agents/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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 openclaw/openclaw-enterprise --skill spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/openclaw-enterprise spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/spec .cursor/skills/spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .cursor/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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.
$ gemini skills install https://github.com/openclaw/openclaw-enterprise.git --path .agents/skills/spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openclaw/openclaw-enterprise --skill spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/openclaw-enterprise spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/spec .gemini/skills/spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .gemini/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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 openclaw/openclaw-enterprise specInstalls 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 openclaw/openclaw-enterprise --skill spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/spec .github/skills/spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .github/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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 openclaw/openclaw-enterprise --skill spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/openclaw-enterprise spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/spec .opencode/skills/spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/spec into .opencode/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", 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.
specDraft or update OpenClaw Enterprise RFCs and implementation plans with repository numbering and lifecycle rules.
Spec is an agent skill from openclaw/openclaw-enterprise. Draft or update OpenClaw Enterprise RFCs and implementation plans with repository numbering and lifecycle rules.
Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/plan-template.md`, `references/plan.md` and `references/rfc.md`).
It sits in Agent Workflows, covering Planning. The repository describes itself as: The Enterprise-grade Control Plane for modern agentic workloads. The licence is MIT.
Read from SKILL.md and the folder at commit ccb76e6. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spec loads about 338 tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 137 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.
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); files beside SKILL.md are not scanned.
The full file from openclaw/openclaw-enterprise at commit ccb76e6, republished under its MIT licence (© openclaw). 137 words, ~338 tokens.
.claude/skills/spec/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Use the user's requested mode. If a request only asks to evaluate an idea or process, discuss it without creating or moving documents.
rfc <description>: propose an architectural decision. Read
the RFC workflow and use the shared
RFC template.plan [RFC-ID or path] <description>: plan implementation of an RFC or
independent feature. Read the plan workflow; its
scaffold is the plan template.These commands author documents. They do not by themselves authorize product implementation, acceptance, publication, or archive reorganization. Preserve any broader authorization already given in the conversation.
Paths in the workflows are relative to the repository root unless explicitly identified as bundled skill paths. The repository's specification process owns numbering, placement, status, and historical exceptions; read it before writing. Use $technical-writing for prose and $enterprise-testing for proportional verification requirements. Neither requires a global skill installation.
© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references, assets) in .agents/skills/spec of openclaw/openclaw-enterprise.
Open the folder on GitHubat commit ccb76e6
Spec 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 |
|---|---|---|---|---|---|---|
| Spec this skillopenclaw/openclaw-enterprise | 367 | — | ~338 | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 103k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 57 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None |
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
openclaw/openclaw-enterprise
Develop OpenClaw Enterprise changes with proportional verification and source-backed flow documentation for non-trivial behavior.
openclaw/openclaw-enterprise
Write, organize, name, edit, or review Enterprise developer documentation, specifications, and technical instructions; ground claims in current source and finish with a plain-language cleanup.
openclaw/openclaw-enterprise
Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
openclaw/openclaw-enterprise
Gate new or changed Enterprise tests and audit existing tests for observable behavior, credible regressions, duplicate coverage, and test-only production seams.
openclaw/openclaw-enterprise
Create or refine readable Mermaid diagrams for changes, architecture, lifecycles, and dependencies in Markdown documents and PR descriptions.
openclaw/openclaw-enterprise
Assess designs, public interfaces, state ownership, readability, and refactor proposals when the task calls for design review or structural simplification; not for unrelated routine edits.
Categories
Draft or update OpenClaw Enterprise RFCs and implementation plans with repository numbering and lifecycle rules. Spec is an agent skill from openclaw/openclaw-enterprise. Draft or update OpenClaw Enterprise RFCs and implementation plans with repository numbering and lifecycle rules.
Spec fits situations like: tasks that involve Planning.
Run `npx skills add openclaw/openclaw-enterprise --skill spec -a claude-code`. Or copy the skill folder (.agents/skills/spec in openclaw/openclaw-enterprise) into .claude/skills/spec in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openclaw/openclaw-enterprise --skill spec -a codex`. Or copy the skill folder (.agents/skills/spec in openclaw/openclaw-enterprise) into .agents/skills/spec in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw-enterprise --skill spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec, .gemini/skills/spec, .github/skills/spec and .opencode/skills/spec in your project.
SKILL.md names no scripts, command-line tools or credentials: Spec is instructions for the agent only.
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.
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. Review the folder before installing.
Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 338 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Spec: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openclaw (a GitHub organization) maintains it in openclaw/openclaw-enterprise, which has 367 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.
Source: openclaw/openclaw-enterprise on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.