New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vibe Workflow Router

by KhazP in KhazP/vibe-coding-prompt-template

Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

MITAuto-check: notesAgent Workflows

Install Vibe Workflow Router

skills CLI
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install KhazP/vibe-coding-prompt-template vibe-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibe-workflow .claude/skills/vibe-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-workflow
GitHub stars
3.1k
Token cost
~544 tokens
SKILL.md length
277 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

  • Starting an app project and unsure whether to plan, build or debug first
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Adding a change to an existing product without redoing discovery
  • Fixing broken behavior without running a new-product interview

What it does

Instead of following a fixed pipeline, this router reads your request and the current project state and chooses among four paths. A new product gets research, PRD and technical design skills used selectively, with a quick mode that only needs a clear outcome, constraints and an acceptance journey. An existing product gets the change made inside its current architecture, and missing planning documents do not force discovery to restart. Broken behavior is reproduced, diagnosed, fixed and verified. A request for instructions or a handoff produces only those artifacts.

It hands off to sibling skills such as `vibe-agents` for project instructions and `vibe-build` for a new implementation, but only if they exist in your environment. The five stages are a route, not approval gates. Answered questions and Handoff Context are reused, missing consequential decisions are asked about, and other gaps become stated assumptions. Stable constraints belong in AGENTS.md, decisions in product documents and current progress in MEMORY.md. Reports must separate real results from checks that were not run, and nothing is published just because local work is done.

When your agent uses it

  • Starting an app project and unsure whether to plan, build or debug first
  • Adding a change to an existing product without redoing discovery
  • Fixing broken behavior without running a new-product interview
  • Producing only project instructions or a handoff document

Example prompts

  • “I have an idea for a habit tracker app; work out the next step and take it.”
  • “Add a dark mode toggle to the existing app without restarting the planning docs.”
  • “The login form submits twice; reproduce it, fix it and verify the fix.”
  • “Write the AGENTS.md and handoff notes for this project, but do not start building.”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

What it can do on your machine

Read from SKILL.md and the folder at commit d26fb0d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Workflow Router loads about 544 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 277 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~544

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from KhazP/vibe-coding-prompt-template at commit d26fb0d, republished under its MIT licence (© KhazP). 277 words, ~544 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-workflow/SKILL.md (or your agent's skills folder).
name
vibe-workflow
description
Select the appropriate planning, implementation, or debugging workflow for an app project.
allowed-tools
Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

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.

© KhazP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/vibe-workflow of KhazP/vibe-coding-prompt-template.

Open the folder on GitHubat commit d26fb0d

Compare with similar skills

Vibe Workflow Router next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Workflow Router compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Workflow Router this skillKhazP/vibe-coding-prompt-template3.1k—~544Automated safety check: NotesMIT
Implementation Plan Writerimbue-ai/bouncer400—~2.1kAutomated safety check: PassAGPL-3.0
Vertical-Slice Task Plannerowainlewis/blueprint412—~1.5kAutomated safety check: PassMIT
Conductor Track Managementwshobson/agents40k9 repos~420Automated safety check: PassMIT
Technical Plan WriterEveryInc/compound-engineering-plugin25k—~1.9kAutomated safety check: PassMIT
Speckit Tasksforyourhealth111-pixel/Vibe-Skills3.6k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Implementation Plan Writer

    imbue-ai/bouncer

    Turns a feature's goals, requirements and architecture documents into a set of self-contained task files that a developer with no project context can follow.

    400 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Vertical-Slice Task Planner

    owainlewis/blueprint

    Breaks a reviewed spec into ordered, vertical-slice tasks that each fit one agent run and one pull request, grouped into milestones when useful.

    412 GitHub stars~1.5k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Conductor Track Management

    wshobson/agents

    Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md…

    40k GitHub starsUsed in 9 repos~420 tokens
    DevelopmentAuto-check passed

  • Technical Plan Writer

    EveryInc/compound-engineering-plugin

    Writes a structured plan for multi-step software or non-software work after research, without writing production code, and pairs with ce-brainstorm and ce-work.

    25k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Speckit Tasks

    foryourhealth111-pixel/Vibe-Skills

    Break down implementation plans into actionable task lists. An agent skill from foryourhealth111-pixel/Vibe-Skills.

    3.6k GitHub stars~1.6k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed

More from KhazP/vibe-coding-prompt-template

All 11 skills in this repo

  • MVP Product Requirements Writer

    KhazP/vibe-coding-prompt-template

    Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.

    3.1k GitHub stars~455 tokensUpdated 4 days ago
    Auto-check passed

  • Vibe Research

    KhazP/vibe-coding-prompt-template

    Researches an app idea or settles product and technical uncertainties before a design is fixed, and saves the findings with a handoff for the next stage.

    3.1k GitHub stars~473 tokensUpdated 4 days ago
    Auto-check passed

  • MVP Technical Design

    KhazP/vibe-coding-prompt-template

    Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.

    3.1k GitHub stars~512 tokensUpdated 4 days ago
    Auto-check passed

  • Vibe Debug

    KhazP/vibe-coding-prompt-template

    A short debugging procedure for an existing project: reproduce the failure, test one hypothesis at a time, make the smallest fix, add a regression check and re-verify.

    3.1k GitHub stars~403 tokensUpdated 4 days ago
    Auto-check: notes

  • Vibe Agents Instructions

    KhazP/vibe-coding-prompt-template

    Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.

    3.1k GitHub stars~421 tokensUpdated 4 days ago
    Auto-check: notes

  • Build a New-Project Slice

    KhazP/vibe-coding-prompt-template

    Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.

    3.1k GitHub stars~353 tokensUpdated 4 days ago
    Auto-check: notes

Categories

Questions about Vibe Workflow Router

What does Vibe Workflow Router do?

Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed. Instead of following a fixed pipeline, this router reads your request and the current project state and chooses among four paths. A new product gets research, PRD and technical design skills used selectively, with a quick mode that only needs a clear outcome, constraints and an acceptance journey.

When should I use Vibe Workflow Router?

Vibe Workflow Router fits situations like: starting an app project and unsure whether to plan, build or debug first; adding a change to an existing product without redoing discovery; fixing broken behavior without running a new-product interview; producing only project instructions or a handoff document.

How do I install Vibe Workflow Router in Claude Code?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-workflow -a claude-code`. Or copy the skill folder (.agents/skills/vibe-workflow in KhazP/vibe-coding-prompt-template) into .claude/skills/vibe-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Workflow Router in Codex?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-workflow -a codex`. Or copy the skill folder (.agents/skills/vibe-workflow in KhazP/vibe-coding-prompt-template) into .agents/skills/vibe-workflow in your project. Codex loads it when a task matches its description.

Can I use Vibe Workflow Router in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-workflow, .gemini/skills/vibe-workflow, .github/skills/vibe-workflow and .opencode/skills/vibe-workflow in your project.

What does Vibe Workflow Router need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Workflow Router is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion.

Does Vibe Workflow Router access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Workflow Router safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vibe Workflow Router use?

Vibe Workflow Router is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Workflow Router use?

About 544 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Workflow Router?

Skills that share tags, products or a category with Vibe Workflow Router: Implementation Plan Writer (imbue-ai/bouncer, 400 stars), Vertical-Slice Task Planner (owainlewis/blueprint, 412 stars), Conductor Track Management (wshobson/agents, 40k stars) and Technical Plan Writer (EveryInc/compound-engineering-plugin, 25k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Workflow Router?

KhazP (a GitHub user) maintains it in KhazP/vibe-coding-prompt-template, which has 3,130 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.

Source: KhazP/vibe-coding-prompt-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.