speq-skill plugin
speq drives spec-driven development in Claude Code and Codex: mission, plan, implement and record into a permanent library.
- 54 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installation runs a script from the internet and puts a binary into the home directory.
- The agent writes and changes project code from specs, so the result must be reviewed.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/exasol-labs/speq-skill/main/install.sh | bashInstalls `speq` into `~/.local/bin`, the plugin into `~/.speq-skill/` and registers the skills.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installation runs a script from the internet and puts a binary into the home directory.
- The agent writes and changes project code from specs, so the result must be reviewed.
This is third-party code. Review the repository files before installing.
What it does
speq-skill sets a repeatable plan, implement, record loop around a library of specs. First `/speq:mission` studies the project and writes `specs/mission.md` and `specs/architecture.md`. Then `/speq:plan` reads existing specs, asks clarifying questions and prepares a plan with deltas, `/speq:implement` writes code under quality and testing guardrails, and `/speq:record` merges the deltas into the permanent library. The skills come with a Rust utility `speq` that lists and reads specs so the agent loads only the relevant ones. Small fixes have `/speq:patch` with no plan and `/speq:patch-pr` that also ships a ready pull request. Each skill rests on semantic anchors such as London School TDD, BLUF and ADR.
Who it is for. Developers who run a project with an agent and want requirements in small specs without bloating the context.
Good fit when
- A new project starts with a mission and architecture that the agent collects through an interview.
- Before a large task the agent reads only the relevant specs and agrees a plan.
- After implementation, deltas are merged into the permanent requirements library.
- A small fix ships as one pull request through `/speq:patch-pr`.
Not a fit when
- You need a ready process with no binary install, since the `speq` utility goes into `~/.local/bin`.
- Your platform is outside Linux x86_64, ARM64 and macOS on Apple Silicon, so you must build from source.
- The project has no requirements and you do not plan to write specs.
Example request
Run the project mission, then draft a plan for adding CSV export from the specs and ask questions before writing any code.Limitations
The installer downloads a prebuilt binary for Linux x86_64, ARM64 and macOS on Apple Silicon and stops on other platforms, pointing to a source build. Plugin files go into `~/.speq-skill/`, and skills register in Claude Code and Codex when those agents are found. Specs and plans are created in your repository and need review like any code. The workflow expects an agent that asks questions, so fully automated runs will slow down.
How to disable. Follow the uninstall section of `docs/installation.md`: it removes the binary from `~/.local/bin`, the `~/.speq-skill/` directory and the skill registration. Delete the `specs/` folder in your project yourself if you do not need the specs.
FAQ
Which command comes first?
`/speq:mission` in Claude Code and `$speq:mission` in Codex. It studies the project and creates `specs/mission.md`.
What does the installer do?
Downloads the `speq` binary into `~/.local/bin/speq`, puts plugin files in `~/.speq-skill/` and registers skills for Claude Code and Codex.
Where are specs stored?
In `specs/<domain>/<feature>/spec.md`, with architecture in `specs/architecture.md` and plans in `specs/_plans/`.
Is a plan needed for a small fix?
No, `/speq:patch` applies the change straight away and `/speq:patch-pr` also prepares one ready pull request.
What are semantic anchors?
They are names of established methodologies, for example London School TDD, BLUF and ADR. Skills reference them to steer the agent toward documented practices.
Discussion
No questions or reviews yet.
Related
PluginsTwo skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
A skill that interviews you and writes requirements.md, design.md and tasks.md so Claude Code and Cursor work from one plan
Spec Kit skills for Claude Code, Codex, Cursor, Copilot and OpenCode: specify, plan, tasks, implement, baseline of existing code
The spxa CLI and a skill set for spec-driven development in Claude Code, Codex and Cursor, from a change proposal to the archive
A Claude Code plugin: spec-driven development over a single SPEC.md file, a loop of seven commands with no sub-agents
A CLI, MCP server and skill for spec-driven development: short markdown specs, a task board and search that an agent can read.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| speq-skill (this card) | no | 54 | |
| OpenSpec | no | 74,784 | difference: `openspec` defines its own change format, while speq keeps a permanent spec library and a Rust utility |
| Spec Kit | no | 149,633 | difference: `spec-kit` follows GitHub stages, while speq shrinks the loop to plan, implement and record with only the relevant specs read |
README in short
The README explains the mission, plan, implement and record loop, the installer, the `specs/` folder layout and quick patch commands. Details live in the `docs/` folder.