VibeOps MCP
A contract-based product organization system that enforces structured planning and validation for product development.
Overview
VibeOps MCP organizes product development work into a clear hierarchy with enforced contracts at each level:
Getting Started
Installation
Using Templates
Templates are provided for each work item type in contracts/templates/:
Contract Validation
Every work item must pass validation against its JSON schema before being considered valid.
Validation Commands
Working with Claude Code
When using Claude Code with this repository:
Ask Claude to create work items: "Create a module for user authentication"
Claude will use the templates and validate contracts automatically
You'll receive validated JSON contracts that conform to the schemas
See CLAUDE.md for detailed guidance on how Claude Code works with this system.
Directory Structure
Contract Requirements Summary
MODULE: Must have unique ID (MOD-####), name, description, type, status
FEATURE: Must have PRD contract with problem statement, goals, success metrics, scope
USER STORY: Must have acceptance criteria, Definition of Done, Definition of Ready
BUG: Must have reproduction steps with expected/actual results, environment details
TECH DEBT: Must have impact assessment and effort estimation
SPIKE: Must have research questions and timebox
See CLAUDE.md for complete contract specifications.
This server cannot be installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
Enforces structured product development through contract-based validation of modules, features, and issues with type-specific requirements (user stories, bugs, tech debt, spikes) using JSON schemas.