Speckit cli

Skill merllinsbeard/merlin-skills/skills/speckit-cli

Spec-first, skill-first, goal-first coding skill pack for Codex.

Install

npx -y skills add merllinsbeard/merlin-skills --skill speckit-cli

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.2 KB, as published. Nobody here has run it

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/[email protected]
specify version

For one-off use without persistent install:

uvx --from git+https://github.com/github/[email protected] 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.