SpecVibe

# SpecVibe: The AI-Native Development Framework

This skill provides a universal, seven-stage framework for developing production-ready, AI-native applications. It enforces a **"Specification-as-Source-of-Truth"** mindset, ensuring that every aspect of the project is defined, testable, secure, and documented before and during implementation, following the most advanced 2026 community best practices from Google, GitHub, and Thoughtworks.

## Core Philosophy

- **Intent is the Source of Truth**: The specification (`spec.md`) is the primary artifact. Code is the last-mile implementation of that intent.
- **Human-AI Collaboration**: Follow the **Delegate/Review/Own** model at every stage to maximize efficiency and maintain quality.
- **Iterate in Small, Validated Chunks**: Break down work into the smallest possible units, test them, and commit frequently. Never let the AI generate large, monolithic blocks of code.
- **Automate Everything**: Use tests, linters, CI/CD, and automated documentation to build a robust quality assurance system.

## The Seven Stages of AI-Native Development

Follow these stages sequentially. Each stage has a **Quality Gate**—a set of questions you must answer before proceeding—and a clear **Delegate/Review/Own** model for human-AI collaboration.

| Stage | Focus | Key Activities | Reference Guides |
| :--- | :--- | :--- | :--- |
| **1. Specify** | User Journey & Requirements | Create `spec.md` defining user stories, goals, and non-functional requirements. | `references/00-specvibe.md` |
| **2. Plan** | Technical Architecture | Create `PLAN.md`, select tech stack, define architecture, and break down the spec into tasks. | `references/02-backend.md`, `references/03-frontend.md` |
| **3. Test** | Behavior-Driven Definition | Write failing unit, integration, and E2E tests based on the spec and plan. | `references/05-testing.md` |
| **4. Implement** | Code Generation & Refinement | Write (or generate) code to make the tests pass, following a chunked...

# SpecVibe

**An executable, spec-driven framework for building production-ready AI-native applications.**

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg )](https://opensource.org/licenses/MIT ) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg )](CONTRIBUTING.md) [![ClawHub](https://img.shields.io/badge/ClawHub-v1.0.0-blue )](https://clawhub.ai/skills/badideal-2046/SpecVibe ) 

SpecVibe is not just a collection of guidelines; it is a complete, structured, and executable framework designed to be integrated directly into modern AI coding assistants like Claude Code, OpenClaw, and Cursor. It enforces a rigorous, seven-stage development workflow, ensuring every project is architected, built, tested, and deployed according to 2026 industry best practices.

## Why SpecVibe?

Most AI development guides are passive documents. SpecVibe is an **active framework** that becomes part of your AI assistant's core logic. It bridges the gap between ad-hoc prompting ("vibe coding") and professional software engineering.

| Feature | Standard Guides | SpecVibe Framework |
| :--- | :--- | :--- |
| **Core Philosophy** | Vague best practices | Executable **Spec-Driven** workflow |
| **Coverage** | Focus on one area (e.g., security) | **Full Lifecycle**: Specify, Plan, Test, Implement, Review, Document, Deploy |
| **Integration** | Manual copy-pasting | **Direct Integration** with Claude Code, OpenClaw, etc. |
| **Security Standard** | General advice | Aligned with **OWASP Top 10:2025** |
| **AI Collaboration** | Basic prompt tips | **Delegate/Review/Own** model at every stage |
| **Completeness** | Missing key areas | Includes a11y, i18n, API versioning, and more |

## The 7-Stage Workflow

SpecVibe structures development into seven distinct stages, each with a clear goal and a quality gate.

1.  **Specify**: Define user journeys and requirements in a structured `spec.md`.
2.  **Plan**: Create the technical architecture, data models, and API...