Individual skill

vibe-workflow

Select the appropriate planning, implementation, or debugging workflow for an app project.

templates/.claude/skills/vibe-workflow/SKILL.md

Read pinned source

Source commit d26fb0d8a9cdac94cf99f004087620487e4da33d

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 3,227
Repository last updated: Oct 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
ai-workflow Repository topic
beginner-friendly Repository topic
mvp-development Repository topic
technical-design Repository topic
vibe-coding Repository topic
llm-tools Repository topic
workflow-automation Repository topic
claude-code Repository topic
chatgpt Repository topic
operations Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,176 bytes

Read excerpt


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