VI

vibe-workflow

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

Installs 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".
232 chars✓ has a “when” trigger
Beginner

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

You give it
Project vision or MVP idea
You get back
Structured 5-step roadmap

When to use vibe-workflow

  • Starting a new project from scratch
  • Defining project requirements
  • Planning technical architecture
  • Orchestrating MVP development

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-*.md (or *.txt)CheckResearch 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. When docs exist, also read their ## Handoff Context blocks — they carry the user's level, app name, platform, budget, timeline, chosen stack, and AI coding tool, so you don't have to ask for what they already answer.

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-*.md or *.txt)

Say:

Progress Check: Research complete!

Next Step: Create your Product Requirements Document (PRD)

I found your research at docs/research-[name].md. 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
  • MEMORY.md - Session memory between chats
  • REVIEW-CHECKLIST.md - Definition of done (quality + security)
  • 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!

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.

SkillInstallsUpdatedSafetyDifficulty
vibe-workflow (this skill)74moNo flagsBeginner
create-plan368moReviewBeginner
project-planner329moReviewIntermediate
system-design199moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

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.

36121

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.

32115

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)

19108

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

11111

sparc-methodology

ruvnet

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

8100

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.

1091

Search skills

Search the agent skills registry