Speq Skill

speq-skill

A light-weight and straightforward workflow for spec-driven development with Claude Code or Codex

Getting Started • Why • How It Works • Documentation • Installation

Getting Started

Then open Claude Code or Codex and start with the matching trigger: /speq:mission in Claude Code, or $speq:mission in Codex.

What does the installer do?

- Downloads a pre-built speq binary for your platform (Linux x86_64/ARM64, macOS Apple Silicon). On other platforms it stops and points to the source build
- Installs the CLI to ~/.local/bin/speq
- Installs plugin files to ~/.speq-skill/
- Registers /speq:* skills for Claude Code and $-triggered skill suggestions for Codex when available
- Registers the local Codex marketplace when the Codex CLI is available

To uninstall, see Installation — Uninstall.

Why I Built It

I want to leverage AI coding agents such as Claude Code and Codex as effective tools for software engineering.

There are many other spec-driven development tools out there...

...but I wanted the following:

1. A workflow that is not primped on one language or framework (e.g., Python or TypeScript)
2. A straightforward repeatable workflow (plan → implement → record)
3. A permanent and growing spec-library
4. A workflow that keeps the specs small to avoid context cluttering
5. A workflow that keeps asking me instead of making assumptions
6. Semantic anchors that ground AI behavior in established methodologies

So I built speq-skill.

It combines skills with a simple CLI called speq that lists and reads the permanent spec library. The coding agent lists the features, then reads only the relevant ones during planning and during the implementation. This avoids reading unnecessary specs into the context window.

New to spec-driven development? Read "Spec-driven…