mcpField
V
vibe-workflow

vibe-workflow

github.com/khazpAgent workflows3.2k215 installsUpdated 3w ago
Repository

About vibe-workflow

vibe-workflow is a skill that routes app-development requests to an appropriate next action based on the request and project state. It distinguishes new products, existing-product changes, bugs, and handoff-only tasks without requiring every project to follow the same stages.

Key features

  1. 01Routes work by request and project state
  2. 02Handles new and existing products
  3. 03Guidance for reproducing and fixing bugs
  4. 04Uses only available skills
  5. 05Separates completed work from unchecked results

Use cases

  1. 01Choosing a next step for a new product
  2. 02Making a change in an existing architecture
  3. 03Diagnosing a reported failure
  4. 04Preparing requested handoff artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-workflow

After installing, type/vibe-workflowin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported