spec-driven-develop
byzhu1090093659· 18 skills
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 Issues as task-tracking units while batching related implementation into coherent reviewable PRs.
How to install spec-driven-develop?
zhu1090093659/spec_driven_develop/spec-driven-develop
$npx -y skills add zhu1090093659/spec_driven_develop --skill spec-driven-developInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/zhu1090093659/spec_driven_develop" --skill "zhu1090093659/spec_driven_develop/spec-driven-develop"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/zhu1090093659/spec_driven_develop" that are relevant to the current task. Run `npx skills add "https://github.com/zhu1090093659/spec_driven_develop"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
