Releases: nareshnavinash/dobbe-mcp
Release list
v0.4.0 -- Declarative Intent-Based Pipelines
What's New
Declarative Pipeline Steps
Pipeline steps no longer send prescriptive instruction paragraphs. Instead, each step declares what needs to happen (intent, mode, context, hints) and Claude decides how to interact with the user.
This means Claude can use its best UX capabilities — plan mode for analysis, interactive prompts for data gathering, native tools for execution — without waiting for MCP updates.
4 step modes:
plan— Claude enters plan mode for deep analysisact— Direct execution: run commands, edit files, create PRsgather— Collect information interactively from user/codebasereport— Synthesize results into formatted output
8 New Multi-Perspective Review Pipelines
| Command | Perspective |
|---|---|
/dobbe-review-as-pm |
Product Manager |
/dobbe-review-as-engineer |
Software Engineer |
/dobbe-review-as-designer |
UX Designer |
/dobbe-review-as-qa |
QA Engineer |
/dobbe-review-as-test-architect |
Test Architect |
/dobbe-review-as-marketing |
Marketing |
/dobbe-review-as-sales |
Sales |
/dobbe-project-review |
All 7 perspectives + synthesis |
Each review uses gather mode to understand the project interactively, then plan mode for analysis.
By the Numbers
- 21 pipelines (up from 13)
- 24 slash commands (up from 16)
- 373 tests (up from 266), 94%+ coverage
- 52 files changed, 1207 insertions, 1025 deletions
Upgrade
npx dobbe installv0.3.0
What's Changed
npx dobbeno longer hangs -- bare command now prints usage help and exits immediatelynpx dobbe startshows feedback -- when run interactively in a terminal, prints a message to stderr explaining it's waiting for MCP messages- Consolidated startup logic --
bin/install.tsnow reuses the full startup fromsrc/index.ts(session cleanup, cache eviction, graceful shutdown, logging) - MCP config updated -- uses
npx dobbe startinstead of barenpx dobbe
Breaking Change
Existing users should re-run npx dobbe install to update their MCP server config.
v0.2.0 -- Role-Based Review Pipelines
What's New
Role-Based Review Pipelines
Added 8 new pipeline commands for multi-perspective project reviews:
| Command | Description |
|---|---|
review-as-pm |
Product Manager -- feature gaps, prioritization, UX concerns |
review-as-engineer |
Staff Engineer -- architecture, scalability, tech debt |
review-as-designer |
UX/UI Designer -- accessibility, design consistency, interactions |
review-as-qa |
Quality Engineer -- bug hunting, edge cases, quality risks |
review-as-test-architect |
Staff SDET -- test strategy, automation, CI/CD, coverage |
review-as-marketing |
Marketing Manager -- promotion strategies, positioning, content |
review-as-sales |
Sales Manager -- competitive analysis, differentiators, objections |
project-review |
Master pipeline -- chains selected roles with executive synthesis |
How It Works
Each role follows a discover -> analyze pattern:
- Discovery: Claude scans the codebase, asks 3-5 targeted questions from the role's perspective, and waits for your answers
- Analysis: Using the Q&A context, Claude produces structured findings + a markdown summary
The master project-review command dynamically chains selected roles and produces a cross-cutting executive summary.
Usage
# Install/update skills
npx dobbe install
# Use individual roles
/dobbe-review-as-pm
/dobbe-review-as-engineer
# Run all 7 roles (or select specific ones)
/dobbe-project-reviewFixes
- Fixed skills path resolution for
dist/src/layout (skills were not found duringdobbe install) - Fixed
.npmignoreto include compiled output in npm package - Fixed
main/typespaths in package.json
Stats
- 21 total pipeline commands (up from 13)
- 24 skills installed
- 366 tests passing