# Spec-Driven Develop — Spec-First Agent Skill (2026)

> Spec-Driven Develop is a spec-first skill/plugin for big agent changes; verified 715★ with installs for Claude Code, Codex marketplace, and Cursor.

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

## Quick Use

```bash
/plugin marketplace add zhu1090093659/spec_driven_develop
/plugin install spec-driven-develop@spec-driven-develop
/reload-plugins
# Codex: codex plugin marketplace add zhu1090093659/spec_driven_develop --ref main
```

## Intro

Spec-Driven Develop is a spec-first skill/plugin for big agent changes; verified 715★ with installs for Claude Code, Codex marketplace, and Cursor.

**Best for:** Large migrations or rewrites where you want an agent to produce a plan/spec first, then execute with checkpoints

**Works with:** Claude Code plugins, Codex CLI plugin marketplace, Cursor skills, and generic Markdown-based agent skills

**Setup time:** 5-15 minutes

## Main

- The README is explicit about multi-platform packaging: Claude Code plugin metadata, Codex plugin marketplace files, Cursor install scripts, and a generic SKILL.md fallback for other agents.
- Because it’s spec-first, it’s best used on transformations (rewrite/migrate/overhaul) where you want a checklist-driven gate before code changes proceed.
- A pragmatic adoption path is to install it in one tool first (Claude Code or Codex), run it on a small module, then scale to whole-repo migrations once the workflow feels predictable.
- Treat it as a process tool: you are buying repeatable checkpoints (spec → execute → tests) rather than a single prompt; the value is consistency across big changes.

### FAQ

- **Is it tied to one agent platform?**: No. It ships plugin packaging for multiple tools and also provides a generic SKILL.md path for any agent that reads Markdown instructions.
- **What is a good first use case?**: Try a focused refactor or migration on one directory; verify the spec/checkpoint loop before attempting an entire project rewrite.
- **How do I install for Codex?**: The README documents adding the GitHub marketplace to Codex, then enabling the plugin (or configuring it in `~/.codex/config.toml`).

## Source & Thanks

> Source: https://github.com/zhu1090093659/spec_driven_develop
> License: MIT
> GitHub stars: 715 · forks: 87

---

<!-- ZH -->

## Quick Use

```bash
/plugin marketplace add zhu1090093659/spec_driven_develop
/plugin install spec-driven-develop@spec-driven-develop
/reload-plugins
# Codex: codex plugin marketplace add zhu1090093659/spec_driven_develop --ref main
```

## Intro

Spec-Driven Develop 是规格优先的 skill/plugin，适合大规模改造；已核验 715★，支持 Claude Code、Codex marketplace 与 Cursor 安装。

**Best for:** 需要“先规格/计划、再执行”的大规模迁移与重构场景

**Works with:** Claude Code 插件、Codex CLI 插件市场、Cursor skills，以及通用 Markdown 技能机制

**Setup time:** 5-15 minutes

## Main

- README 明确说明了多平台封装：Claude Code 插件、Codex plugin marketplace、Cursor 安装脚本，以及对其他 agent 的通用 SKILL.md 兜底。
- 它更适合规格优先的“大改造”：先把目标拆成可验证的 checklist，再推进代码变更，降低一次性重构的失控风险。
- 推荐先在一个工具里落地（Claude Code 或 Codex），用小模块试跑流程，再扩到全仓库迁移/重写，确保可预测性。
- 把它当成流程工具：价值在于“规格 → 执行 → 测试”的重复性与一致性，而不是一次性的长 prompt。

### FAQ

- **只绑定某一个 agent 平台吗？**：不是。它为多种工具提供插件封装，同时也提供通用 SKILL.md，可被任何读取 Markdown 指令的 agent 使用。
- **第一次用建议选什么任务？**：先选一个目录做小范围迁移/重构，验证“规格+检查点”闭环，再扩大到全项目重写。
- **Codex 怎么安装？**：README 说明了先把 GitHub marketplace 加到 Codex，再在 UI 启用（或写入 `~/.codex/config.toml`）。

## Source & Thanks

> Source: https://github.com/zhu1090093659/spec_driven_develop
> License: MIT
> GitHub stars: 715 · forks: 87


---
Source: https://tokrepo.com/en/workflows/spec-driven-develop-spec-first-agent-skill-2026
Author: Skill Factory