PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Write technical specs that let agents implement autonomously.
Install Specification Writing
$ npx skills add EpicenterHQ/epicenter --skill specification-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EpicenterHQ/epicenter specification-writing --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/EpicenterHQ/epicenter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/specification-writing .claude/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .claude/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writingType 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 EpicenterHQ/epicenter --skill specification-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EpicenterHQ/epicenter specification-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/specification-writing .agents/skills/specification-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .agents/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 EpicenterHQ/epicenter --skill specification-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EpicenterHQ/epicenter specification-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/specification-writing .cursor/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .cursor/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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/EpicenterHQ/epicenter.git --path .agents/skills/specification-writing--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 EpicenterHQ/epicenter --skill specification-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EpicenterHQ/epicenter specification-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/specification-writing .gemini/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .gemini/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 EpicenterHQ/epicenter specification-writingInstalls 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 EpicenterHQ/epicenter --skill specification-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/specification-writing .github/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .github/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 EpicenterHQ/epicenter --skill specification-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EpicenterHQ/epicenter specification-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/specification-writing .opencode/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/specification-writing into .opencode/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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
specification-writing- GitHub stars
- 4.8k
- Token cost
- ~4k tokens
- SKILL.md length
- 1,355 words
- Files
- 2 (incl. references)
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write technical specs that let agents implement autonomously.
- Plan this feature
- SKILL.md covers References, The Core Philosophy, Maintainer-Time Contract and Spec Placement, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Create a planning doc
What it does
Specification Writing is an agent skill from EpicenterHQ/epicenter. Write technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".
Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/decision-hygiene.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: Open-source, local-first apps.
When your agent uses it
- Plan this feature
- Create a planning doc
Example prompts
- “write a spec”
- “plan this feature”
- “create a planning doc”
- “/specification-writing”
What it can do on your machine
Read from SKILL.md and the folder at commit 5b4bb69. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Specification Writing loads about 4k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 38 tokens; SKILL.md has 1,355 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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,355 words (~4,046 tokens).
“Follow writing-voice for prose sections. For ownership or flow explanations, lead with the useful model, ground it in the relevant boundary, and keep only the diagrams and prose implementation needs.”
- name
- specification-writing
- metadata.author
- epicenter
- metadata.version
- 1.0
Files
SKILL.md and 1 other file (references) in .agents/skills/specification-writing of EpicenterHQ/epicenter.
- SKILL.md
- references/decision-hygiene.md
Open the folder on GitHubat commit 5b4bb69
Compare with similar skills
Specification Writing 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 |
|---|---|---|---|---|---|---|
| Specification Writing this skillEpicenterHQ/epicenter | 4.8k | — | ~4k | Automated safety check: Pass | Custom licence | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Architecture Decision
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
More from EpicenterHQ/epicenter
All 65 skills in this repoAgent Instructions
EpicenterHQ/epicenter
Write and maintain repository guidance across AGENTS.md, CLAUDE.md, and .agents/skills.
Consult Claude
EpicenterHQ/epicenter
Assign Claude Code a read-only investigation, recommendation, or finished text draft.
Better Auth Security Best Practices
EpicenterHQ/epicenter
Better Auth security hardening: rate limits, secrets, CSRF, trusted origins, cookies, sessions, OAuth tokens, and audit logging.
Cohesion Over Testability
EpicenterHQ/epicenter
Collapse test-shaped production boundaries while preserving behavior and coverage.
Collapse Pass
EpicenterHQ/epicenter
Remove indirection that does not earn its boundary across a diff or package.
Error Handling
EpicenterHQ/epicenter
Apply Wellcrafted Result patterns to fallible operations and preserve failures at boundaries.
Related
Categories
Questions about Specification Writing
What does Specification Writing do?
Write technical specs that let agents implement autonomously. Specification Writing is an agent skill from EpicenterHQ/epicenter. Write technical specs that let agents implement autonomously.
When should I use Specification Writing?
Specification Writing fits situations like: plan this feature; create a planning doc.
How do I install Specification Writing in Claude Code?
Run `npx skills add EpicenterHQ/epicenter --skill specification-writing -a claude-code`. Or copy the skill folder (.agents/skills/specification-writing in EpicenterHQ/epicenter) into .claude/skills/specification-writing in your project. Claude Code loads it when a task matches its description.
How do I install Specification Writing in Codex?
Run `npx skills add EpicenterHQ/epicenter --skill specification-writing -a codex`. Or copy the skill folder (.agents/skills/specification-writing in EpicenterHQ/epicenter) into .agents/skills/specification-writing in your project. Codex loads it when a task matches its description.
Can I use Specification Writing 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 EpicenterHQ/epicenter --skill specification-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specification-writing, .gemini/skills/specification-writing, .github/skills/specification-writing and .opencode/skills/specification-writing in your project.
What does Specification Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Specification Writing is instructions for the agent only.
Does Specification Writing 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 Specification Writing 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. Review the folder before installing.
What licence does Specification Writing use?
Specification Writing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Specification Writing use?
About 4k tokens (SKILL.md is roughly 16k 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 711 tokens, read only when the agent opens those files.
What are the alternatives to Specification Writing?
Skills that share tags, products or a category with Specification Writing: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specification Writing?
EpicenterHQ (a GitHub organization) maintains it in EpicenterHQ/epicenter, which has 4,821 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on October 8, 2026.
Source: EpicenterHQ/epicenter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.