vibe-techdesign
GitHub根据需求编写MVP技术设计文档，明确架构边界、数据归属及部署目标。分析技术选型权衡与风险，区分测试与生产环境，输出结构化设计并衔接后续工作流，避免过度设计。
Trigger Scenarios
Install
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -g -y
SKILL.md
Frontmatter
{
"name": "vibe-techdesign",
"description": "Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs.",
"allowed-tools": "Read, Write, Glob, Grep, WebSearch, AskUserQuestion"
}
MVP technical design
Read the agreed requirements and reuse Handoff Context. Inspect an existing project's stack and relevant implementation before proposing replacements. Ask only for consequential choices that remain unresolved; a known answer does not need another confirmation echo.
Describe the architecture needed for the core journey: component/service boundaries, data ownership, integration contracts, deployment target, and relevant failure behavior. Prefer the smallest design that meets requirements. Add auth, storage, infrastructure, AI, or paid services only when justified. Verify changing vendor details from the installed code or official sources.
Record meaningful tradeoffs, compatibility constraints, migration/recovery requirements where applicable, and how the result will be checked. Distinguish local test operations from external sends, production writes, and deployments. Keep secrets out of generated documents. Do not assign broad tool permissions or require a team of agents to execute an ordinary implementation.
Use the manifest's configured design path or docs/TechDesign-[AppName]-MVP.md.
Quick mode can be a short architecture and implementation plan; deeper modes
should expand only where uncertainty or risk warrants it. End with Handoff
Context carrying app, known user level, platform, budget, timeline, mode,
constraints, decisions, source files, and open questions. Continue to the next
authorized workflow stage rather than stopping solely because a document exists.
For a guided interview with unresolved requirements, consult the relevant optional question prompts.
When producing a document for vibeworkflow, include the exact
CLI output metadata. This is a parser contract,
not an optional prose template.
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
修复面试规则以支持批量回答；恢复安全清单缺失内容；合并主分支更新Handoff Context逻辑。
-
06d0796
2026-07-19 18:25
v3.0.0重构：引入Handoff Context块实现阶段间无缝衔接，避免重复提问；精简part3内容；优化Claude Code配置及工具矩阵。
- e063721 2026-07-05 14:58
