Individual skill
wu5-dev-flow
用简短的项目文档和小步验证,指导软件项目从想法、调研、PRD、技术设计到开发、质量检查、发布和反馈迭代。用于启动项目、继续开发、修复或重构,以及准备交付;按当前任务进入阶段,沿用项目技术栈。
wu5-dev-flow/SKILL.md
Source commit 960d47b2165e1219e3ad8af0cac1177e8c4fa208
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- Yes
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 17
- Repository last updated
- Oct 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- codex Repository topic
- git-workflow Repository topic
- python Repository topic
- sdd Repository topic
- tdd Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,837 bytesagents/openai.yamlasset · 335 bytesreferences/00-environment.mddoc · 1,644 bytesreferences/01-research.mddoc · 2,289 bytesreferences/02-prd.mddoc · 2,305 bytesreferences/03-tech-design.mddoc · 2,485 bytesreferences/04-context.mddoc · 2,826 bytesreferences/05-build.mddoc · 2,348 bytesreferences/06-quality.mddoc · 2,256 bytesreferences/07-ship.mddoc · 2,309 bytesreferences/08-launch.mddoc · 2,183 bytesreferences/09-iterate.mddoc · 2,237 bytesreferences/SOURCES.mddoc · 4,312 bytes
Read excerpt
# Wu5 Dev Flow
先明确要解决的问题,再交付一个可验证的小结果。流程服务于开发,每次只推进当前需要的阶段。
## 阶段门禁
一个回合只推进当前一个阶段。判断当前阶段,只读该阶段参考,只产出该阶段的文档或代码,在交接点停下汇报。
- 不连跳。想着手新项目就从 00 或 01 开始;不把调研、PRD、TechDesign 写完再一起汇报。
- 一个回合内写多份阶段文档同样是越界。多份文档的“一次性”交付不是完成,是把用户从流程里挤出去。
- 阶段完成条件只是停止条件,不是继续前进的信号。停下时说明本阶段产出(路径)、真实依据与不确定项,再用一句话问是否进入下一阶段。
- 除非用户授权,否则不连跳阶段。用户只是在描述完整目标、没有回应上一阶段时不算授权;粗略或过去会话的授权也不顶用,要说清本次连续走哪些阶段并由用户同意。
- 用户提前回答后续阶段的问题时,记为当前阶段的未知项或待办,不因此跳阶段。
- 单个缺陷、小修改或重构是单阶段任务,直接进入 05 做完验证与提交,不套用逐阶段流程。