merllinsbeardmerllinsbeard/merlin-skills/skills/speckit-cli/SKILL.md

speckit-cli

Skill1 starsChanged 6 months agoMITView on GitHub

Install, verify, initialize, and manage the official GitHub Spec Kit `specify` CLI. Use when setting up spec-kit project infrastructure, checking CLI version/features, installing Codex integration skills, or managing Spec Kit integrations, extensions, and presets.

In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brainstormingSkill
- create-goalSkill
- diagnoseSkill
- grill-with-docsSkill
- install-merlin-skillsSkill
- merlin-skills-routingSkill
- playwright-cliSkill
- playwright-skillSkill
- gstack-qaSkill
- gstack-shipSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- tddSkill
- to-prdSkill
- zoom-outSkill

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use the official GitHub Spec Kit specify CLI to set up and maintain the .specify/ project infrastructure that the speckit-* skills rely on.
line 8
Distinctive:
Use this skill when the user asks to:
line 14
Very specific:
add the Codex integration that installs $speckit-* skills.
line 18
Very specific:
Do not use this for writing specs once the project is initialized.
line 22
Very specific:
If a local specify behaves like an older version, prefer checking first:
line 39
Very specific:
Do not install speckit-git-* behavior implicitly.
line 101
Distinctive:
After CLI setup, the Merlin route is:
line 105
Very specific:
Use speckit-implement only when the user explicitly wants native upstream Spec Kit implementation instead of the Merlin /goal path.
line 111

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Spec Kit CLI

Use the official GitHub Spec Kit specify CLI to set up and maintain the .specify/ project infrastructure that the speckit-* skills rely on.

This is a Merlin-owned wrapper around the official CLI. Do not reimplement Spec Kit commands here.

When To Use

Use this skill when the user asks to:

install or update GitHub Spec Kit;
initialize a project for Spec Kit;
add the Codex integration that installs $speckit-* skills;
inspect specify version or feature support;
manage Spec Kit integrations, extensions, presets, or workflows.

Do not use this for writing specs once the project is initialized. Route to speckit-constitution, speckit-specify, speckit-clarify, speckit-plan, or speckit-tasks.

Official Install

Spec Kit is installed from GitHub, not from PyPI.

uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@v0.8.12
specify version

For one-off use without persistent install:

uvx --from git+https://github.com/github/spec-kit.git@v0.8.12 specify version

If a local specify behaves like an older version, prefer checking first:

specify version --features --json
specify self check

Initialize A Project

Codex uses Spec Kit's skills-based integration.

specify init --here --integration codex --script sh

For an existing non-empty repo:

specify init --here --force --integration codex --script sh

For a read-only or planning dry run, inspect the intended target first and avoid mutating the repo until the user asks for setup.

What Init Creates

Expected Codex setup:

.agents/skills/speckit-*/SKILL.md
.specify/memory/constitution.md
.specify/scripts/bash/
.specify/templates/
.specify/workflows/
AGENTS.md managed Spec Kit section

The user-facing skills are invoked as $speckit-*.

Integration Management

Useful commands:

specify integration list
specify integration install codex
specify integration use codex
specify check

Install additional integrations only when requested. Codex is multi-install safe because it uses .agents/skills and AGENTS.md.

Extensions And Presets

Extensions add capabilities. Presets customize templates or terminology.

specify extension search
specify extension add <extension-name>
specify preset search
specify preset add <preset-name>

Do not install speckit-git-* behavior implicitly. Git branch, issue, commit, and remote side effects should stay explicit and remain compatible with the repo's own git rules and gstack-ship.

Merlin Default

After CLI setup, the Merlin route is:

speckit-constitution -> speckit-specify -> speckit-clarify -> speckit-plan -> speckit-tasks -> speckit-analyze/checklist -> create-goal -> /goal

Use speckit-implement only when the user explicitly wants native upstream Spec Kit implementation instead of the Merlin /goal path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free