-
Notifications
You must be signed in to change notification settings - Fork 95
Installation
Spec-Driven Develop is distributed as Markdown skills plus optional plugin metadata for Claude Code and Codex. The core workflow has no runtime dependency, SDK, API key, or build step.
Use the Claude Code plugin marketplace:
/plugin marketplace add zhu1090093659/spec_driven_develop
/plugin install spec-driven-develop@spec-driven-develop
After installation, reload plugins:
/reload-plugins
Claude Code also gets optional slash commands and sub-agent prompts:
-
/spec-devstarts the Spec-Driven Develop workflow. -
/dpstarts the Deep Discuss workflow. -
project-analyzer,task-architect, andtask-executorsupport large workflow runs when sub-agents are available.
Install the Codex plugin marketplace from GitHub:
codex plugin marketplace add zhu1090093659/spec_driven_develop --ref mainThen enable Spec-Driven Develop in the Codex plugin UI.
If your Codex client does not expose plugin UI yet, add this to ~/.codex/config.toml:
[plugins."spec-driven-develop@spec-driven-develop"]
enabled = trueYou can also install only the core skill from inside a Codex session:
$skill-installer install https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/spec-driven-develop
Or use the shell installer:
bash <(curl -sL https://raw.githubusercontent.com/zhu1090093659/spec_driven_develop/main/scripts/install-codex.sh)Use the Cursor install script:
bash <(curl -sL https://raw.githubusercontent.com/zhu1090093659/spec_driven_develop/main/scripts/install-cursor.sh)Or clone the repository and run the script locally:
git clone https://github.com/zhu1090093659/spec_driven_develop.git
bash spec_driven_develop/scripts/install-cursor.shAny agent that can read custom Markdown instructions can use the core workflow.
Download the main skill:
curl -sL https://raw.githubusercontent.com/zhu1090093659/spec_driven_develop/main/plugins/spec-driven-develop/skills/spec-driven-develop/SKILL.md -o SKILL.mdFor the complete workflow, also copy the references/ directory from:
plugins/spec-driven-develop/skills/spec-driven-develop/references/
Common placement options:
| Agent | Where to Put It |
|---|---|
| Windsurf |
.windsurf/skills/ or project rules |
| Cline |
.cline/skills/ or custom instructions |
| Aider | Reference in .aider.conf.yml or paste into chat |
| Continue |
.continue/ configuration or system prompt |
| Other agents | Any custom instruction, skill, memory, or system prompt surface |
After cloning:
git clone https://github.com/zhu1090093659/spec_driven_develop.git
cd spec_driven_develop
bash scripts/install-all.shAfter installation, ask your agent one of these:
Use spec-driven development to plan this migration.
Help me analyze this technical problem deeply.
If installed correctly, the agent should either trigger Spec-Driven Develop for large transformation work or Deep Discuss for structured problem analysis.