speckit-agent-skills
Spec Kit skills for Claude Code, Codex, Cursor, Copilot and OpenCode: specify, plan, tasks, implement, baseline of existing code
- 172 ★ on the repository
- Last commit
Minimal access
Why this level
- The skills guide the agent through the specification and implementation cycle, and the agent changes code and files itself on your requests
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/speckit-agent-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills guide the agent through the specification and implementation cycle, and the agent changes code and files itself on your requests
This is third-party code. Review the repository files before installing.
What it does
The repository keeps the current Spec Kit output and a small set of its own skills. Shared skills live in `skills/`: `speckit-constitution`, `speckit-specify`, `speckit-clarify`, `speckit-plan`, `speckit-tasks`, `speckit-analyze`, `speckit-checklist`, `speckit-implement`, `speckit-converge` and `speckit-taskstoissues`. Claude Code uses them through `.claude/skills` and Codex through `.agents/skills`. The author's own skills add two things: `speckit-baseline` derives specifications from existing code and `claude-command-converter` converts Claude commands into the Agent Skill format. For Cursor, Copilot CLI, OpenCode and Gemini there are generated layers (`.cursor/skills`, `.github/agents`, `.opencode/commands`, `.gemini/commands`). `VERSION.md` records the Spec Kit version, and CI checks for a new release and regenerates the output.
Who it is for. Teams that develop with Spec Kit across several agents at once and want ready skills at hand without running `specify init` separately in each project.
Good fit when
- A feature must go through the specification, plan, tasks and implementation cycle
- There is working code without a specification and a baseline specification must be derived from it
- Claude commands must be turned into Agent Skill format skills
- The same skills are needed by Claude Code, Codex and Cursor from one place
Not a fit when
- Spec Kit itself with the `specify` command is needed: the repository holds the output and not the utility
- A pinned version for your project is needed: the set follows the latest Spec Kit release
- AGPL-3.0 license terms are unacceptable for you
Example request
Prepare a specification for a new report export feature and make a plan and task list from it.Limitations
Skills do not always run by themselves: invoke them explicitly through the runtime skills mechanism. If a skill fails, check its `SKILL.md`, the Spec Kit project structure and prerequisites. Run Spec Kit scripts from the repository root, preferably with `--json` modes. Gemini is kept in the repository but is not part of the CI regeneration set. The AGPL-3.0 license places requirements on distributing changes. Legacy layouts of old runtimes should not be restored. The latest commit in the repository is from November 2026.
How to disable. Delete the copied `speckit-*` directories from `~/.claude/skills/` or `~/.agents/skills/`. If a `.specify/` folder and specification files appeared in your project, they stay as ordinary files.
FAQ
What is in the set?
Shared Spec Kit skills: constitution, specify, clarify, plan, tasks, analyze, checklist, implement, converge, taskstoissues, plus the author's `speckit-baseline` and `claude-command-converter`.
How do I install it?
The README has no install command: clone the repository and copy the directories from `skills/` into the agent skills folder. Claude Code and Codex read them through the `.claude/skills` and `.agents/skills` links.
What does speckit-baseline do?
Derives specifications from existing code, that is, creates a starting point for a project that had no specifications yet.
Which runtimes have output?
CI runs `specify init` for Codex, agy, Cursor Agent, Copilot, OpenCode and Claude. Gemini is kept in the repository but is not regenerated.
How do I find the Spec Kit version?
Open `VERSION.md`: it records the tracked version. CI checks the latest release and regenerates output only when it changes.
Discussion
No questions or reviews yet.
Related
Skills14 skills that find the gaps in a task before the code: interviews, plans, assumption tests and proof that a bug fix works
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
speq drives spec-driven development in Claude Code and Codex: mission, plan, implement and record into a permanent library.
A skill that interviews you and writes requirements.md, design.md and tasks.md so Claude Code and Cursor work from one plan
Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task
17 ready skills for tests, Git, READMEs and multi-agent work plus a kernel that checks skill execution in Claude Code and Codex.
README in short
The README explains the repository makeup: shared skills, layers for Cursor, Copilot, OpenCode and Gemini and the `.specify/` infrastructure. The integration model, a path table, the skill list, the structure and usage notes follow.