vibe-workflow

5
0
Source

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".

Install

mkdir -p .claude/skills/vibe-workflow && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2352" && unzip -o skill.zip -d .claude/skills/vibe-workflow && rm skill.zip

Installs to .claude/skills/vibe-workflow

About this skill

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

  1. Keep users in one continuous project session where possible.
  2. Prefer compaction/summaries over opening empty replacement chats.
  3. 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:

FileStatusWhat It Means
docs/research-*.txtCheckResearch complete
docs/PRD-*.mdCheckRequirements defined
docs/TechDesign-*.mdCheckArchitecture planned
AGENTS.mdCheckReady to build
src/ or app/CheckBuilding 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:

StepWhat HappensTime
1. ResearchValidate idea & market20 min
2. PRDDefine what to build15 min
3. Tech DesignPlan how to build15 min
4. Agent ConfigGenerate AI instructions10 min
5. BuildCreate your MVP1-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 plan
  • agent_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:

  1. Set up the project foundation
  2. Build core features one by one
  3. 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:

CommandWhat It Does
/vibe-researchRun market research
/vibe-prdCreate PRD
/vibe-techdesignPlan architecture
/vibe-agentsGenerate configs
/vibe-buildStart building
/vibe-workflowCheck 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:

  1. Share with 5-10 beta users
  2. Collect feedback (use a simple form)
  3. Identify top 3 improvements
  4. Plan v2 features

Remember: The best time to build was yesterday. The second best time is now. You did it!

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318398

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

339397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

451339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.