Get the FREE Ultimate OpenClaw Setup Guide →

vibe-workflow

Scanned
npx machina-cli add skill KhazP/vibe-coding-prompt-template/vibe-workflow --openclaw
Files (1)
SKILL.md
4.5 KB

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)

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!

Source

git clone https://github.com/KhazP/vibe-coding-prompt-template/blob/main/.claude/skills/vibe-workflow/SKILL.mdView on GitHub

Overview

Vibe-workflow acts as the master orchestrator for the five-step MVP process, guiding you from idea to launch. It assesses current state, then steers you through Research, PRD, Tech Design, and Agent Config, culminating in building your MVP. It tracks progress and provides quick commands to jump between steps.

How This Skill Works

It inventories the project by checking for docs/research-*.txt, docs/PRD-*.md, docs/TechDesign-*.md, AGENTS.md, and src/. Based on what exists, it guides you through Step 1 to Step 5, prompting for research, PRD, tech design, and agent config, then triggers the MVP build. It updates workflow progress after each major milestone and supports quick jump commands.

When to Use It

  • Starting a new project from scratch and starting the full 5-step MVP workflow
  • Going through the full idea-to-launch MVP process
  • Saying help me build an MVP
  • Saying start new project
  • Saying vibe coding workflow

Quick Start

  1. Step 1: Assess Current State by inspecting docs/research-*.txt, PRD-*.md, TechDesign, AGENTS.md, and src/
  2. Step 2: If starting fresh, present the Welcome message and start with Step 1: Research
  3. Step 3: Progress through PRD, Tech Design, Agent Config, then Build MVP, updating AGENTS.md as you go

Best Practices

  • Begin with Step 1: Assess Current State to map existing docs and project structure
  • Keep PRD and Tech Design up to date as you progress through steps
  • Treat AGENTS.md as the master build plan and reference it during Build MVP
  • Use the quick commands to jump between steps: /vibe-research, /vibe-prd, /vibe-techdesign
  • Pause to confirm before skipping a step and document the rationale

Example Use Cases

  • Starting a brand-new app MVP from scratch and kickoff with Step 1: Research
  • Resuming an existing project by confirming docs/research-*.txt and PRD-*.md
  • Generating Tech Design and AGENTS.md to define architecture and build plan
  • Creating agent_configs and tool configurations for AI-assisted development
  • Building and launching the MVP within the stated Build phase

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers