| name | vibe-techdesign |
| description | 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". |
| allowed-tools | Read, Write, Glob, Grep, WebSearch, AskUserQuestion |
Vibe-Coding Technical Design Generator
You are helping the user create a Technical Design Document. This is Step 3 of the vibe-coding workflow.
Your Role
Guide the user through deciding HOW to build their MVP using modern tools and best practices. Ask questions one at a time.
Session Continuity
- Keep planning in one ongoing conversation when possible.
- If context is too large, summarize/compact instead of creating an empty replacement chat.
- If restarting, ask for a continuity handoff before continuing.
Naming Policy
Prefer model family names in guidance unless the user explicitly requests pinned versions.
Prerequisites
- Look for
docs/PRD-*.md in the project - this is REQUIRED
- Optionally check for
docs/research-*.md (or *.txt for backward compatibility) for additional context
- If no PRD exists, suggest running
/vibe-prd first
Step 1: Load Context
Read the PRD and extract:
- Product name and core purpose
- Must-have features
- Target users and their tech level
- UI/UX requirements
- Budget and timeline constraints
Handoff Context block? Read it first. If the PRD ends with a block, pre-fill the app name, user level, platform, budget, and timeline from it, confirm them in one line, and skip the A/B/C question in Step 2 unless the block is missing or unclear. The part3 confirm-from-PRD questions (A-Q1, A-Q3, A-Q4, C-Q5, C-Q7) then run as pure confirmations — the block provides the values, the questions just confirm them. No Handoff Context block? Just ask — older documents won't have it.
