vibe-ipd 1.0.6

vibe-ipd — Integrated Product Development Toolkit (forked from GitHub Spec Kit). Spec-Driven Development for AI-Native teams with IPD governance.

vibe-ipd

English · 中文

Integrated Product Development — Agile-Stage-Gate Hybrid for AI-Native Teams

vibe-ipd 是一个基于 Spec Kit (speckit) 增强的集成产品开发（IPD）框架，融合了敏捷开发与阶段门禁治理（Agile-Stage-Gate），为 AI-Native 团队提供从概念到交付的全流程工程化支持。

vibe-ipd extends the Spec Kit (speckit) open-source toolkit with a full IPD governance framework, multi-agent orchestration via oh-my-claudecode, and Product Development Team (PDT) role mapping — bringing enterprise-grade product development discipline to AI-assisted coding workflows.

---

What Makes vibe-ipd Different from speckit?

While speckit provides the foundational Spec-Driven Development (SDD) engine, vibe-ipd adds an opinionated IPD-Agile hybrid governance layer on top:

#	Differentiator	Description
1	IPD Stage-Gate Governance (TR0–TR6)	Full Technology Review gate model integrated into every SDD command — each /vipd-* command performs deep content validation against prior gate criteria before proceeding
2	oh-my-claudecode Multi-Agent Orchestration	50+ specialized agent roles (architect, executor, debugger, security reviewer, etc.) orchestrated via intelligent multi-agent workflows, far beyond speckit's single-agent model
3	PDT Role Mapping with RACI Matrix	Explicit mapping of LPDT → RTE, Product Manager → PO, Dev Lead → System Architect, Test Lead → QA Lead, Ops Lead → DevOps Lead, with RACI-based responsibility assignments
4	Product Trio Collaboration Workflows	Built-in templates and workflows for PO + System Architect + UX Designer collaboration during the discovery track, with structured review processes
5	Bilingual Support (中文/English)	Chinese-first documentation, Windows-native PowerShell tooling, and bilingual spec/plan support — designed for teams operating in Chinese-speaking environments
6	Dual-Track Agile with Automatic Gate Enforcement	Continuous discovery track (Product Trio) runs in parallel with delivery track; TR gates are automatically enforced by AI agents without external platform dependencies
7	Go/Kill/Hold/Recycle Gate Decisions	Every TR gate review produces an explicit decision: Go, Kill, Hold, or Recycle — no implicit defaults, ensuring rigorous stage-gate discipline

---

Quickstart

0. Install vibe-ipd

# Install from PyPI (recommended)
uv tool install vibe-ipd

# Or from source via GitHub
# uv tool install vibe-ipd --from git+https://github.com/wwe1428103707/vibe-ipd.git

Prerequisites: uv (or pipx), Python 3.11+, and an AI coding agent like Claude Code.

1. Initialize your project

# Create a new vibe-ipd project (uses uvx or pipx under the hood)
/vipd-init my-project --integration claude
cd my-project

2. Establish project principles

/vipd-constitution Create principles focused on code quality, testing standards, and IPD governance

3. Specify your feature

/vipd-specify Build a user authentication system with email/password and SSO support

4. Create implementation plan

/vipd-plan Use Python FastAPI with PostgreSQL, JWT-based auth, and pytest

5. Generate tasks and implement

/vipd-tasks
/vipd-implement

That's it — your feature is now built with full IPD governance, TR gate validation, and multi-agent orchestration.

---

Architecture Overview

Feature Catalog

vibe-ipd v1.0.1 implements 17 features across the IPD workflow:

#	Feature	Status
001	IPD Toolkit — Core gate framework and constitution	✅
002	IPD Agent PM Integration	✅
003	Blueprint Docstate-only Mode	✅
004	VIPD Command Prefix Migration	✅
005	Implement IPD Gates (TR0-TR6)	✅
006	Implement Docstate Tools	✅
007	PDT Role Setup with RACI Matrix	✅
008	CLI IPD Adaptation	✅
009	IPD Migration Gaps — 25 gaps filled	✅
010	E2E Workflow Validation	✅
011	Multilingual Greeting (--lang en/zh/ja)	✅
012	Project Cleanup & Documentation Rebrand	✅
013	VIPD Init Skill (uvx/pipx scaffolding)	✅
014	Chinese Documentation Translation	✅
015	Fix TR Gate Chicken-Egg Dependency	✅
016	VIPD Init Language Option (--lang flag)	✅
017	Version Management & Docs Preparation	✅ v1.0.0

Run vipd --version to see the current version and underlying speckit version.

Versioning

vipd follows semantic versioning (MAJOR.MINOR.PATCH), same conventions as speckit:

Bump	When
MAJOR	Breaking workflow changes, backward-incompatible format changes
MINOR	New features implemented (new specs)
PATCH	Bug fixes, doc updates, refactoring

The vipd version is tracked independently from the speckit version. Run vipd --version to see both:

vipd 1.0.0 (speckit 0.9.3.dev0)

See VERSION_BUMP.md for the complete bump process and CHANGELOG.md for release history.

Available Commands

All vibe-ipd commands follow the /vipd-* naming convention:

Core Command	Description
/vipd-init	Scaffold a new vibe-ipd project — wraps upstream specify init CLI behind a unified brand entry point
/vipd-constitution	Create or update project governing principles with IPD gate criteria
/vipd-specify	Define feature specifications with user stories and TR1 gate assessment
/vipd-clarify	Identify and resolve underspecified areas before planning
/vipd-plan	Create implementation plan with gate readiness and ADL
/vipd-tasks	Generate actionable task lists with dependency ordering
/vipd-implement	Execute tasks with IPD gate validation at each phase
/vipd-analyze	Cross-artifact consistency and coverage analysis
/vipd-checklist	Generate quality checklists for requirements validation

Agent Assignment Commands	Description
/vipd-agent-assign-assign	Auto-assign tasks to specialized agents based on RACI matrix
/vipd-agent-assign-validate	Validate agent assignments exist and RACI-compliant
/vipd-agent-assign-execute	Execute tasks by spawning assigned agents with TR4 gate validation

Documentation

Full documentation is available in the docs/ directory:

• Quickstart Guide — Get started with vibe-ipd
• Installation Guide — Install and configure
• Concepts — SDD, IPD, and Agile-Stage-Gate explained
• IPD Transformation Guide — Migrate from speckit to vibe-ipd
• Reference — Command reference and CLI docs
• Community — Extensions, presets, and walkthroughs

Project Status

vibe-ipd is currently in active development as a fork of Spec Kit with enhanced IPD capabilities. The project has completed:

• ✅ Full Spec Kit compatibility (spec → plan → tasks → implement)
• ✅ IPD gate integration (TR0–TR6 with deep content validation)
• ✅ PDT role mapping with RACI compliance
• ✅ Product Trio workflow templates
• ✅ Multi-agent orchestration via oh-my-claudecode
• ✅ Windows-native PowerShell tooling
• ✅ Bilingual documentation (CN/EN)

Current version: vipd 1.0.1 (speckit 0.9.3.dev0) — first official release! 🎉

Next milestones: TR6 launch gate automation, release management workflows, and CI/CD integration.

Prerequisites

• Linux/macOS/Windows (Windows with PowerShell 5.1+ recommended)
• Claude Code or compatible AI coding agent
• oh-my-claudecode for multi-agent orchestration
• uv or pipx for package management
• Python 3.11+
• Git

---

Relationship to Spec Kit (speckit)

vibe-ipd is a derivative fork of the Spec Kit open-source project. We retain full compatibility with the speckit engine and its template/extension/preset systems while adding our opinionated IPD governance layer on top.

If you are looking for the upstream Spec-Driven Development toolkit without IPD extensions, please use Spec Kit directly.

Acknowledgments

This project builds upon the excellent work of the Spec Kit team and the Spec-Driven Development methodology pioneered by John Lam. Without their open-source contributions, vibe-ipd would not exist.

Special thanks to the following projects and contributors:

• Agent Assign by xymelon — The /vipd-agent-assign-* command suite (assign, validate, execute) is adapted from this specialized extension for intelligent task-to-agent assignment. It enables scanning available Claude Code agents, auto-matching them to tasks based on capabilities and file path patterns, and executing tasks with IPD TR4 gate validation — bringing production-grade multi-agent orchestration to the VIPD workflow.

License

This project is licensed under the terms of the MIT open source license. Please refer to the LICENSE file for the full terms.