analyzthis_design 2.2.0 → 2.3.1

package/HOW-TO-USE.md

@@ -335,6 +335,23 @@ npx analyzthis_design evolve --extract             # write patch proposals
 npx analyzthis_design evolve --apply <patchId>      # apply after review
 ```
 
+### Check evolution metrics
+
+```bash
+npx analyzthis_design evolve --metrics             # team evolution dashboard
+npx analyzthis_design evolve --ready               # check if enough data to evolve
+```
+
+The dashboard shows a per-persona score (0-100) based on lessons, outcomes, and patches applied. Levels: Novice (0-19) -> Developing (20-39) -> Proficient (40-59) -> Advanced (60-79) -> Expert (80-100).
+
+After every successful run, Devi prints an evolution readiness hint automatically.
+
+### Premise challenge (v2.2)
+
+When you run a critique, the planner now evaluates whether your task framing is valid before planning chunks. If the premise is questionable (e.g., "users don't convert because X is buried" — but maybe they reach X and still don't convert), the planner adds a `premise_check` chunk that Raj runs first. All subsequent persona chunks see the premise assessment.
+
+The synthesis step also explicitly resolves disagreements — if Arjun says SHIP and Meera says REVISE, the synthesis picks a winner with a forward path instead of summarizing both sides.
+
 ### Confirm whether the advice actually shipped
 
 ```bash
@@ -426,6 +443,8 @@ npx analyzthis_design moodboard critique --board <id>
 npx analyzthis_design moodboard add --board <id> --url <url> --tags a,b
 
 # Evolve
+npx analyzthis_design evolve --metrics
+npx analyzthis_design evolve --ready
 npx analyzthis_design evolve --extract --dry-run
 npx analyzthis_design evolve --apply <patchId>
 npx analyzthis_design outcome --confirm --persona arjun --result shipped

package/README.md

@@ -4,6 +4,22 @@ A set of AI design personas and a task-first evaluation framework that plugs int
 
 Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
 
+## v2.3.1 — independently callable personas (31 Aug 2026)
+
+After install, type `/noor`, `/anuj`, `/arjun`, `/meera`, `/priya`, `/zara`, `/raj`, `/kavi` even if Claude’s slash menu only lists Getting Started.
+
+- `npx analyzthis_design --target claude` is the same as `install --target claude` (leading `--target` used to print “Unknown command”).
+- Install writes project slash commands into `.claude/commands/` and `.cursor/commands/`.
+- `mcp --configure claude` writes Claude Desktop, Claude Code (`~/.claude.json`), and this repo’s `.mcp.json` when you are in a project.
+- Do not `npm install` this package inside a pnpm/Yarn `workspace:*` repo — use `npx … --target` instead.
+- Slash and MCP still use the model already in your chat. CLI `run` still picks a strong planner and cheap chunks.
+
+Website changelog: [analyzthis-lab.vercel.app/design#whats-new](https://analyzthis-lab.vercel.app/design#whats-new)
+
+## v2.3.0 — MCP for any IDE
+
+19 MCP tools (`analyzthis_noor`, not `/noor`). Slash commands and MCP are different pipes. MCP never creates a slash menu entry.
+
 ## v2.2 — project-scoped knowledge bank
 
 Knowledge sources are now scoped per project by default. `collect`, `connect`, `sync`, `disconnect`, and `status` operate on the project derived from your current working directory, and the built `knowledge-bank` skill is written into that project's local skills directory (`<project>/.claude/skills/knowledge-bank/SKILL.md`, `<project>/.cursor/skills/...`, etc.). Invoking a skill from one project never reads another project's vaults.
@@ -21,17 +37,21 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
 
 Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
 
-**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.2.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
+**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.3.1 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
 
 ---
 
 ## Quick start
 
 ```bash
-# 1. Install the npm package (no auto-install, no obfuscation)
+# 1. Install the CLI globally (optional). Do not run npm install inside a
+#    pnpm/Yarn workspace repo — npm cannot read workspace:* and will fail.
+#    Prefer npx from any folder:
 npm install -g analyzthis_design
 
-# 2. Install slash commands into your IDE (explicit, consent-based)
+# 2. Copy skills + slash commands into your IDE (consent-based)
+npx analyzthis_design install --target all
+# Same thing: a leading --target means install
 npx analyzthis_design --target all
 
 # 3. Run a task in v2.0 chunked mode (free/cheap models)
@@ -41,11 +61,14 @@ npx analyzthis_design run --task "Review invoice approval screen"
 npx analyzthis_design run-unchunked --task "Review invoice approval screen" --provider host
 ```
 
-> **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design --target <ide>` command.
+> **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
+>
+> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server with 19 tools (all personas + combination passes + utilities). Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
 
 ### Install by target IDE
 
 ```bash
+npx analyzthis_design install --target claude
 npx analyzthis_design --target claude
 npx analyzthis_design --target codex
 npx analyzthis_design --target grok
@@ -53,7 +76,7 @@ npx analyzthis_design --target windsurf
 npx analyzthis_design --target all --force
 ```
 
-**After install:** type `/getting-started` in Cursor or Claude Code (or `@getting-started` in Windsurf). For a complete walkthrough, see [HOW-TO-USE.md](./HOW-TO-USE.md). Re-print CLI help anytime with `npx analyzthis_design welcome`.
+**After install:** type `/noor`, `/arjun`, `/ux-ideator` (or `@` in Windsurf). Claude’s menu may only show Getting Started — type the name anyway. Also `/getting-started`. Walkthrough: [HOW-TO-USE.md](./HOW-TO-USE.md). Re-print help: `npx analyzthis_design welcome`.
 
 | Tool | Skills installed to | Invoke |
 |---|---|---|
@@ -733,9 +756,18 @@ npx analyzthis_design run --continue --task "..."   # resume host-mode run after
 # CSV validation
 npx analyzthis_design validate    # validate all 28 CSV files against schema.json
 
+# MCP server (for any AI IDE: Cursor, Claude Desktop, Lovable, v0, Bolt, Replit)
+npx analyzthis_design mcp                          # start stdio MCP server
+npx analyzthis_design mcp --configure cursor       # auto-config Cursor
+npx analyzthis_design mcp --configure claude        # auto-config Claude Desktop
+npx analyzthis_design mcp --configure windsurf     # auto-config Windsurf
+npx analyzthis_design mcp --configure <tool>       # print config for any other tool
+
 # Self-evolving team (v1.21)
 npx analyzthis_design evolve --extract [--window N] [--dry-run]
 npx analyzthis_design evolve --apply <patchId> [--dry-run]
+npx analyzthis_design evolve --metrics [--project id]
+npx analyzthis_design evolve --ready [--project id]
 npx analyzthis_design outcome --infer [--window N]
 npx analyzthis_design outcome --pending
 npx analyzthis_design outcome --confirm --persona <id> --result shipped|revised|blocked|missed
@@ -783,6 +815,8 @@ lib/
   chunk-telemetry.js    Per-chunk model quality tracking
   chunk-run.js          Top-level chunked execution coordinator
   reference-pack.js     Shared multi-file CSV + vault retrieval (buildReferencePack)
+  mcp-server.js         MCP server — 19 tools for any MCP-compatible IDE
+  system-prompt.js      Consolidated prompt generator (fallback for non-MCP tools)
   moodboard.js          Mood-board engine: collect web/DS references, tag, deliberate
   dedup.js              Cross-persona redundancy detection
   lessons.js            Self-evolving lessons store (extract/retrieve/inject)
@@ -829,6 +863,27 @@ skills/
 
 ---
 
+## What's new in v2.3
+
+| Feature | Description |
+|---------|-------------|
+| **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
+| **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
+| **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
+| **19 MCP tools** | 8 individual personas (arjun, meera, priya, zara, noor, anuj, raj, kavi) + 6 combination passes (ux-ideator, persona-orchestrator, design-critic, ux-story-gate, design-director, mood-board) + 5 utilities (evolve-check, collect, retrieve, session, system-prompt) |
+| **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
+
+## What's new in v2.2
+
+| Feature | Description |
+|---------|-------------|
+| **Premise challenge** | Planner now evaluates whether the task premise is valid before planning chunks. Can add a `premise_check` chunk (Raj) that runs first and questions "are we solving the right problem?" |
+| **Conflict resolution** | Synthesis must pick a winner when personas disagree — not summarize both sides. Detects disagreements automatically, injects them into the synthesis prompt, and requires a definitive answer with a forward path. |
+| **Raj authority expanded** | Raj can now challenge the task premise (not just arbitrate stalemates). "Accepting the task framing without questioning it" is explicitly forbidden. |
+| **Evolution metrics** | `evolve --metrics` shows a per-persona evolution dashboard (0-100 score, levels: Novice → Expert). `evolve --ready` checks if enough data exists to propose patches. |
+| **Devi evolution check** | After every successful run, Devi prints an evolution readiness hint and asks if the team is ready to evolve. |
+| **Plain source, no obfuscation** | Removed `javascript-obfuscator` entirely. `dist/` is fully auditable plain JavaScript. `postinstall` only prints a message — no auto-install. |
+
 ## What's new in v2.0
 
 | Feature | Description |

package/agents/cards/raj.md

@@ -2,11 +2,11 @@
 
 10+ years product strategy. Speaks ONLY when the Stalemate Protocol activates — does not volunteer opinions. Every position anchored to PRD evidence, user data, or a named product principle.
 
-**Allowed:** resolve stalemates between personas using the 5 product principles; issue final SHIP/REVISE/BLOCK when personas disagree.
+**Allowed:** resolve stalemates between personas using the 5 product principles; issue final SHIP/REVISE/BLOCK when personas disagree; challenge the task premise — "are we solving the right problem?"
 
-**Forbidden:** running with no stalemate/BLOCK condition; code edits without explicit build approval.
+**Forbidden:** running with no stalemate/BLOCK condition; code edits without explicit build approval; accepting the task framing without questioning it.
 
-**Activation criteria (any one):** 2+ unconceded structural objections; a "non-negotiable" claim refused; the same argument repeated without new evidence; a PRD-persona-priority conflict with no established priority.
+**Activation criteria (any one):** 2+ unconceded structural objections; a "non-negotiable" claim refused; the same argument repeated without new evidence; a PRD-persona-priority conflict with no established priority; synthesis phase (always — must resolve conflicts and challenge premise).
 
 ## Output schema (always full — Raj has no lite mode; his output is inherently a short decision)
 ```

package/dist/HOW-TO-USE.md

@@ -335,6 +335,23 @@ npx analyzthis_design evolve --extract             # write patch proposals
 npx analyzthis_design evolve --apply <patchId>      # apply after review
 ```
 
+### Check evolution metrics
+
+```bash
+npx analyzthis_design evolve --metrics             # team evolution dashboard
+npx analyzthis_design evolve --ready               # check if enough data to evolve
+```
+
+The dashboard shows a per-persona score (0-100) based on lessons, outcomes, and patches applied. Levels: Novice (0-19) -> Developing (20-39) -> Proficient (40-59) -> Advanced (60-79) -> Expert (80-100).
+
+After every successful run, Devi prints an evolution readiness hint automatically.
+
+### Premise challenge (v2.2)
+
+When you run a critique, the planner now evaluates whether your task framing is valid before planning chunks. If the premise is questionable (e.g., "users don't convert because X is buried" — but maybe they reach X and still don't convert), the planner adds a `premise_check` chunk that Raj runs first. All subsequent persona chunks see the premise assessment.
+
+The synthesis step also explicitly resolves disagreements — if Arjun says SHIP and Meera says REVISE, the synthesis picks a winner with a forward path instead of summarizing both sides.
+
 ### Confirm whether the advice actually shipped
 
 ```bash
@@ -426,6 +443,8 @@ npx analyzthis_design moodboard critique --board <id>
 npx analyzthis_design moodboard add --board <id> --url <url> --tags a,b
 
 # Evolve
+npx analyzthis_design evolve --metrics
+npx analyzthis_design evolve --ready
 npx analyzthis_design evolve --extract --dry-run
 npx analyzthis_design evolve --apply <patchId>
 npx analyzthis_design outcome --confirm --persona arjun --result shipped

package/dist/README.md

@@ -4,6 +4,22 @@ A set of AI design personas and a task-first evaluation framework that plugs int
 
 Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
 
+## v2.3.1 — independently callable personas (31 Aug 2026)
+
+After install, type `/noor`, `/anuj`, `/arjun`, `/meera`, `/priya`, `/zara`, `/raj`, `/kavi` even if Claude’s slash menu only lists Getting Started.
+
+- `npx analyzthis_design --target claude` is the same as `install --target claude` (leading `--target` used to print “Unknown command”).
+- Install writes project slash commands into `.claude/commands/` and `.cursor/commands/`.
+- `mcp --configure claude` writes Claude Desktop, Claude Code (`~/.claude.json`), and this repo’s `.mcp.json` when you are in a project.
+- Do not `npm install` this package inside a pnpm/Yarn `workspace:*` repo — use `npx … --target` instead.
+- Slash and MCP still use the model already in your chat. CLI `run` still picks a strong planner and cheap chunks.
+
+Website changelog: [analyzthis-lab.vercel.app/design#whats-new](https://analyzthis-lab.vercel.app/design#whats-new)
+
+## v2.3.0 — MCP for any IDE
+
+19 MCP tools (`analyzthis_noor`, not `/noor`). Slash commands and MCP are different pipes. MCP never creates a slash menu entry.
+
 ## v2.2 — project-scoped knowledge bank
 
 Knowledge sources are now scoped per project by default. `collect`, `connect`, `sync`, `disconnect`, and `status` operate on the project derived from your current working directory, and the built `knowledge-bank` skill is written into that project's local skills directory (`<project>/.claude/skills/knowledge-bank/SKILL.md`, `<project>/.cursor/skills/...`, etc.). Invoking a skill from one project never reads another project's vaults.
@@ -21,17 +37,21 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
 
 Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
 
-**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.2.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
+**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.3.1 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
 
 ---
 
 ## Quick start
 
 ```bash
-# 1. Install the npm package (no auto-install, no obfuscation)
+# 1. Install the CLI globally (optional). Do not run npm install inside a
+#    pnpm/Yarn workspace repo — npm cannot read workspace:* and will fail.
+#    Prefer npx from any folder:
 npm install -g analyzthis_design
 
-# 2. Install slash commands into your IDE (explicit, consent-based)
+# 2. Copy skills + slash commands into your IDE (consent-based)
+npx analyzthis_design install --target all
+# Same thing: a leading --target means install
 npx analyzthis_design --target all
 
 # 3. Run a task in v2.0 chunked mode (free/cheap models)
@@ -41,11 +61,14 @@ npx analyzthis_design run --task "Review invoice approval screen"
 npx analyzthis_design run-unchunked --task "Review invoice approval screen" --provider host
 ```
 
-> **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design --target <ide>` command.
+> **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
+>
+> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server with 19 tools (all personas + combination passes + utilities). Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
 
 ### Install by target IDE
 
 ```bash
+npx analyzthis_design install --target claude
 npx analyzthis_design --target claude
 npx analyzthis_design --target codex
 npx analyzthis_design --target grok
@@ -53,7 +76,7 @@ npx analyzthis_design --target windsurf
 npx analyzthis_design --target all --force
 ```
 
-**After install:** type `/getting-started` in Cursor or Claude Code (or `@getting-started` in Windsurf). For a complete walkthrough, see [HOW-TO-USE.md](./HOW-TO-USE.md). Re-print CLI help anytime with `npx analyzthis_design welcome`.
+**After install:** type `/noor`, `/arjun`, `/ux-ideator` (or `@` in Windsurf). Claude’s menu may only show Getting Started — type the name anyway. Also `/getting-started`. Walkthrough: [HOW-TO-USE.md](./HOW-TO-USE.md). Re-print help: `npx analyzthis_design welcome`.
 
 | Tool | Skills installed to | Invoke |
 |---|---|---|
@@ -733,9 +756,18 @@ npx analyzthis_design run --continue --task "..."   # resume host-mode run after
 # CSV validation
 npx analyzthis_design validate    # validate all 28 CSV files against schema.json
 
+# MCP server (for any AI IDE: Cursor, Claude Desktop, Lovable, v0, Bolt, Replit)
+npx analyzthis_design mcp                          # start stdio MCP server
+npx analyzthis_design mcp --configure cursor       # auto-config Cursor
+npx analyzthis_design mcp --configure claude        # auto-config Claude Desktop
+npx analyzthis_design mcp --configure windsurf     # auto-config Windsurf
+npx analyzthis_design mcp --configure <tool>       # print config for any other tool
+
 # Self-evolving team (v1.21)
 npx analyzthis_design evolve --extract [--window N] [--dry-run]
 npx analyzthis_design evolve --apply <patchId> [--dry-run]
+npx analyzthis_design evolve --metrics [--project id]
+npx analyzthis_design evolve --ready [--project id]
 npx analyzthis_design outcome --infer [--window N]
 npx analyzthis_design outcome --pending
 npx analyzthis_design outcome --confirm --persona <id> --result shipped|revised|blocked|missed
@@ -783,6 +815,8 @@ lib/
   chunk-telemetry.js    Per-chunk model quality tracking
   chunk-run.js          Top-level chunked execution coordinator
   reference-pack.js     Shared multi-file CSV + vault retrieval (buildReferencePack)
+  mcp-server.js         MCP server — 19 tools for any MCP-compatible IDE
+  system-prompt.js      Consolidated prompt generator (fallback for non-MCP tools)
   moodboard.js          Mood-board engine: collect web/DS references, tag, deliberate
   dedup.js              Cross-persona redundancy detection
   lessons.js            Self-evolving lessons store (extract/retrieve/inject)
@@ -829,6 +863,27 @@ skills/
 
 ---
 
+## What's new in v2.3
+
+| Feature | Description |
+|---------|-------------|
+| **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
+| **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
+| **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
+| **19 MCP tools** | 8 individual personas (arjun, meera, priya, zara, noor, anuj, raj, kavi) + 6 combination passes (ux-ideator, persona-orchestrator, design-critic, ux-story-gate, design-director, mood-board) + 5 utilities (evolve-check, collect, retrieve, session, system-prompt) |
+| **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
+
+## What's new in v2.2
+
+| Feature | Description |
+|---------|-------------|
+| **Premise challenge** | Planner now evaluates whether the task premise is valid before planning chunks. Can add a `premise_check` chunk (Raj) that runs first and questions "are we solving the right problem?" |
+| **Conflict resolution** | Synthesis must pick a winner when personas disagree — not summarize both sides. Detects disagreements automatically, injects them into the synthesis prompt, and requires a definitive answer with a forward path. |
+| **Raj authority expanded** | Raj can now challenge the task premise (not just arbitrate stalemates). "Accepting the task framing without questioning it" is explicitly forbidden. |
+| **Evolution metrics** | `evolve --metrics` shows a per-persona evolution dashboard (0-100 score, levels: Novice → Expert). `evolve --ready` checks if enough data exists to propose patches. |
+| **Devi evolution check** | After every successful run, Devi prints an evolution readiness hint and asks if the team is ready to evolve. |
+| **Plain source, no obfuscation** | Removed `javascript-obfuscator` entirely. `dist/` is fully auditable plain JavaScript. `postinstall` only prints a message — no auto-install. |
+
 ## What's new in v2.0
 
 | Feature | Description |

package/dist/agents/cards/raj.md

@@ -2,11 +2,11 @@
 
 10+ years product strategy. Speaks ONLY when the Stalemate Protocol activates — does not volunteer opinions. Every position anchored to PRD evidence, user data, or a named product principle.
 
-**Allowed:** resolve stalemates between personas using the 5 product principles; issue final SHIP/REVISE/BLOCK when personas disagree.
+**Allowed:** resolve stalemates between personas using the 5 product principles; issue final SHIP/REVISE/BLOCK when personas disagree; challenge the task premise — "are we solving the right problem?"
 
-**Forbidden:** running with no stalemate/BLOCK condition; code edits without explicit build approval.
+**Forbidden:** running with no stalemate/BLOCK condition; code edits without explicit build approval; accepting the task framing without questioning it.
 
-**Activation criteria (any one):** 2+ unconceded structural objections; a "non-negotiable" claim refused; the same argument repeated without new evidence; a PRD-persona-priority conflict with no established priority.
+**Activation criteria (any one):** 2+ unconceded structural objections; a "non-negotiable" claim refused; the same argument repeated without new evidence; a PRD-persona-priority conflict with no established priority; synthesis phase (always — must resolve conflicts and challenge premise).
 
 ## Output schema (always full — Raj has no lite mode; his output is inherently a short decision)
 ```

package/dist/bin/cli.js

@@ -83,6 +83,13 @@ Usage:
   research --url <url>       Fetch a URL and append to session web-context.md
   research --query <text>    Search stub (or provider) appended to web-context.md
 
+── MCP server (for any AI IDE: Cursor, Claude Desktop, Lovable, v0, Bolt) ──
+  mcp                       Start the MCP server on stdio (for MCP client config)
+  mcp --configure cursor    Write MCP config to ~/.cursor/mcp.json
+  mcp --configure claude    Write MCP config to Claude Desktop config
+  mcp --configure windsurf   Write MCP config to Windsurf
+  mcp --configure <tool>    Print manual MCP config for any other tool
+
 ── Mood board commands ─────────────────────────────────────
   moodboard create --task <text>   Build a mood board from web + DS references
                                     [--url <url> ...] [--auto]
@@ -241,7 +248,13 @@ Docs: https://github.com/rishikeshjoshi/analyzthis_design
 
 // ─── Parse args ──────────────────────────────────────────────────────────────
 
-const [,, cmd, ...flags] = process.argv;
+let [, , cmd, ...flags] = process.argv;
+// Leading flags mean install: `npx analyzthis_design --target claude`
+// Keep --help / -h as help, not install.
+if (cmd && cmd.startsWith('-') && cmd !== '--help' && cmd !== '-h') {
+  flags = [cmd, ...flags];
+  cmd = 'install';
+}
 
 function getFlag(name) {
   // Supports both --flag=value and --flag value
@@ -751,6 +764,19 @@ switch (cmd) {
     process.exit(1);
   }
 
+  // ── MCP server ─────────────────────────────────────────────────────────
+
+  case 'mcp': {
+    const mcpServer = require('../lib/mcp-server');
+    const configureTarget = getFlag('configure');
+    if (configureTarget) {
+      mcpServer.writeMcpConfig(configureTarget);
+      break;
+    }
+    mcpServer.startStdioServer();
+    break;
+  }
+
   // ── Retrieve-on-demand reference rows ───────────────────────────────────
 
   case 'retrieve': {

package/dist/lib/chunk-planner.js

@@ -108,6 +108,17 @@ function plannerSystemPrompt() {
     'Each chunk targets one persona and has a clear goal, prompts, effort level, and dependencies.',
     'You must output ONLY a JSON object inside a ```json code fence.',
     '',
+    'CRITICAL: Before planning chunks, evaluate whether the task premise is valid.',
+    'Ask: "Are we solving the right problem?" If the premise is questionable, add a',
+    'premise_check chunk (persona: raj, effort: hard) that explicitly challenges the',
+    'framing. The premise_check chunk should run FIRST and its output should be',
+    'available to subsequent chunks via depends_on.',
+    '',
+    'Also add a synthesis chunk (persona: raj, effort: hard) that runs LAST and must:',
+    '1. Resolve any disagreements between personas (pick a winner, give a forward path)',
+    '2. Challenge the premise if it was not already challenged',
+    '3. Produce a definitive verdict — not a summary of opinions',
+    '',
     'Allowed personas: arjun (UX/visual), meera (business), priya (feasibility), zara (delight), noor (minimalist IA), anuj (dense power-user), raj (strategy/arbitration).',
     '',
     'Effort levels:',
@@ -119,21 +130,33 @@ function plannerSystemPrompt() {
     '{',
     '  "plan_id": "short-unique-id",',
     '  "task_summary": "one-line summary",',
+    '  "premise_valid": true | false | "questionable",',
+    '  "premise_concern": "if questionable, what is the real problem?",',
     '  "chunks": [',
     '    {',
-    '      "id": "ia",',
-    '      "persona": "noor",',
-    '      "goal": "define information hierarchy",',
+    '      "id": "premise_check",',
+    '      "persona": "raj",',
+    '      "goal": "challenge the task framing — are we solving the right problem?",',
     '      "system_prompt": "...",',
     '      "user_prompt": "...",',
-    '      "effort": "standard",',
+    '      "effort": "hard",',
     '      "depends_on": [],',
-    '      "output_schema": "hierarchy_list"',
+    '      "output_schema": "premise_assessment"',
+    '    },',
+    '    {',
+    '      "id": "arjun",',
+    '      "persona": "arjun",',
+    '      "goal": "...",',
+    '      "system_prompt": "...",',
+    '      "user_prompt": "...",',
+    '      "effort": "standard",',
+    '      "depends_on": ["premise_check"],',
+    '      "output_schema": "ux_audit"',
     '    }',
     '  ],',
     '  "synthesis": {',
     '    "persona": "raj",',
-    '    "goal": "resolve conflicts and produce final verdict",',
+    '    "goal": "resolve conflicts, challenge premise if needed, produce definitive verdict",',
     '    "system_prompt": "...",',
     '    "user_prompt": "..."',
     '  }',

package/dist/lib/chunk-synthesis.js

@@ -29,18 +29,46 @@ function buildSynthesisPrompt(plan, results, contextPack) {
     lines.push(r.output.slice(0, 1200));
   }
 
+  // Detect disagreements between personas for explicit arbitration.
+  var disagreements = [];
+  for (var a = 0; a < results.length; a++) {
+    for (var b = a + 1; b < results.length; b++) {
+      var va = results[a].structured_output && results[a].structured_output.verdict;
+      var vb = results[b].structured_output && results[b].structured_output.verdict;
+      if (va && vb && va !== vb) {
+        disagreements.push(results[a].persona + ' says ' + va + ' but ' + results[b].persona + ' says ' + vb);
+      }
+    }
+  }
+
   lines.push('',
+    'You MUST do the following:',
+    '',
+    '1. RESOLVE CONFLICTS: If personas disagree on any point, pick a winner. Do not present both sides and leave it open. State which persona is correct and why, with a forward path.',
+    '2. CHALLENGE THE PREMISE: Before accepting the task framing, ask: "Are we solving the right problem?" If the premise is questionable, flag it explicitly.',
+    '3. Give a definitive answer — not a summary of opinions.',
+    '',
     'Produce:',
+    '- Premise check: Is the task framing valid? If not, what is the real problem?',
+    '- Resolved conflicts: For each disagreement, who is right and why.',
     '- Verdict: SHIP | REVISE | BLOCK',
     '- Composite score out of 5 if applicable',
-    '- Top 3 actionable changes',
+    '- Top 3 actionable changes (each with a specific forward path, not just "fix it")',
     '- Brief reasoning',
     '',
     'Use the same format as the design-critic synthesis.'
   );
 
+  if (disagreements.length) {
+    lines.splice(lines.indexOf('You MUST do the following:'), 0,
+      'DETECTED DISAGREEMENTS (must resolve each):', '');
+    for (var d = 0; d < disagreements.length; d++) {
+      lines.splice(lines.indexOf('DETECTED DISAGREEMENTS'), 0, '  - ' + disagreements[d]);
+    }
+  }
+
   return {
-    system: 'You synthesize multi-persona design critique outputs. Be concise and cite the most important conflicts.',
+    system: 'You synthesize multi-persona design critique outputs. You are decisive — not a summarizer. Resolve conflicts explicitly, challenge premises, and give forward paths. If personas contradict, pick a winner with reasoning.',
     user: lines.join('\n'),
   };
 }
@@ -138,6 +166,9 @@ async function synthesize(opts) {
     markdown: syn.markdown || text,
     model_used: { provider: model.provider, model: model.model, cost: model.cost },
     contradictions: contradictions,
+    premise_challenge: extractPremiseCheck(text),
+    conflict_resolutions: extractConflictResolutions(text),
+    raw_synthesis: text,
     tokens: { input: inTok, output: outTok },
     cost: chunkModels.estimateCost(model, inTok, outTok),
   };
@@ -169,8 +200,34 @@ function fallbackSynthesis(results) {
   };
 }
 
+function extractPremiseCheck(text) {
+  if (!text) return null;
+  var m = text.match(/premise[\s:]*check[\s:]*([^\n]+)/i);
+  if (m) return m[1].trim();
+  m = text.match(/are we solving[\s\S]{0,200}/i);
+  if (m) return m[0].trim();
+  m = text.match(/premise[\s:]*([valid|questionable|invalid]+)/i);
+  if (m) return m[0].trim();
+  return null;
+}
+
+function extractConflictResolutions(text) {
+  if (!text) return [];
+  var resolutions = [];
+  var blocks = text.split(/\n(?=\d+\.|resolve|conflict|disagree)/i);
+  for (var i = 0; i < blocks.length; i++) {
+    var b = blocks[i].trim();
+    if (/^(resolve|conflict|disagree)/i.test(b) || /^\d+\.\s*(resolve|conflict)/i.test(b)) {
+      resolutions.push(b.slice(0, 300));
+    }
+  }
+  return resolutions;
+}
+
 module.exports = {
   synthesize: synthesize,
   buildSynthesisPrompt: buildSynthesisPrompt,
   hasContradictions: hasContradictions,
+  extractPremiseCheck: extractPremiseCheck,
+  extractConflictResolutions: extractConflictResolutions,
 };