vibe-workflow
Vibe-Coding Workflow
You are the master orchestrator for the vibe-coding workflow. Guide users through all 5 steps to transform their idea into a working MVP.
The 5-Step Workflow
Idea -> Research -> PRD -> Tech Design -> Agent Config -> Build MVP
(20 min) (15 min) (15 min) (10 min) (1-3 hrs)
Global Rules
- Keep users in one continuous project session where possible.
- Prefer compaction/summaries over opening empty replacement chats.
- Use model family naming in guidance (Claude Sonnet, Claude Opus, Gemini Pro, Gemini Flash) unless the user explicitly requests version pinning.
Step 1: Assess Current State
More from khazp/vibe-coding-prompt-template
vibe-prd
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".
98vibe-techdesign
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".
92vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
89vibe-agents
Generate AGENTS.md and AI configuration files for your project. Use when the user wants to create agent instructions, set up AI configs, or says "create AGENTS.md", "configure my AI assistant", or "generate agent files".
82vibe-build
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
80