Transform any AI coding agent into a structured development partner with battle-tested engineering workflows.
# Setup your coding agent
npx responsible-vibe-mcp --generate-config amazonq-cli # or claude, gemini, opencode, copilot-vscode
# OR manually configure any MCP agent with our system prompt, check the docs for thatHead over to a new empty dir and ask your agent: "Build a UNO-like card game" – and instantly experience how your agent doesn't just shoot, but starts engineering – with YOU in the driver seat!
✅ Multiple battle-tested workflows (classical V-model "waterfall", Anthropic's EPCC, Test-Driven-Development, Reproduction-based bugfix, and many more)
✅ Context-aware process guidance: Your agent will take notes and plan tasks which survive context compression and even sessions.
✅ Project memory across conversations and branches
✅ Automatic documentation and decision tracking
✅ Multi-agent collaboration with specialized roles (business-analyst, architect, developer)
Enable teams of specialized AI agents to collaborate on development tasks with crowd-mcp:
- 👥 Team-based development: Business-analyst, architect, and developer agents work together
- 🔄 Structured handoffs: Clear responsibility transfers between agents
- 💬 Built-in collaboration: Agents consult each other via messaging
- 📋 Specialized workflows: sdd-feature-crowd, sdd-bugfix-crowd, sdd-greenfield-crowd
Quick Start:
# Copy pre-configured agent definitions
npx responsible-vibe-mcp@latest agents copy
# List available agent configurations
npx responsible-vibe-mcp@latest agents listSee Crowd MCP Integration Guide → for setup and usage.
Works in any agent that supports the Model-Context-Protocol. Whenever a new IDE or Terminal UI rises: You don't need to change the way you work.
There are zillions of "game changer next gen IDEs" out there, each claiming they will revolutionalize how software is going to be created.
In the end, they all just manipulate context of a transformer based LLM – it's all just noodle soup. And they are fast at changing wha't going to be part of the context, and it's even getting accelerated by parallel agents.
The problem: The faster agents become, the harder it is to engineer. I strongly believe that software engineering is a creative process which majorly happens inside the engineers brain.
Responsible-Vibe-MCP helps to fill the conversation context with contents from YOUR brain – instead of relying the agent will have understood what you should have thought about.
And since may developers tend to through structured processing off the cliff once they think they start coding, responsible-vibe-mcp will maintain proactive process guidance - your AI knows what to do next in each development phase, follow proven engineering methodologies, and maintain long-term project context.
Check the 📖 Complete Documentation →
There is also a recorded session on "how to tame your stubborn software agent" as part of the video podcast Software-Architektur.tv (German, auto-translated subtitles are okay-ish) which gives a more detailed insight into the basic ideas and how it's supposed to work.