vibe-engineering

Guide software development through Spec, Plan, Build, Verify, and Ship phases.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/fauzanazz/claude-skills --skill vibe-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-engineering
Source: https://github.com/fauzanazz/claude-skills/tree/main/vibe-engineering
Command: npx skills add https://github.com/fauzanazz/claude-skills --skill vibe-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures disciplined AI-assisted development by guiding the process through structured phases, reducing ambiguity, and optimizing model usage.

Core Features & Use Cases

  • Structured Development Phases: Guides through Spec, Plan, Build, Verify, and Ship phases to maintain clarity and prevent mistakes.
  • Model Selection: Uses different models for different phases (Opus for Spec/Plan, Sonnet for Build/Verify/Ship) for optimal performance.
  • Memory Management: Implements robust session management and memory tracking to maintain context across sessions.
  • Multi-Session Work: Supports multi-session tasks using TDD as a contract, ensuring continuous progress and context transfer.
  • AI-Friendly Architecture: Encourages practices that make codebases easier for AI to navigate and assist with.
  • When to Skip Phases: Provides guidance on when to skip certain phases for trivial changes or bug fixes.
  • Delegation Intuition: Defines what tasks are best delegated to AI and what should be kept for human decision-making.

Quick Start

Start a new development task by running 'vibe-engineering'.

Frequently Asked Questions about vibe-engineering

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

FAQPage Schema
What is structured AI-assisted development methodology?

Structured AI-assisted development guides software processes through distinct phases—Spec, Plan, Build, Verify, and Ship—to reduce ambiguity and optimize model usage. It enforces discipline by delegating tasks appropriately between human and AI.

How do I maintain context across multiple AI development sessions?

To maintain context across multiple AI development sessions, implement robust session management and memory tracking. Use test-driven development as a contract to ensure continuous progress and seamless context transfer between sessions.

Which AI models should I use for different software development phases?

For structured software development phases, use high-capacity models like Opus for Spec and Plan phases to maximize reasoning, and faster models like Sonnet for Build, Verify, and Ship phases to optimize execution performance.

When should I skip development phases for bug fixes or trivial changes?

You should skip structured development phases like Spec and Plan for trivial changes or minor bug fixes when the scope is clear. This prevents overhead while maintaining necessary verification and shipping discipline.

What tasks should be delegated to AI versus kept for human decision-making?

Delegation intuition defines that repetitive coding and verification tasks are best delegated to AI, while architectural decisions and requirement specifications should be kept for human decision-making to ensure alignment.

How do I make my codebase easier for AI to navigate and assist with?

To make your codebase easier for AI to navigate, adopt an AI-friendly architecture that encourages clear structure and modular practices. This structured approach reduces ambiguity and improves assistance efficiency.