Practical overview
When it fits
Use it when a software change needs more structure than a single coding prompt can provide, or when discussion and code review should follow repeatable workflows.
Who it is for
- Developers using AI coding agents for migrations, rewrites, refactors, or architecture changes.
- Teams that want staged development work tracked through GitHub Issues and pull requests.
- Developers who want structured technical discussion or findings-first review workflows alongside implementation planning.
Documented uses
- Analyze a project and turn a large change into phased, actionable tasks.
- Clarify scope, priorities, and constraints before implementation.
- Track development progress locally or through GitHub Issues, milestones, and pull requests.
- Resume work after an interrupted session using a persistent progress index.
- Structure technical discussion or review changes for bugs and regressions.
Requirements & limits
The repository presents the project as open source under the MIT license.
- The workflows are Markdown-based and target agents that read custom skills; the README names Claude Code, Codex, OpenCode, and Cursor.
- The repository describes both local progress tracking and GitHub-based tracking, with GitHub Issues and pull requests used in GitHub modes.
- The main workflow asks for plan confirmation before execution and treats sub-agent delegation or parallel lanes as conditional choices.
- The repository says there is no SDK or third-party runtime dependency, while including small helper scripts.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install the Spec-Driven Develop plugin for Claude Code
Add the plugin through its marketplace and reload Claude Code to activate it.
Before you start
- Claude Code
Steps
Add the marketplace with
/plugin marketplace add zhu1090093659/spec_driven_develop.Install the plugin with
/plugin install spec-driven-develop@spec-driven-develop.Run
/reload-pluginsto activate it.
Expected outcome
The Spec-Driven Develop plugin is installed and activated in Claude Code.
Guide limitations
- These steps cover Claude Code installation and activation; they do not describe a development task workflow.
Resume an interrupted workflow from its progress file
Restore workflow context in a new session using the persistent progress index.
Before you start
- A previous workflow session has created
docs/progress/MASTER.md.
Steps
Start a new session with the agent.
Have the agent read
docs/progress/MASTER.mdto restore context.Continue from the point recorded in the progress file.
Expected outcome
The agent can resume the workflow using the saved progress context.
Guide limitations
- The documented resume procedure does not specify how to recover if the progress file is absent or incomplete.
- In GitHub modes, the agent also queries current GitHub Issue states; this behavior is specific to those modes.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Spec Driven Develop | Analyze a project and turn a large change into phased, actionable tasks. | CLI | The repository presents the project as open source under the MIT license. |
| Cclsp | Find where a symbol is defined. | CLI | The public GitHub repository displays an MIT license. The documented setup uses the CLI and requires Node.js 18+ or Bun. |
| Roam | Find a symbol and inspect its callers, callees or indexed dependents. | CLI, Self-hosted | Roam is described as open source under Apache 2.0, with free open-source functionality and paid services. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 November 2026
- Original website title
- zhu1090093659/spec_driven_develop · Official homepage title · retained in its source language