OpenSpec Skills
Canonical home for agent skills used by openspec-schemas. Schemas installed from that repo reference the skills here; consumers pull the skills they need into their own project.
All skills live under .agents/skills/, one directory per skill, each with a SKILL.md (plus supporting files where needed).
Skills
| Skill |
Purpose |
| acceptance-test-authoring |
Setting up and writing acceptance tests over Markdown specs where headings carry the structure and fenced Gherkin carries the steps — extraction, effective-spec composition, spec linting, and Page Object Model conventions. Includes cucumber-js and behave stack packs. |
| architectural-decision-records |
Documenting, drafting, reviewing, and updating ADRs, decision logs, tradeoffs, and rationale. Includes ADR templates (MADR, Nygard, Y-statement). |
| c4-diagrams |
Explaining code architecture and visualizing systems with C4-style diagrams in ASCII or Mermaid. |
| discovery |
Breaking a large PRD into a release plan for an OpenSpec project — personas, journey map, MoSCoW prioritization, and thin vertical stories captured as an openspec/discovery.md checklist that feeds /opsx:propose one story at a time. Checkpointed per phase, so sessions can stop and resume. |
| gherkin-authoring |
Drafting, reviewing, and improving Gherkin/Cucumber scenarios and BDD acceptance criteria. |
| glossary |
Keeping domain and technical terms consistent across specs, requirements, design docs, ADRs, and tasks. |
| grill-me |
Relentlessly interviewing the user about a plan or design until shared understanding is reached. |
| openspec-git-discipline |
Git hygiene for OpenSpec propose/continue/apply/verify/archive workflows — proposal artifacts, branches, merges, and archive timing. |
| spec-as-source |
Umbrella skill making OpenSpec "Spec As Source" Spec-Driven Development using Behaviour Driven Development — spec.md with fenced-Gherkin authoring, acceptance-test-first task ordering, and BDD zone isolation as one opt-in workflow. Requires gherkin-authoring and acceptance-test-authoring; its templates override the schema's. |
| test-driven-development |
Implementing production changes through strict red-green-refactor with focused tests, meaningful boundaries, verified collaborator interactions, and maintainable test code. |
Installing skills into your project
Skills associated with a schema are installed automatically when you install that schema from openspec-schemas. You can also install any skill individually as described below.
The quickest way: point your coding agent at this repo and let it follow the install guide —
Install the discovery skill from https://github.com/intent-driven-dev/skills following its AGENT_INSTALL.md
To install by hand, clone this repo and copy the skill directories you need into your project's .agents/skills/:
git clone --depth 1 https://github.com/intent-driven-dev/skills.git /tmp/openspec-skills
mkdir -p your-project/.agents/skills
cp -R /tmp/openspec-skills/.agents/skills/<skill-name> your-project/.agents/skills/
If your agent doesn't discover skills in .agents/skills/, symlink the project-local copy into the agent's own skills folder (e.g. .claude/skills/ for Claude Code, .opencode/skills/ for OpenCode, .codex/skills/ for Codex):
mkdir -p your-project/.claude/skills
ln -s ../../.agents/skills/<skill-name> your-project/.claude/skills/<skill-name>
See AGENT_INSTALL.md for the full step-by-step flow.