By doctormozg
Multi-perspective AI panels — brainstorming and Delphi-style expert consultation powered by a unified roster of 16 lens agents shared across both modes
npx claudepluginhub doctormozg/claude-pipelines --plugin mz-creativeFinal report writer for the /expert skill. Reads all 3 rounds of panelist outputs and synthesizers, produces a structured executive report with citation tags traceable to specific agents and rounds.
Codebase researcher for the /expert skill. When a scope modifier (scope:working, scope:branch, scope:global) is set, scans the repo within that scope and produces research.md to ground expert panel critiques in real code.
Neutral round synthesizer for the /expert skill. Reads all 5 panelist outputs from one round and produces a lens-agnostic consensus/divergence/tension summary.
Artist lens — visual thinker who approaches problems through aesthetics, form, sensory experience, and emotional resonance. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
CTO lens — tech-strategy thinker who approaches problems through architecture, build-vs-buy economics, tech-debt cost, engineering-org impact, delivery risk, and platform leverage. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Data lens — analytics and growth thinker who approaches problems through measurement validity, experiment design, instrumentation, and growth loops. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
DevOps lens — reliability-focused thinker who approaches problems through SLOs, observability, deploy safety, capacity, cost, and operational burden. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Economist lens — strategic thinker who approaches problems through incentives, markets, game theory, externalities, and opportunity cost. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Engineer lens — systems thinker focused on technical feasibility, architecture, scalability, and engineering trade-offs. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Futurist lens — forward-looking thinker who approaches problems through emerging trends, disruption cycles, convergences, and long-term trajectories. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Historian lens — context-aware thinker who approaches problems through historical precedent, patterns of change, cultural context, and path dependence. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Mathematician lens — pattern thinker who approaches problems through formal logic, optimization, structure, and elegant abstractions. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Philosopher lens — deep thinker who approaches problems through meaning, ethics, cultural impact, and conceptual frameworks. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Product lens — PMF-focused thinker who approaches problems through user value, jobs-to-be-done, roadmap tradeoffs, kill criteria, and prioritization discipline. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Psychologist lens — behavior-focused thinker who approaches problems through cognition, bias, motivation, habits, and human factors. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Scientist lens — evidence-driven thinker who approaches problems through hypotheses, experiments, empirical data, and natural systems. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Security lens — appsec thinker who approaches problems through threat modeling (STRIDE), attack surface, data handling, authZ, supply chain, compliance, and blast radius. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
SEO lens — organic-visibility thinker who approaches problems through search intent, content strategy, technical SEO, SERP features, backlink economics, and AI search impact. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
Storyteller lens — narrative thinker who approaches problems through story arcs, character motivations, metaphors, and audience engagement. Dual-mode panelist for /brainstorm and /expert; behavior is injected by the dispatching skill.
ALWAYS invoke when the user wants creative ideas, brainstorming, multi-perspective thinking, or diverse viewpoints on a problem. Triggers: "brainstorm", "creative ideas for", "think about this from different angles", "diverse perspectives on".
ALWAYS invoke when the user wants a multi-sided expert critique of an idea. Triggers:"expert review of","consult experts on","critique this idea","multi-angle analysis","strengths and weaknesses of". Provide the idea as the argument.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
No description provided.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Multi-agent plugins for Claude Code. Autonomous development pipelines, code review, deep research, and business intelligence — all as slash commands.
[!TIP] Skills compose. Most real tasks span 3–4 commands across multiple plugins — chain them end-to-end instead of reaching for any single skill in isolation. Click any workflow below to see the flow.
mz-dev-base + mz-dev-pipeflowchart LR
A["/deep-research"]:::base --> B["/build"]:::pipe
B --> C["/verify"]:::pipe
C --> D["/review-branch"]:::base
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/deep-research — survey trade-offs, cite references, pick an approach/build — research → plan (approval gate) → parallel code → review → test/verify — lint + types + tests + coverage, diagnose failures/review-branch — independent final pass before opening the PRmz-dev-pipeflowchart LR
A["/debug"]:::pipe --> B["/blast-radius"]:::pipe
B --> C["/investigate"]:::pipe
C --> D["/polish"]:::pipe
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/debug — reproduce → regression test → diagnose → fix → verify/blast-radius — map every caller, test, and type at risk of the patch/investigate — prove or disprove "does the same race exist on the refund path" without touching code/polish — fix-test-review loop until the criteria are metmz-dev-base + mz-dev-pipeflowchart LR
A["/init-rules"]:::base --> B["/explain"]:::pipe
B --> C["/audit"]:::pipe
C --> D["/blast-radius"]:::pipe
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/init-rules — install curated coding rules for the detected languages/explain — multi-angle walkthrough with Mermaid diagrams of the module/audit — ranked list of landmines and tech-debt hotspots/blast-radius — know what shatters before the first refactor commitmz-dev-pipe + mz-dev-baseflowchart LR
A["/audit"]:::pipe --> B["/investigate"]:::pipe
B --> C["/debug"]:::pipe
C --> D["/review-branch"]:::base
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/audit — prioritized vulnerabilities with file:line evidence/investigate — verify top critical findings, drop false positives/debug — TDD-style fix anchored on a regression test/review-branch — catch any fallout the fix introduced elsewheremz-creative + mz-design + mz-dev-pipe 3 pluginsflowchart LR
A["/brainstorm"]:::creative --> B["/expert"]:::creative
B --> C["/design-document"]:::design
C --> D["/build"]:::pipe
classDef creative fill:#fbefff,stroke:#8250df,color:#8250df
classDef design fill:#ffebf0,stroke:#bf3989,color:#bf3989
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/brainstorm — 5 lens personas → parallel ideation → vote-to-consensus/expert — Delphi critique (3 rounds) with dedicated report writer/design-document — draft → 4-critic loop → WCAG 2.2 AA hard gate/build — plan → code → review → test against the approved specmz-biz-outreach + mz-dev-base + mz-creative 3 pluginsflowchart LR
A["/lead-gen"]:::outreach --> B["/deep-research"]:::base
B --> C["/brainstorm"]:::creative
classDef outreach fill:#fff1e5,stroke:#bc4c00,color:#bc4c00
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef creative fill:#fbefff,stroke:#8250df,color:#8250df
/lead-gen — strategy → source research → scout → enrich → score → report/deep-research — domain context to ground outreach in current regulation/brainstorm — multi-lens positioning ideas tied back to the lead-gen reportmz-dev-pipeOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim