@polymorphism-tech/morph-spec 4.10.10 → 4.11.0

package/framework/skills/level-1-workflows/morph-phase-implement/prompts/implementer-prompt.md

@@ -20,7 +20,7 @@ You are implementing tasks for the feature '{{FEATURE_NAME}}' as agent '{{AGENT_
 ## Execution Rules
 
 1. Before starting each task:
-   - Execute: `npx morph-spec task start {{FEATURE_NAME}} {{TASK_ID}}`
+   - Execute: `morph-spec task start {{FEATURE_NAME}} {{TASK_ID}}`
 
 2. For each task, follow TDD:
    - Write the failing test first
@@ -32,11 +32,11 @@ You are implementing tasks for the feature '{{FEATURE_NAME}}' as agent '{{AGENT_
 3. Before marking any task done:
    - Verify build compiles: `dotnet build` or `npm run build`
    - Run relevant tests
-   - Execute: `npx morph-spec task done {{FEATURE_NAME}} {{TASK_ID}}`
+   - Execute: `morph-spec task done {{FEATURE_NAME}} {{TASK_ID}}`
 
 4. Every 3 tasks:
-   - Execute: `npx morph-spec checkpoint-save {{FEATURE_NAME}}`
-   - Execute: `npx morph-spec validate-feature {{FEATURE_NAME}} --phase implement`
+   - Execute: `morph-spec checkpoint-save {{FEATURE_NAME}}`
+   - Execute: `morph-spec validate-feature {{FEATURE_NAME}} --phase implement`
 
 5. Contracts are the source of truth — all DTOs, interfaces, and types MUST match `contracts.cs` exactly
 

package/framework/skills/level-1-workflows/morph-phase-plan/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Plan). Generates a detailed implementation plan
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.10"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Plan — Phase 4
@@ -28,8 +28,8 @@ Generate a detailed implementation plan with exact paths, TDD code, and executio
 | Read spec + contracts + decisions | **Read** all outputs | — |
 | Analyze existing codebase | **Glob** + **Grep** patterns | — |
 | Look up library docs | **Context7 MCP** `query_docs()` | **WebSearch** |
-| Dispatch agents for analysis | **Bash** `npx morph-spec dispatch-agents $ARGUMENTS plan` | — |
-| Update state | **Bash** `npx morph-spec state mark-output $ARGUMENTS plan` | — |
+| Dispatch agents for analysis | **Bash** `morph-spec dispatch-agents $ARGUMENTS plan` | — |
+| Update state | **Bash** `morph-spec state mark-output $ARGUMENTS plan` | — |
 
 **Anti-patterns:**
 - Generating plan without reading contracts (contracts are the source of truth!)
@@ -45,12 +45,12 @@ Generate a detailed implementation plan with exact paths, TDD code, and executio
 ### 0. Ensure plan phase
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field:
 - `"phase": "plan"` → correct phase, proceed
-- any other value → run `npx morph-spec phase advance $ARGUMENTS` and re-check
+- any other value → run `morph-spec phase advance $ARGUMENTS` and re-check
 
 > **Rule:** Never write to `3-plan/` until the phase is `plan`.
 
@@ -101,7 +101,7 @@ cat .morph/config/config.json | grep -A3 '"architecture"'
 Run the dispatch analysis:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS plan
+morph-spec dispatch-agents $ARGUMENTS plan
 ```
 
 **Factors for recommendation:**
@@ -185,7 +185,7 @@ git commit -m "{message}"
 ### Step 4: Update State
 
 ```bash
-npx morph-spec state mark-output $ARGUMENTS plan
+morph-spec state mark-output $ARGUMENTS plan
 ```
 
 ---
@@ -224,8 +224,8 @@ Use `AskUserQuestion` to capture approval before advancing. This gate prevents t
 
 - **"Approve plan"** →
   ```bash
-  npx morph-spec approve $ARGUMENTS plan
-  npx morph-spec phase advance $ARGUMENTS
+  morph-spec approve $ARGUMENTS plan
+  morph-spec phase advance $ARGUMENTS
   ```
 - **"I have feedback" or "Other"** → apply the feedback and repeat this PAUSE
 

package/framework/skills/level-1-workflows/morph-phase-setup/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech sta
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.10"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Setup — Phase 1
@@ -26,19 +26,19 @@ Initialize the context and prepare the environment for an approved feature.
 
 | Action | Tool | Alternative |
 |--------|------|-------------|
-| Verify state | **Bash** `npx morph-spec state get` | — |
-| Detect agents + standards | **Bash** `npx morph-spec detect-agents $ARGUMENTS --json` → parse → **Bash** `npx morph-spec state add-agent` | **Read** agents.json manually |
+| Verify state | **Bash** `morph-spec state get` | — |
+| Detect agents + standards | **Bash** `morph-spec detect-agents $ARGUMENTS --json` → parse → **Bash** `morph-spec state add-agent` | **Read** agents.json manually |
 | Read project context | **Read** `.morph/context/README.md` | — |
 | Read config | **Read** `.morph/config/config.json` | — |
 | Detect VSA architecture | **Read** `.morph/config/config.json` → check `config.architecture.style` | — |
 | Scan project structure | **Glob** `src/**/*.{ts,tsx,cs}` | — |
 | Repository metadata | **GitHub MCP** `get_repo()` | **Bash** `gh repo view --json` |
-| Update state | **Bash** `npx morph-spec state set` | — |
+| Update state | **Bash** `morph-spec state set` | — |
 
 **MCPs for this phase:** GitHub (optional — repo metadata).
 
 **Anti-patterns:**
-- Do not read agents.json manually for keyword matching — use `npx morph-spec detect-agents` CLI
+- Do not read agents.json manually for keyword matching — use `morph-spec detect-agents` CLI
 - Do not use a Task agent for agent detection (CLI is faster and consistent)
 - Do not use WebSearch for local project info (use Read/Glob)
 
@@ -76,7 +76,7 @@ Update each task to `in_progress` before its step and `completed` after.
 Read these files first — they inform all subsequent decisions:
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 If the feature doesn't exist in state, go back to Phase 0.
@@ -93,8 +93,8 @@ Read `.morph/config/config.json` and check `config.architecture.style`:
 
 | Value | Action |
 |-------|--------|
-| `"vertical-slice"` | `npx morph-spec state add-agent $ARGUMENTS vsa-architect` |
-| absent / any other value | `npx morph-spec state add-agent $ARGUMENTS domain-architect` |
+| `"vertical-slice"` | `morph-spec state add-agent $ARGUMENTS vsa-architect` |
+| absent / any other value | `morph-spec state add-agent $ARGUMENTS domain-architect` |
 
 Proceed with normal keyword detection for all other agents. The architect was already added above — skip it during keyword matching to avoid duplication.
 
@@ -103,7 +103,7 @@ Proceed with normal keyword detection for all other agents. The architect was al
 Use the `detect-agents` CLI to match agent keywords against the proposal (excludes architects already handled in Step 2.0):
 
 ```bash
-npx morph-spec detect-agents $ARGUMENTS --exclude domain-architect,vsa-architect --json
+morph-spec detect-agents $ARGUMENTS --exclude domain-architect,vsa-architect --json
 ```
 
 This reads the proposal from `.morph/features/$ARGUMENTS/0-proposal/proposal.md` and agents.json, returning JSON with `detected[]` and `skipped[]` arrays. Agents with `active_phases: ['*']` are always included.
@@ -111,7 +111,7 @@ This reads the proposal from `.morph/features/$ARGUMENTS/0-proposal/proposal.md`
 Parse the JSON output and add each detected agent to state:
 
 ```bash
-npx morph-spec state add-agent $ARGUMENTS {agent-id}
+morph-spec state add-agent $ARGUMENTS {agent-id}
 ```
 
 Run `add-agent` once per detected agent ID from the `detected[]` array.
@@ -156,7 +156,7 @@ Use `AskUserQuestion` with header `"{MCP}"` and options:
 
 **4. For MCPs RECOMMENDED but NOT CONFIGURED:**
 - Print `△ {MCP} — not configured (fallback: {registry.fallback})`
-- Suggestion: `Tip: configure with /morph-init refresh or npx morph-spec mcp setup`
+- Suggestion: `Tip: configure with /morph-init refresh or morph-spec mcp setup`
 
 **Summary:** Show a status table for each MCP before proceeding:
 ```
@@ -173,15 +173,15 @@ MCP Readiness:
 Run a quick check to verify all expected agents are installed for this project's stack:
 
 ```bash
-npx morph-spec doctor 2>&1 | grep -A 1 "agents completeness"
+morph-spec doctor 2>&1 | grep -A 1 "agents completeness"
 ```
 
 If the output shows **missing agents**, inform the user:
 
-> ⚠ Some agents for your stack are not installed. Run `npx morph-spec setup-infra` to install them.
+> ⚠ Some agents for your stack are not installed. Run `morph-spec setup-infra` to install them.
 
 Use `AskUserQuestion` with header `"Agents"` and options:
-- **Install now** — run `npx morph-spec setup-infra` to reinstall with current stack tags
+- **Install now** — run `morph-spec setup-infra` to reinstall with current stack tags
 - **Continue without** — proceed with available agents (may lack specialized support)
 
 If "Install now" is selected, run the command and continue.
@@ -200,7 +200,7 @@ Based on the proposal and context, confirm:
 Show the agents detected from the proposal:
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Parse the JSON and list `activeAgents` with their emojis/icons and responsibilities (look up each agent in `.morph/framework/agents.json` for the `icon` field).
@@ -208,7 +208,7 @@ Parse the JSON and list `activeAgents` with their emojis/icons and responsibilit
 **If there are 2+ specialist agents active**, show the dispatch plan for the next phase:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS design
+morph-spec dispatch-agents $ARGUMENTS design
 ```
 
 This shows which agents will be dispatched in parallel during the design phase and which tasks they'll execute.
@@ -222,7 +222,7 @@ This shows which agents will be dispatched in parallel during the design phase a
 Update the feature state:
 
 ```bash
-npx morph-spec state set $ARGUMENTS status in_progress
+morph-spec state set $ARGUMENTS status in_progress
 ```
 
 **Determine the next phase** based on active agents:

package/framework/skills/level-1-workflows/morph-phase-tasks/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ord
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.10"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Tasks — Phase 4
@@ -33,8 +33,8 @@ Break the approved specification into executable tasks, define execution order,
 | Count similar existing patterns | **Glob** `**/Services/**/*.cs` | — |
 | Look up implementation patterns | **Context7 MCP** `query_docs()` | **WebSearch** |
 | Create GitHub issues from tasks | **GitHub MCP** `create_issue()` | **Bash** `gh issue create ...` |
-| Render tasks template | **Bash** `npx morph-spec template render docs/tasks ...` | — |
-| Update state with task count | **Bash** `npx morph-spec state set ... tasks.total N` | — |
+| Render tasks template | **Bash** `morph-spec template render docs/tasks ...` | — |
+| Update state with task count | **Bash** `morph-spec state set ... tasks.total N` | — |
 
 **Phase MCPs:** Context7 (estimate complexity), GitHub (create issues).
 
@@ -54,7 +54,7 @@ Break the approved specification into executable tasks, define execution order,
 ### 0. Ensure tasks phase
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field:
@@ -62,8 +62,8 @@ Check the `"phase"` field:
 **If `"phase": "tasks"`** → correct phase, proceed.
 
 **If `"phase": "clarify"`** → run in sequence:
-1. `npx morph-spec state mark-output $ARGUMENTS clarifications`
-2. `npx morph-spec phase advance $ARGUMENTS` (→ tasks)
+1. `morph-spec state mark-output $ARGUMENTS clarifications`
+2. `morph-spec phase advance $ARGUMENTS` (→ tasks)
 
 **Any other value** → STOP — inconsistent state, report to user.
 
@@ -114,8 +114,8 @@ Before starting the breakdown:
 If any checkbox is NOT checked → return to corresponding phase and resolve.
 
 ```bash
-npx morph-spec state get $ARGUMENTS
-npx morph-spec approval-status $ARGUMENTS
+morph-spec state get $ARGUMENTS
+morph-spec approval-status $ARGUMENTS
 ```
 
 ---
@@ -245,8 +245,8 @@ If there are Azure resources, add Bicep and migration tasks.
 ### Step 8: Update State
 
 ```bash
-npx morph-spec state set $ARGUMENTS tasks.total {N}
-npx morph-spec state mark-output $ARGUMENTS tasks
+morph-spec state set $ARGUMENTS tasks.total {N}
+morph-spec state mark-output $ARGUMENTS tasks
 ```
 
 ## Outputs
@@ -273,8 +273,8 @@ Use `AskUserQuestion` to capture explicit approval before advancing. This gate p
 
 - **"Approve and implement"** →
   ```bash
-  npx morph-spec approve $ARGUMENTS tasks
-  npx morph-spec phase advance $ARGUMENTS
+  morph-spec approve $ARGUMENTS tasks
+  morph-spec phase advance $ARGUMENTS
   ```
 - **"I have feedback" or "Other"** → apply the feedback and repeat this PAUSE
 

package/framework/skills/level-1-workflows/morph-phase-uiux/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md,
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.10"
+cliVersion: "4.11.0"
 ---
 
 # MORPH UI/UX Design - Phase 1.5
@@ -36,9 +36,9 @@ Conditional phase for features with front-end. Collects UI/UX requirements, gene
 | Inspect page structure | **Playwright MCP** `browser_snapshot()` | **WebFetch** + manual parse |
 | Test responsive layout | **Playwright MCP** `browser_resize()` + `browser_take_screenshot()` | Manual testing |
 | External design references | **WebSearch** + **WebFetch** | — |
-| Render UI templates | **Bash** `npx morph-spec template render docs/ui-mockups ...` | — |
-| Generate design system from existing CSS | **Bash** `npx morph-spec generate design-system --scan` | — |
-| Update state | **Bash** `npx morph-spec state mark-output ...` | — |
+| Render UI templates | **Bash** `morph-spec template render docs/ui-mockups ...` | — |
+| Generate design system from existing CSS | **Bash** `morph-spec generate design-system --scan` | — |
+| Update state | **Bash** `morph-spec state mark-output ...` | — |
 
 **MCPs for this phase:** Playwright (preview, inspection, responsiveness), Context7 (component docs).
 
@@ -54,7 +54,7 @@ Conditional phase for features with front-end. Collects UI/UX requirements, gene
 ### Step 0: Ensure uiux phase
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field in the output:
@@ -62,7 +62,7 @@ Check the `"phase"` field in the output:
 **If `"phase": "uiux"`** → correct phase, proceed.
 
 **If `"phase": "setup"`** → execute:
-1. `npx morph-spec phase advance $ARGUMENTS` (→ uiux)
+1. `morph-spec phase advance $ARGUMENTS` (→ uiux)
 
 **Any other value** → do not proceed — inconsistent state, report to user.
 
@@ -134,7 +134,7 @@ Print: `✓ Design system generated from [N] tokens — .morph/context/design-sy
 Check if active agents include `ui-designer`:
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 If `ui-designer` is NOT in `activeAgents`, skip this phase and continue to Phase 2 (Design).
@@ -290,7 +290,7 @@ mcp__plugin_playwright_playwright__browser_take_screenshot({}) → save as .morp
 
 Create the following files in `.morph/features/$ARGUMENTS/`:
 
-> **Use templates:** Use `npx morph-spec template render` to generate files from templates in `.morph/framework/templates/docs/`. Available templates: `ui-design-system`, `ui-mockups`, `ui-components`, `ui-flows`.
+> **Use templates:** Use `morph-spec template render` to generate files from templates in `.morph/framework/templates/docs/`. Available templates: `ui-design-system`, `ui-mockups`, `ui-components`, `ui-flows`.
 
 #### 4.1. `ui-design-system.md`
 
@@ -367,17 +367,17 @@ Document in UI files:
 ### Step 6: Update State
 
 ```bash
-npx morph-spec state mark-output $ARGUMENTS ui-design-system
-npx morph-spec state mark-output $ARGUMENTS ui-mockups
-npx morph-spec state mark-output $ARGUMENTS ui-components
-npx morph-spec state mark-output $ARGUMENTS ui-flows
+morph-spec state mark-output $ARGUMENTS ui-design-system
+morph-spec state mark-output $ARGUMENTS ui-mockups
+morph-spec state mark-output $ARGUMENTS ui-components
+morph-spec state mark-output $ARGUMENTS ui-flows
 ```
 
 > **Format note:** The `mark-output` commands accept BOTH kebab-case (`ui-design-system`)
 > AND camelCase (`uiDesignSystem`). Both formats work equally! Use whichever is more
 > comfortable for you. Examples:
-> - `npx morph-spec state mark-output my-feature uiDesignSystem`
-> - `npx morph-spec state mark-output my-feature ui-design-system`
+> - `morph-spec state mark-output my-feature uiDesignSystem`
+> - `morph-spec state mark-output my-feature ui-design-system`
 
 ## Generated Outputs
 
@@ -421,8 +421,8 @@ Use `AskUserQuestion` to capture explicit approval before advancing:
 
 - **"Approve UI/UX"** →
   ```bash
-  npx morph-spec approve $ARGUMENTS uiux
-  npx morph-spec phase advance $ARGUMENTS
+  morph-spec approve $ARGUMENTS uiux
+  morph-spec phase advance $ARGUMENTS
   ```
 - **"I have feedback" or "Other"** → apply the received feedback and repeat this PAUSE
 

package/framework/skills/level-1-workflows/morph-scope-escalation/SKILL.md

@@ -4,7 +4,7 @@ description: Guided workflow for mid-implementation scope escalation — analyze
 user-invocable: true
 argument-hint: "[feature-name]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.10"
+cliVersion: "4.11.0"
 ---
 
 # Scope Escalation Workflow
@@ -57,7 +57,7 @@ Use `AskUserQuestion` to gather the details:
 Run dry-run analysis:
 
 ```bash
-npx morph-spec scope escalate <feature> --task <id> --reason "<reason>" --dry-run
+morph-spec scope escalate <feature> --task <id> --reason "<reason>" --dry-run
 ```
 
 Read the recommendation output. Additionally:
@@ -116,17 +116,17 @@ Based on approved action:
 
 **For expansion (low impact):**
 ```bash
-npx morph-spec task expand <feature> <task-id> --into "T017a: <title>" "T017b: <title>" ...
+morph-spec task expand <feature> <task-id> --into "T017a: <title>" "T017b: <title>" ...
 ```
 
 **For regression (medium/high impact):**
 ```bash
-npx morph-spec scope escalate <feature> --task <id> --reason "<reason>"
+morph-spec scope escalate <feature> --task <id> --reason "<reason>"
 ```
 
 Or with target override:
 ```bash
-npx morph-spec scope escalate <feature> --task <id> --reason "<reason>" --target design
+morph-spec scope escalate <feature> --task <id> --reason "<reason>" --target design
 ```
 
 ### Step 6: GUIDE Next Steps

package/framework/workflows/README.md

@@ -371,7 +371,7 @@ Keywords like: `bicep`, `azure`, `deploy`, `docker`, `kubernetes`, `infrastructu
 
 ```bash
 # When creating a feature
-npx morph-spec feature create user-pagination \
+morph-spec feature create user-pagination \
   --request "add pagination to users table"
 
 # System automatically:
@@ -385,7 +385,7 @@ npx morph-spec feature create user-pagination \
 
 ```bash
 # Analyze request without creating feature
-npx morph-spec detect-workflow "implement complete authentication system"
+morph-spec detect-workflow "implement complete authentication system"
 
 # Output:
 Detected Workflow: full-morph (92% confidence)
@@ -407,7 +407,7 @@ Alternative Workflows:
 ### JSON Output (for automation)
 
 ```bash
-npx morph-spec detect-workflow "add pagination" --json
+morph-spec detect-workflow "add pagination" --json
 
 # Output:
 {
@@ -435,17 +435,17 @@ npx morph-spec detect-workflow "add pagination" --json
 
 ```bash
 # Force specific workflow
-npx morph-spec state set user-auth workflow full-morph
+morph-spec state set user-auth workflow full-morph
 
 # Re-detect after request changes
-npx morph-spec state detect-workflow user-auth \
+morph-spec state detect-workflow user-auth \
   "implement basic login only (no OAuth)"
 ```
 
 ### View Current Workflow
 
 ```bash
-npx morph-spec state get user-auth workflow
+morph-spec state get user-auth workflow
 
 # Output:
 Workflow: standard
@@ -594,7 +594,7 @@ Create `framework/workflows/docs/my-workflow.md` explaining the workflow.
 **3. Test Detection:**
 
 ```bash
-npx morph-spec detect-workflow "request with custom-keyword"
+morph-spec detect-workflow "request with custom-keyword"
 ```
 
 ### Modifying Existing Workflows
@@ -675,7 +675,7 @@ Phases: Quick Analysis → Implement
 
 **User Experience:**
 ```bash
-npx morph-spec feature create login-typo --request "fix typo in login button"
+morph-spec feature create login-typo --request "fix typo in login button"
 
 # Output:
 ✓ Detected workflow: fast-track
@@ -683,7 +683,7 @@ npx morph-spec feature create login-typo --request "fix typo in login button"
 📝 Write quick analysis (1 paragraph) and implement
 
 # User writes quick analysis, then:
-npx morph-spec phase advance login-typo
+morph-spec phase advance login-typo
 
 # Output:
 ⏩ Skipping: setup, uiux, design, clarify, tasks, sync
@@ -704,7 +704,7 @@ Phases: PROPOSAL → DESIGN → TASKS → IMPLEMENT
 
 **User Experience:**
 ```bash
-npx morph-spec feature create user-pagination \
+morph-spec feature create user-pagination \
   --request "add pagination to users table"
 
 # Output:
@@ -727,7 +727,7 @@ Phases: ALL (9 phases mandatory)
 
 **User Experience:**
 ```bash
-npx morph-spec feature create user-auth \
+morph-spec feature create user-auth \
   --request "implement complete authentication system with OAuth"
 
 # Output:
@@ -750,7 +750,7 @@ Phases: PROTOTYPE ANALYSIS → TASKS → IMPLEMENT
 
 **User Experience:**
 ```bash
-npx morph-spec feature create dashboard-screens \
+morph-spec feature create dashboard-screens \
   --request "implement screens from Figma design"
 
 # Output:
@@ -774,7 +774,7 @@ Phases: VISUAL ANALYSIS → DESIGN SYSTEM → IMPLEMENT
 
 **User Experience:**
 ```bash
-npx morph-spec feature create dashboard-redesign \
+morph-spec feature create dashboard-redesign \
   --request "redesign dashboard to look more modern"
 
 # Output:
@@ -794,13 +794,13 @@ npx morph-spec feature create dashboard-redesign \
 
 **Solution 1: Provide more context**
 ```bash
-npx morph-spec feature create simple-fix \
+morph-spec feature create simple-fix \
   --request "add pagination (simple, already have paginator component)"
 ```
 
 **Solution 2: Manual override**
 ```bash
-npx morph-spec state set my-feature workflow standard
+morph-spec state set my-feature workflow standard
 ```
 
 **Solution 3: Improve keywords**
@@ -849,7 +849,7 @@ If this happens often, add keywords to workflow config:
 **Alternative:**
 Use `detect-workflow` first to see both options:
 ```bash
-npx morph-spec detect-workflow "add authentication"
+morph-spec detect-workflow "add authentication"
 
 # Review both workflows
 # Decide based on:
@@ -891,13 +891,13 @@ Create `framework/workflows/configs/blazor-standard.json`:
 **Solution 1: Force phase**
 ```bash
 # Manually go to UIUX phase
-npx morph-spec phase set my-feature uiux
+morph-spec phase set my-feature uiux
 ```
 
 **Solution 2: Override workflow**
 ```bash
 # Use full-morph (includes all phases)
-npx morph-spec state set my-feature workflow full-morph
+morph-spec state set my-feature workflow full-morph
 ```
 
 **Solution 3: Document in decisions.md**

package/framework/workflows/docs/enforcement-pipeline.md

@@ -113,7 +113,7 @@ export function loadStandardsForAgent(agentId, projectPath) {
 
 ```bash
 # Standards auto-injected when running detect-agents with --json
-npx morph-spec detect-agents --json "create blazor dashboard"
+morph-spec detect-agents --json "create blazor dashboard"
 
 # Output includes standardsSummary for each agent:
 {

package/framework/workflows/docs/full-morph.md

@@ -18,7 +18,7 @@
 6. Ativar agentes baseado em stack + keywords
 
 ### FASE 0: PROPOSAL
-1. `npx morph-spec detect "{user-request}"`
+1. `morph-spec detect "{user-request}"`
 2. Analisar solicitação, identificar stack, estimar complexidade
 3. Gerar proposal.md, registrar agentes no state.json
 - **⛔ PAUSA:** 3 itens (1 ação + 1 pergunta + 1 sugestão)
@@ -55,7 +55,7 @@
 
 ### FASE 5: IMPLEMENT
 1. Implementar task por task
-2. `npx morph-spec task done {feature} {task-id}` após cada task
+2. `morph-spec task done {feature} {task-id}` após cada task
 3. Framework gerencia checkpoints automaticamente (a cada 3 tasks)
 4. Gerar recap.md ao final
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "4.10.10",
+  "version": "4.11.0",
   "description": "MORPH-SPEC: AI-First development framework with validation pipeline and multi-stack support",
   "keywords": [
     "claude-code",

package/src/commands/project/doctor.js

@@ -947,13 +947,12 @@ export async function doctorCommand(options = {}) {
         logger.dim('  PowerShell (as Administrator):');
         console.log(chalk.gray(`    [Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";${prefix}", "User")`));
         logger.blank();
-        logger.dim('  Or use npx instead:');
-        logger.dim('    npx @polymorphism-tech/morph-spec init');
+        logger.dim('  Then open a new terminal.');
         logger.blank();
       } else if (!inPath) {
         logger.info('morph-spec not in PATH:');
-        logger.dim('  Use npx instead:');
-        logger.dim('    npx @polymorphism-tech/morph-spec init');
+        logger.dim('  Open a new terminal — the installer adds npm global to $PROFILE automatically.');
+        logger.dim('  If it persists, add manually: npm config get prefix → add to PATH');
         logger.blank();
       }
     }

package/src/commands/project/status.js

@@ -236,7 +236,14 @@ export async function statusCommand(featureName, options = {}) {
     process.exit(1);
   }
 
-  const feature = getFeature(featureName);
+  let feature;
+  try {
+    feature = getFeature(featureName);
+  } catch (err) {
+    console.error(chalk.red(`✗ Error: ${err.message}`));
+    console.error(chalk.gray('Run \'morph-spec doctor\' to diagnose or fix your state.json'));
+    process.exit(1);
+  }
   if (!feature) {
     console.error(chalk.red(`✗ Error: Feature '${featureName}' not found`));
     console.error(chalk.gray(`Run 'morph-spec state get ${featureName}' to check if feature exists`));

package/src/commands/scope/escalate.js

@@ -13,7 +13,7 @@
 import chalk from 'chalk';
 import { readFileSync, writeFileSync, existsSync, mkdirSync } from 'fs';
 import { join } from 'path';
-import { loadState, saveState } from '../../core/state/state-manager.js';
+import { loadState, saveState, derivePhase } from '../../core/state/state-manager.js';
 import { analyzeImpact } from '../../lib/scope/impact-analyzer.js';
 
 /**
@@ -35,8 +35,10 @@ export async function escalateScope(featureName, options) {
     return { success: false, error: `Feature "${featureName}" not found in state.json` };
   }
 
-  if (feature.phase !== 'implement') {
-    return { success: false, error: `Scope escalation only available during implement phase (current: ${feature.phase})` };
+  const featurePath = join(process.cwd(), '.morph', 'features', featureName);
+  const currentPhase = feature.phase || derivePhase(featurePath);
+  if (currentPhase !== 'implement') {
+    return { success: false, error: `Scope escalation only available during implement phase (current: ${currentPhase})` };
   }
 
   // Read tasks.md