vibe-coding

Classify and route user instructions to appropriate vibe-coding workflow phases.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-coding-adhi-jp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-coding
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-coding
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-coding-adhi-jp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify and route user instructions to the appropriate downstream phase of a vibe-coding workflow. It centralizes routing logic to coordinate multiple specialist skills while preserving phase boundaries and governance.

Core Features & Use Cases

  • Route user instructions to the appropriate specialist phase based on current context and metadata.
  • Dynamically discover and route to visible specialists at routing time, enabling growth or shrinkage of the roster without code changes.
  • Preserve and enforce each specialist's write boundary, approval gate, stop condition, and verification rules across transitions.
  • Use case: a user starts with a vague goal and vibe-coding routes to a requirements-specification phase, then hands off to planning and execution phases with controlled handoffs.

Quick Start

Activate vibe-coding by issuing an explicit host signal or instruction to begin routing the current coding workflow.

Frequently Asked Questions about vibe-coding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-turn coding workflows with phase routing?

Multi-turn coding workflows are orchestrated by classifying user instructions and routing them to the appropriate downstream specialist phase. The routing state dynamically discovers available specialists to coordinate handoffs.

What is vibe-coding workflow management for specialist coordination?

Vibe-coding workflow management centralizes routing logic to coordinate multiple specialist skills. It preserves phase boundaries, write permissions, and governance rules while managing transitions between requirements, planning, and execution phases.

How do I route instructions to different coding workflow phases dynamically?

Instructions are routed dynamically by maintaining active routing state and activation signals based on current context and metadata. The system discovers visible specialists at routing time, enabling roster growth without code changes.

Can I enforce write boundaries and approval gates across workflow phases?

Write boundaries and approval gates are enforced across workflow phases by preserving each specialist's stop conditions and verification rules. The routing system requires explicit consent to proceed with downstream actions.

Do I need explicit consent to proceed with downstream coding actions?

Explicit consent is required to proceed with downstream coding actions. The workflow routing system preserves governance by enforcing approval gates and stop conditions before transitioning between specialist phases.

What's the best way to manage vague goals in a multi-phase coding workflow?

Vague goals in a multi-phase coding workflow are managed by routing to a requirements-specification phase first, then handing off to planning and execution phases with controlled transitions governed by verification rules.