A 5-step workflow to guide developers from initial concept to a functioning MVP.
Install
mkdir -p .claude/skills/vibe-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2352" && unzip -o skill.zip -d .claude/skills/vibe-workflow && rm skill.zipInstalls to .claude/skills/vibe-workflow
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.
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".Key capabilities
- →Guide product research validation
- →Draft requirement specifications (PRD)
- →Plan technical architecture components
- →Generate expert AI agent instructions
- →Sequence MVP development milestones
How it works
Follows a defined sequential workflow to transform conceptual ideas into actionable technical documentation and build steps.
Inputs & outputs
When to use vibe-workflow
- →Starting a new project from scratch
- →Defining project requirements
- →Planning technical architecture
- →Orchestrating MVP development
About this skill
App workflow router
Use the request and existing project state to choose the next useful action. Load only the context needed to identify the outcome, constraints, and current implementation. An existing file does not prove that a stage is complete.
- New product: use research, PRD, and technical design skills selectively. Quick mode needs a clear outcome, constraints, and acceptance journey; deeper planning is useful for unresolved integrations or consequential decisions.
- Existing product: implement the requested change in the current architecture. Use a change skill if available; missing planning documents do not require restarting discovery.
- Broken behavior: reproduce, diagnose, fix, and verify the failure. Use a debugging skill if available, without redoing the new-product interview.
- Instructions or handoff only: produce the requested artifacts and report their limits; do not begin an unrequested implementation or deployment.
Use vibe-agents when creating project instructions, vibe-build for a new
implementation, and an available verification skill for a relevant user journey.
Only invoke skills actually present in the target environment. The five stages
are a useful route, not five approval gates or a mandatory document set for
every edit.
Reuse answered questions and Handoff Context. Ask for missing consequential decisions; otherwise proceed with clearly stated assumptions. Keep stable constraints in AGENTS.md, decisions in product documents, and current progress in MEMORY.md where the project uses it. One builder is sufficient unless independent work and available tools justify delegation.
Complete the scope the user requested, including relevant checks and fixes. When reporting, distinguish actual results from unperformed checks and name any concrete blocker. Do not stop at the first implementation if a working product was requested; do not publish merely because local work is complete.
When not to use it
- →Small feature updates to existing code
- →Tasks without clear project goals
Limitations
- →Time-intensive for full workflow
- →Requires user input for each phase
How it compares
Structures the entire project lifecycle rather than addressing isolated coding tasks.
Compared to similar skills
vibe-workflow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vibe-workflow (this skill) | 7 | 5mo | No flags | Beginner |
| create-plan | 36 | 9mo | Review | Beginner |
| project-planner | 32 | 11mo | Review | Intermediate |
| system-design | 19 | 11mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by KhazP
View all by KhazP →You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
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.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
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).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.