spec-driven-develop
Automates pre-development workflow for large-scale complex tasks. Use when the user mentions "rewrite", "migrate", "overhaul", "refactor entire project", "transform", "rebuild in [language]", "spec-driven", or describes any large-scale project transformation that requires planning before coding. Also triggers on Chinese keywords: "改造", "重写", "迁移", "重构", "大规模", "规范驱动". Performs full project analysis, task decomposition, documentation generation, project-level instruction and native memory surface resolution, progress tracking setup, and then executes the plan within the same session. Keeps Issu
Profile →npx skills add zhu1090093659/spec_driven_develop --skill spec-driven-develop --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Spec-Driven Develop You are executing the **Spec-Driven Development** workflow — a seven-phase pipeline (Phases 0-6) for large-scale complex tasks. Complete preparation phases (analysis, planning, progress setup), then execute the plan — all within a single session. **Behavioral rules**: `references/behavioral-rules.md` — read and follow them in every phase; they are non-negotiable. ## Configuration | Path | Default Value | Purpose | |:-----|:--------------|:--------| | Analysis output | `docs/analysis/` | Phase 1 analysis documents | | Plan output | `docs/plan/` | Phase 3 planning documents | | Progress output | `docs/progress/` | Phase 4 tracking documents (incl. MASTER.md) | | Instruction surfaces | Resolved per project | Project-level constraints for agents (see Phase 4) | | Memory surface | Native first | Durable facts via the agent's native memory when available; repo fallback only when explicitly selected | | Archive output | `docs/archives/<project>/` | Phase 6 archived artifacts | | Task tracking mode | Auto-detect | `GITHUB_FULL`, `GITHUB_STANDARD`, or `LOCAL_ONLY` | | Delivery batching | Phase-first | Issues track tasks; PRs integrate coherent task batches | | Adaptive
- Configuration
- Before You Begin: Cross-Conversation Continuity Check
- Phase 0: Quick Intent Capture
- Phase 1: Deep Project Analysis
- Phase 2: Intent Refinement & Confirmation
- Phase 3: Task Decomposition
- Phase 4: Progress Tracking Documentation
- Project Governance Surface (all modes)
- In GITHUBFULL or GITHUBSTANDARD mode:
- In LOCALONLY mode:
- Common to all modes:
- Phase 5: Confirm & Execute
- 5a. Summary & Confirmation
- 5b. Execution
What does the spec-driven-develop skill do?
Automates pre-development workflow for large-scale complex tasks. Use when the user mentions "rewrite", "migrate", "overhaul", "refactor entire project", "transform", "rebuild in [language]", "spec-driven", or describes any large-scale project transformation that requires planning before coding. Also triggers on Chinese keywords: "改造", "重写", "迁移", "重构", "大规模", "规范驱动". Performs full project analysis, task decomposition, documentation generation, project-level instruction and native memory surface resolution, progress tracking setup, and then executes the plan within the same session. Keeps Issu
How do I install it?
Run `npx skills add zhu1090093659/spec_driven_develop --skill spec-driven-develop --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From zhu1090093659/spec_driven_develop, a repository with 958 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.