vibe-workflow
GitHubApp工作流路由器，根据项目状态（新建、现有或故障）智能选择规划、实现或调试策略。协调研究、设计、构建及验证技能，确保按正确阶段推进任务，避免不必要的重复工作，提升开发流程效率与规范性。
Trigger Scenarios
Install
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-workflow -g -y
SKILL.md
Frontmatter
{
"name": "vibe-workflow",
"description": "Select the appropriate planning, implementation, or debugging workflow for an app project.",
"allowed-tools": "Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion"
}
App workflow router
Use the request and existing project state to choose the next useful action. Load only the context needed to identify the outcome, constraints, and current implementation. An existing file does not prove that a stage is complete.
- New product: use research, PRD, and technical design skills selectively. Quick mode needs a clear outcome, constraints, and acceptance journey; deeper planning is useful for unresolved integrations or consequential decisions.
- Existing product: implement the requested change in the current architecture. Use a change skill if available; missing planning documents do not require restarting discovery.
- Broken behavior: reproduce, diagnose, fix, and verify the failure. Use a debugging skill if available, without redoing the new-product interview.
- Instructions or handoff only: produce the requested artifacts and report their limits; do not begin an unrequested implementation or deployment.
Use vibe-agents when creating project instructions, vibe-build for a new
implementation, and an available verification skill for a relevant user journey.
Only invoke skills actually present in the target environment. The five stages
are a useful route, not five approval gates or a mandatory document set for
every edit.
Reuse answered questions and Handoff Context. Ask for missing consequential decisions; otherwise proceed with clearly stated assumptions. Keep stable constraints in AGENTS.md, decisions in product documents, and current progress in MEMORY.md where the project uses it. One builder is sufficient unless independent work and available tools justify delegation.
Complete the scope the user requested, including relevant checks and fixes. When reporting, distinguish actual results from unperformed checks and name any concrete blocker. Do not stop at the first implementation if a working product was requested; do not publish merely because local work is complete.
Version History
-
db48176
Current 2026-09-22 04:50
重构工作流逻辑，精简代理技能引用，优化内部结构与依赖关系。
-
b00eb84
2026-09-08 23:13
版本0.3.0：新增基于情境的路由机制（新建/延续/修复）、按比例规划及变更/调试技能；增强CLI参数解析、Windows路径处理及安装流程；完善测试与文档。
-
254bae5
2026-08-27 13:02
优化访谈规则以支持批量回答和跳过已回答问题，避免重复提问；恢复被合并丢弃的安全检查清单（依赖审计、输入验证等）。
-
06d0796
2026-07-19 18:25
v3.0.0：引入统一AGENTS.md模板，实现文档间Handoff Context自动传递以消除重复询问；新增Claude Code、Codex等工具适配；重构部分章节并优化提示词质量。
- e063721 2026-07-05 14:58
