vibe-workflow
Skill1 starsChanged 8 months agoMITView on GitHub
Complete 5-step workflow to build an MVP from idea to launch. Use when the user wants to start a new project from scratch, go through the full workflow, or says "help me build an MVP", "start new project", or "vibe coding workflow".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- sz-xiaohuolong/vibe-workflowtheir own version, first seen Nov 15, 2026
- enigmalibs/ClaudeSkillstheir own version, first seen Nov 1, 2026
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- KhazP/vibe-coding-prompt-template★ 3.1ksame name
- sz-xiaohuolong/vibe-workflow★ 4same name
- enigmalibs/ClaudeSkills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- vibe-agentsSkill
- vibe-buildSkill
- vibe-prdSkill
- vibe-researchSkill
- vibe-techdesignSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Keep users in one continuous project session where possible.
- Distinctive: line 20
Prefer compaction/summaries over opening empty replacement chats.
- Distinctive: line 21
Use model family naming in guidance (Claude Sonnet, Claude Opus, Gemini Pro, Gemini Flash) unless the user explicitly requests version …
- Distinctive: line 129
Keep track of progress. After each major step:
- Distinctive: line 140
If user wants to skip a step:
- Distinctive: line 163
When MVP is deployed:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
First, check what already exists in the project:
| File | Status | What It Means |
docs/research-*.txt | Check | Research complete |
docs/PRD-*.md | Check | Requirements defined |
docs/TechDesign-*.md | Check | Architecture planned |
AGENTS.md | Check | Ready to build |
src/ or app/ | Check | Building started |
Based on findings, identify where the user is in the workflow.
Step 2: Guide to Next Step
If Starting Fresh (No files)
Say:
Welcome to the Vibe-Coding Workflow!
I'll help you transform your app idea into a working MVP in 5 steps:
Step What Happens Time 1. Research Validate idea & market 20 min 2. PRD Define what to build 15 min 3. Tech Design Plan how to build 15 min 4. Agent Config Generate AI instructions 10 min 5. Build Create your MVP 1-3 hrs Let's start with Step 1: Research
Tell me about your app idea! What problem does it solve?
Then guide them through the research phase (see vibe-research skill).
If Research Exists (has research-*.txt)
Say:
Progress Check: Research complete!
Next Step: Create your Product Requirements Document (PRD)
I found your research at
docs/research-[name].txt. I'll use this to inform your PRD.Ready to define your product requirements?
Then guide through PRD creation.
If PRD Exists (has PRD-*.md)
Say:
Progress Check: Research and PRD complete!
Next Step: Create your Technical Design
I'll help you decide:
- What tech stack to use
- How to structure the project
- Which tools are best for your skill level
Ready to plan the technical architecture?
Then guide through Tech Design.
If Tech Design Exists (has TechDesign-*.md)
Say:
Progress Check: Research, PRD, and Tech Design complete!
Next Step: Generate AI agent configuration files
I'll create:
AGENTS.md- Master build planagent_docs/- Detailed specifications- Tool configs based on your choices
Which AI tools will you use to build?
Then guide through Agent Config.
If AGENTS.md Exists
Say:
Progress Check: All planning complete! Ready to build!
Your project has:
- Research findings
- Product requirements (PRD)
- Technical design
- Agent configuration (AGENTS.md)
Let's build your MVP!
I'll follow the plan in AGENTS.md:
- Set up the project foundation
- Build core features one by one
- Polish and prepare for launch
Shall I start with Phase 1: Foundation?
Then execute the build.
Workflow State Tracking
Keep track of progress. After each major step:
Workflow Progress:
- Step 1: Research
- Step 2: PRD
- Step 3: Tech Design <- You are here
- Step 4: Agent Config
- Step 5: Build MVP
Handling Interruptions
If user wants to skip a step:
I recommend completing [step] before moving to [next step] because:
- [Reason 1]
- [Reason 2]
However, if you want to proceed anyway, I can work with what we have. Your choice?
Quick Commands
Remind users they can jump to specific steps:
| Command | What It Does |
/vibe-research | Run market research |
/vibe-prd | Create PRD |
/vibe-techdesign | Plan architecture |
/vibe-agents | Generate configs |
/vibe-build | Start building |
/vibe-workflow | Check progress |
Completion
When MVP is deployed:
Congratulations! Your MVP is live!
Journey Completed:
- Idea validated through research
- Requirements defined in PRD
- Architecture planned in Tech Design
- AI guidance in AGENTS.md
- MVP built and deployed
What's Next:
- Share with 5-10 beta users
- Collect feedback (use a simple form)
- Identify top 3 improvements
- Plan v2 features
Remember: The best time to build was yesterday. The second best time is now. You did it!
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

