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:

1. Discovery: Claude scans the codebase, asks 3-5 targeted questions from the role's perspective, and waits for your answers
2. 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-review

Fixes

• Fixed skills path resolution for dist/src/ layout (skills were not found during dobbe install)
• Fixed .npmignore to include compiled output in npm package
• Fixed main/types paths in package.json

Stats

• 21 total pipeline commands (up from 13)
• 24 skills installed
• 366 tests passing