Specify

Skill MakFly/ai-dev-kit/.claude/skills/specify

Spec-Driven Agentic OS for Claude Code + OpenAI Codex CLI. Native skills, subagents, hooks, and an adversarial codex review loop. Inspired by github/spec-kit, built on Claude Code primitives. No daemon, no vendor lock-in.

Install

npx -y skills add MakFly/ai-dev-kit --skill specify

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

2 stars2 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

Use PROACTIVELY when the user invokes /specify <slug> or asks to "write the spec", "define the feature", "what should we build". Runs the `specifier` subagent in a forked context which writes specs/<slug>/spec.md. Refuses to write code or plan.

SKILL.md

2.0 KB, as published. Nobody here has run it

/specify

Author specs/<slug>/spec.md via the specifier subagent.

Procedure

Parse the argument. <slug> is the first arg (kebab-case). The rest is free-form user intent.
Reject if conflict. If specs/<slug>/spec.md already exists with Status: locked, refuse and propose /clarify <slug> instead.
Read constitution. cat memory/constitution.md — surface any obvious tension with the user's intent before delegating.
Check digest freshness. If newest supports/digests/digest-*.md is > 7 days old, warn the user. Do not block.
Delegate. Invoke the specifier subagent with the user intent and slug. The subagent writes the file.
Surface Open questions. When specifier returns, list the spec's §6 Open questions to the user. Suggest /clarify <slug> if any.
Commit. git add specs/<slug>/spec.md && git commit -m "spec(<slug>): initial draft". Ask user before committing if they prefer to review first.

Doctrine

WHAT only. No HOW. If the user's intent already contains HOW ("use redis", "with a worker"), redirect those to /plan.
One spec, one slug. Refuse to mix multiple features in one spec.
Surface ambiguity, don't smooth it. Better to write a spec with 5 Open questions than a "clear" spec that silently chose for the user.

Pipeline position

/constitution → /specify [YOU] → /clarify → /plan → /tasks → /implement → /review