Generates technical design documentation for MVPs based on existing product requirements and user feedback.
Install
mkdir -p .claude/skills/vibe-techdesign && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4082" && unzip -o skill.zip -d .claude/skills/vibe-techdesign && rm skill.zipInstalls to .claude/skills/vibe-techdesign
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".Key capabilities
- →Plan system architecture
- →Choose tech stacks
- →Generate technical design documents
- →Define MVP requirements
How it works
It extracts requirements from a PRD to guide the user through architectural decisions and tech stack selection for an MVP.
Inputs & outputs
When to use vibe-techdesign
- →Create architecture plans for a new app
- →Choose a tech stack for an MVP
- →Generate technical design docs from a PRD
About this skill
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.
When not to use it
- →When the project lacks a defined PRD
Prerequisites
Limitations
- →Requires a PRD file
- →Dependent on user-provided constraints
How it compares
It generates a formal technical design document based on existing requirements rather than ad-hoc planning.
Compared to similar skills
vibe-techdesign side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vibe-techdesign (this skill) | 1 | 5mo | No flags | Advanced |
| project-planner | 32 | 11mo | Review | Intermediate |
| spec-kit-workflow | 11 | 10mo | No flags | Intermediate |
| specification-architect | 13 | 10mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by KhazP
View all by KhazP →You might also like
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
architecture
davila7
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
context-driven-development
wshobson
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context