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:51
重构工作流以精简代理技能和参考资料
- b00eb84 2026-09-08 23:14
- 254bae5 2026-08-27 13:02
