SpecVibe
A world-class, spec-driven development framework for building production-ready, AI-native applications. Use for any new project to ensure adherence to the most advanced 2026 best practices in architecture, security, testing, and deployment.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/badideal-2046/specvibeSpecVibe: 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 iteration strategy. | references/08-ai-collaboration.md |
| 5. Review | Quality & Security Assurance | Conduct automated and human code reviews, focusing on security, logic, and maintainability. | references/04-security.md |
| 6. Document | Knowledge Capture | Automatically generate and manually refine user and developer documentation. | references/09-documentation.md |
| 7. Deploy | CI/CD & Observability | Containerize, set up CI/CD pipelines, and implement full observability. | references/06-devops.md, references/07-error-handling.md |
Stage 1: Specify - The Intent
Goal: Define what to build and why in a structured spec.md.
- Delegate: Ask the AI to interview you about the project goals and generate a draft
spec.mdusing thetemplates/spec-template.md. - Review: Check if the spec accurately captures all user stories, edge cases, and success metrics.
- Own: The final approval of the user requirements and business goals.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-badideal-2046-specvibe": {
"enabled": true,
"auto_update": true
}
}
}