spec-driven
v5.3.3Spec-driven development workflow with structured requirements, design, tasks, and autonomous execution.
By habib0xLicense: MIT1.1k GitHub starsUpdated 12 hours ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 23, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install spec-driven for Codex
codex plugin marketplace add hashgraph-online/awesome-codex-plugins
codex plugin marketplace upgrade awesome-codex-plugins
codex plugin add spec-driven@awesome-codex-pluginsPaste and run these commands in a terminal with Codex. They add and refresh the awesome-codex-plugins catalog, then install this plugin.
Compatibility: the page URL and API slug “spec-driven” remain stable.
- Codex:
spec-driven@agent-plugin-marketplace→spec-driven@awesome-codex-plugins
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/hashgraph-online/awesome-codex-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/Habib0x0/spec-driven-plugin/.
Plugin files
├── .codex-plugin/plugin.json└── skills/spec-workflow/SKILL.md
Included Skills1
This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase", "design phase", or "tasks phase". Provides structured 3-phase workflow for feature development.
Plugin manifests1
{
"name": "spec-driven",
"version": "5.3.3",
"description": "Spec-driven development workflow with structured requirements, design, tasks, and autonomous execution.",
"author": {
"name": "habib0x",
"url": "https://github.com/Habib0x0"
},
"homepage": "https://github.com/Habib0x0/spec-driven-plugin",
"repository": "https://github.com/Habib0x0/spec-driven-plugin",
"license": "MIT",
"keywords": [
"specs",
"requirements",
"design",
"planning",
"workflow",
"EARS",
"codex"
],
"skills": "./skills/",
"interface": {
"displayName": "Spec Driven",
"composerIcon": "./assets/spec-driven-icon.svg",
"shortDescription": "Turn feature ideas into requirements, design docs, tasks, and execution loops.",
"longDescription": "A structured spec-driven development workflow for Codex. It guides features through brainstorming, EARS requirements, technical design, task breakdown, validation, execution, and post-completion review.",
"developerName": "habib0x",
"category": "Development",
"capabilities": [
"Interactive",
"Write"
],
"websiteURL": "https://github.com/Habib0x0/spec-driven-plugin",
"privacyPolicyURL": "https://github.com/Habib0x0/spec-driven-plugin/blob/main/PRIVACY.md",
"termsOfServiceURL": "https://github.com/Habib0x0/spec-driven-plugin/blob/main/LICENSE",
"defaultPrompt": [
"$spec create a spec for this feature.",
"$spec-loop run the implementation loop.",
"$spec-exec run one implementation iteration.",
"$spec-status check spec progress.",
"$spec-validate validate the current spec.",
"$spec-brainstorm explore this idea before formalizing.",
"$spec-bugfix analyze this bug and plan a fix.",
"$spec-refine update requirements or design."
],
"brandColor": "#0F766E"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[spec-driven on Agent Plugins Marketplace](https://pluginsmp.com/plugins/spec-driven)