@polymorphism-tech/morph-spec 4.10.10 → 4.11.0

package/README.md

@@ -3,7 +3,7 @@
 > Spec-driven development framework for multi-stack projects. Turns feature requests into implementation-ready code through structured, AI-orchestrated phases.
 
 **Package:** `@polymorphism-tech/morph-spec`
-**Version:** 4.10.10  
+**Version:** 4.11.0  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -312,17 +312,11 @@ After updating, run `morph-spec doctor` to confirm the installation is healthy.
 
 ### `morph-spec: command not found`
 
-If you are using nvm-windows or a Node version manager, the global bin path may not be on `PATH` in your shell. Use `npx` instead:
-
-```bash
-npx @polymorphism-tech/morph-spec init
-```
-
-Or add the npm global bin to your PATH:
+The installer automatically adds the npm global directory to your PowerShell `$PROFILE`. Open a **new terminal** after installing. If it still doesn't work, add it manually:
 
 ```bash
 npm config get prefix
-# Add {prefix}/bin to your PATH
+# Add {prefix} to your PATH
 ```
 
 ### `morph-spec doctor` reports issues
@@ -354,7 +348,7 @@ npm config set prefix %APPDATA%\npm-global
 npm install -g @polymorphism-tech/morph-spec
 ```
 
-1. Use `npx` for all CLI invocations
+1. Open a new terminal (the installer adds npm to your PATH automatically)
 
 ### Hook not triggering on SessionStart
 
@@ -376,4 +370,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.10.10 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.11.0 by [Polymorphism Tech](https://polymorphism.tech)*

package/bin/morph-spec.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 import { program } from 'commander';
 import chalk from 'chalk';

package/bin/task-manager.js

@@ -408,7 +408,7 @@ class TaskManager {
       // This is fail-open by design: a broken validator shouldn't block commits.
       // Common cause: missing optional deps.
       console.log(chalk.yellow(`\n⚠️  Validation skipped (${error.message})`));
-      console.log(chalk.gray(`   Run manually: npx morph-spec validate-feature ${featureName}`));
+      console.log(chalk.gray(`   Run manually: morph-spec validate-feature ${featureName}`));
       return { passed: true, validators: {}, passRate: 1.0 };
     }
   }
@@ -850,7 +850,7 @@ async function main() {
         const taskIds = filteredArgs.slice(2);
 
         if (!featureName || taskIds.length === 0) {
-          console.error(chalk.red('Usage: npx morph-spec task done <feature> <task-id> [task-id...] [--skip-validation] [--dry-run]'));
+          console.error(chalk.red('Usage: morph-spec task done <feature> <task-id> [task-id...] [--skip-validation] [--dry-run]'));
           process.exit(1);
         }
 
@@ -870,7 +870,7 @@ async function main() {
         const rangeArg = filteredArgs[2]; // e.g. T001..T082
 
         if (!featureName) {
-          console.error(chalk.red('Usage: npx morph-spec task bulk-done <feature> [--all | --from T001 --to T053 | T001..T082] [--skip-validation] [--dry-run]'));
+          console.error(chalk.red('Usage: morph-spec task bulk-done <feature> [--all | --from T001 --to T053 | T001..T082] [--skip-validation] [--dry-run]'));
           process.exit(1);
         }
 
@@ -886,7 +886,7 @@ async function main() {
         const taskId = args[2];
 
         if (!featureName || !taskId) {
-          console.error(chalk.red('Usage: npx morph-spec task start <feature> <task-id>'));
+          console.error(chalk.red('Usage: morph-spec task start <feature> <task-id>'));
           process.exit(1);
         }
 
@@ -898,7 +898,7 @@ async function main() {
         const featureName = args[1];
 
         if (!featureName) {
-          console.error(chalk.red('Usage: npx morph-spec task next <feature>'));
+          console.error(chalk.red('Usage: morph-spec task next <feature>'));
           process.exit(1);
         }
 

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.10.10",
+  "version": "4.11.0",
   "displayName": "MORPH-SPEC Framework",
   "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
   "publisher": "polymorphism-tech",

package/docs/CHEATSHEET.md

@@ -198,4 +198,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.10.10 by Polymorphism Tech*
+*morph-spec v4.11.0 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -6,13 +6,7 @@
 npm install -g @polymorphism-tech/morph-spec
 ```
 
-Or use `npx` without a global install:
-
-```bash
-npx @polymorphism-tech/morph-spec init
-```
-
-> **Windows / nvm-windows:** Global installs may not appear on PATH. Use `npx` or add the npm prefix to PATH manually: `npm config get prefix`, then add `{prefix}` to your PATH.
+> The installer automatically configures your PowerShell PATH on Windows. If `morph-spec` is not found, open a new terminal window.
 
 ---
 
@@ -203,4 +197,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.10.10 by Polymorphism Tech*
+*morph-spec v4.11.0 by Polymorphism Tech*

package/framework/agents/frontend/css-specialist.md

@@ -67,7 +67,7 @@ When reviewing CSS:
 
 If project already has CSS variables, scan them:
 ```bash
-npx morph-spec generate design-system --scan
+morph-spec generate design-system --scan
 ```
 
 This extracts existing `:root { --var: value }` declarations and populates design-system.md.

package/framework/agents/infrastructure/azure-deploy-specialist.md

@@ -220,7 +220,7 @@ Por favor, forneca os valores abaixo. Serao armazenados de forma segura.
 
 ```bash
 # Validar custos antes de deploy
-npx morph-spec cost infra/main.bicep --verbose
+morph-spec cost infra/main.bicep --verbose
 
 # Se custo > limite configurado:
 # 1. PARAR deployment
@@ -563,7 +563,7 @@ Para uso em pipelines Azure DevOps:
 
 ```bash
 # Uso automatico (sem pausas interativas)
-npx morph-spec deploy prod --auto \
+morph-spec deploy prod --auto \
   --sql-password "$(SQL_PASSWORD)" \
   --tenant-id "$(TENANT_ID)" \
   --client-secret "$(CLIENT_SECRET)" \
@@ -622,7 +622,7 @@ stages:
             deploy:
               steps:
                 - script: |
-                    npx morph-spec deploy dev --auto \
+                    morph-spec deploy dev --auto \
                       --sql-password "$(SqlPassword)" \
                       --skip-confirmation
                   displayName: 'Deploy to Dev'
@@ -638,7 +638,7 @@ stages:
             deploy:
               steps:
                 - script: |
-                    npx morph-spec deploy prod --auto \
+                    morph-spec deploy prod --auto \
                       --sql-password "$(SqlPasswordProd)" \
                       --skip-confirmation
                   displayName: 'Deploy to Prod'

package/framework/commands/morph-apply.md

@@ -23,10 +23,10 @@ Implement the feature by executing its task breakdown, tracking progress through
 |--------|------|-------------|
 | Read spec, tasks, contracts | **Read** all outputs | — |
 | Detect architecture style | **Bash** `cat .morph/config/config.json \| grep architecture` | — |
-| Agent dispatch config | **Bash** `npx morph-spec dispatch-agents $ARGUMENTS implement` | — |
+| Agent dispatch config | **Bash** `morph-spec dispatch-agents $ARGUMENTS implement` | — |
 | Parallel task execution | **Agent** subagent per task group | Sequential fallback |
 | Look up implementation patterns | **Context7 MCP** `query_docs()` | **WebSearch** |
-| Track progress | **Bash** `npx morph-spec state get $ARGUMENTS` | — |
+| Track progress | **Bash** `morph-spec state get $ARGUMENTS` | — |
 
 ---
 
@@ -37,9 +37,9 @@ Before writing any code, verify all prior phases are complete. This gate prevent
 ### 1. Check state and approvals
 
 ```bash
-npx morph-spec state get $ARGUMENTS
-npx morph-spec approval-status $ARGUMENTS
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec state get $ARGUMENTS
+morph-spec approval-status $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 ```
 
 **All three must pass.** If any fails:
@@ -87,13 +87,13 @@ cat .morph/config/config.json | grep -A3 '"architecture"'
 ### 4. Get agent dispatch config
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement --table
+morph-spec dispatch-agents $ARGUMENTS implement --table
 ```
 
 This shows which agents are active for implementation and how tasks can be grouped. If agent teams are enabled and tasks have no dependencies between groups, consider dispatching parallel agents:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement
+morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
 The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for multi-agent coordination.
@@ -105,7 +105,7 @@ The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for mult
 ### Step 1: Advance to implement phase
 
 ```bash
-npx morph-spec phase advance $ARGUMENTS
+morph-spec phase advance $ARGUMENTS
 ```
 
 This validates phase eligibility and emits a SKILL DISPATCH block listing required skills for implementation (verification-before-completion, morph-checklist, etc.).
@@ -113,7 +113,7 @@ This validates phase eligibility and emits a SKILL DISPATCH block listing requir
 ### Step 2: Initialize state tracking
 
 ```bash
-npx morph-spec state set $ARGUMENTS tasks.total {N}
+morph-spec state set $ARGUMENTS tasks.total {N}
 ```
 
 Where `{N}` is the number of tasks in tasks.md (e.g., 6 for T001-T006).
@@ -124,7 +124,7 @@ For each task in the breakdown, follow this cycle:
 
 ```bash
 # 1. Start the task (activates task-tracking guard)
-npx morph-spec task start $ARGUMENTS {task-id}
+morph-spec task start $ARGUMENTS {task-id}
 
 # 2. Implement the task
 #    - Follow spec.md and contracts
@@ -136,7 +136,7 @@ npx morph-spec task start $ARGUMENTS {task-id}
 #    matches the spec and contracts before marking done
 
 # 4. Complete the task (triggers Tier-4 validators automatically)
-npx morph-spec task done $ARGUMENTS {task-id}
+morph-spec task done $ARGUMENTS {task-id}
 ```
 
 **If validation fails on `task done`:**
@@ -153,8 +153,8 @@ If `dispatch-agents` identified parallelizable task groups and agent teams are e
 After every 3 completed tasks, save a checkpoint:
 
 ```bash
-npx morph-spec checkpoint-save $ARGUMENTS "after-T003"
-npx morph-spec state get $ARGUMENTS
+morph-spec checkpoint-save $ARGUMENTS "after-T003"
+morph-spec state get $ARGUMENTS
 ```
 
 Checkpoints validate architecture compliance, check package versions, scan for security issues, and save a restorable snapshot. The cadence is every 3 tasks — for 6 tasks: checkpoint after T003 and T006. For 10 tasks: after T003, T006, T009, and at completion.
@@ -162,7 +162,7 @@ Checkpoints validate architecture compliance, check package versions, scan for s
 After each checkpoint, check progress:
 
 ```bash
-npx morph-spec state list
+morph-spec state list
 ```
 
 ### Step 5: Finalize implementation
@@ -171,16 +171,16 @@ After all tasks are complete:
 
 ```bash
 # Final validation
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 
 # Generate recap (auto-marks 'recap' output in state)
-npx morph-spec generate recap $ARGUMENTS
+morph-spec generate recap $ARGUMENTS
 
 # Verify final state
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 
 # Advance to next phase
-npx morph-spec phase advance $ARGUMENTS
+morph-spec phase advance $ARGUMENTS
 ```
 
 ### Step 6: Post-implementation review

package/framework/commands/morph-preflight.md

@@ -26,9 +26,9 @@ These checks verify that the morph-spec workflow is complete for the feature bei
 
 ```bash
 # Verify implementation is complete
-npx morph-spec state get {feature}
-npx morph-spec approval-status {feature}
-npx morph-spec validate-feature {feature}
+morph-spec state get {feature}
+morph-spec approval-status {feature}
+morph-spec validate-feature {feature}
 ```
 
 | Check | Command | Pass Criteria |

package/framework/commands/morph-proposal.md

@@ -15,7 +15,7 @@ Guide a feature through the full planning pipeline (proposal through tasks) with
 Check if the feature already has state:
 
 ```bash
-npx morph-spec state get {feature-name}
+morph-spec state get {feature-name}
 ```
 
 - **Exists:** Read the current phase and resume from where it stopped (skip completed phases)
@@ -40,7 +40,7 @@ Read `framework/agents.json` (or `.morph/framework/agents.json` in client projec
 
 Register each selected agent:
 ```bash
-npx morph-spec state add-agent {feature-name} {agent-id}
+morph-spec state add-agent {feature-name} {agent-id}
 ```
 
 ### Step 3: Determine if UI/UX phase is needed
@@ -70,9 +70,9 @@ Fill every section of the template. In particular:
 ### Step 5: Register state
 
 ```bash
-npx morph-spec state init {feature-name}
-npx morph-spec state set {feature-name} status draft
-npx morph-spec state mark-output {feature-name} proposal
+morph-spec state init {feature-name}
+morph-spec state set {feature-name} status draft
+morph-spec state mark-output {feature-name} proposal
 ```
 
 ### MANDATORY PAUSE
@@ -88,8 +88,8 @@ Options: Approve proposal / Request changes / Reject
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} proposal
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} proposal
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -112,8 +112,8 @@ Check if `ui-designer` is in `activeAgents`:
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} uiux
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} uiux
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -130,8 +130,8 @@ Present: spec, contracts, decisions, effort estimate. Use `AskUserQuestion` with
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} design
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} design
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -158,8 +158,8 @@ Present: implementation plan with recommended strategy. Use `AskUserQuestion` wi
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} plan
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} plan
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -176,8 +176,8 @@ Present: task breakdown, execution order, total estimate. Use `AskUserQuestion`
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} tasks
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} tasks
+morph-spec phase advance {feature-name}
 ```
 
 ---

package/framework/commands/morph-status.md

@@ -13,7 +13,7 @@ Show the current MORPH project status and features in development.
 **ALWAYS** use the state-manager CLI to get status:
 
 ```bash
-npx morph-spec state list
+morph-spec state list
 ```
 
 This command automatically shows:
@@ -35,7 +35,7 @@ This command automatically shows:
 To get detailed JSON for a feature:
 
 ```bash
-npx morph-spec state get {feature-name}
+morph-spec state get {feature-name}
 ```
 
 ### 3. Archived Features
@@ -51,7 +51,7 @@ Check `.morph/specs/` for consolidated specs.
 
 ## Output
 
-The `npx morph-spec state list` command automatically generates a formatted dashboard:
+The `morph-spec state list` command automatically generates a formatted dashboard:
 
 ```
 ╔════════════════════════════════════════════════════════════════╗

package/framework/commands/morph-troubleshoot.md

@@ -72,7 +72,7 @@ site:learn.microsoft.com/azure {error}
 **WebSearch usage example:**
 
 If the user asks about a SignalR error:
-1. First: `npx morph-spec troubleshoot SignalR connection`
+1. First: `morph-spec troubleshoot SignalR connection`
 2. If not found: WebSearch with `site:github.com/dotnet/aspnetcore SignalR connection closed`
 3. Return formatted relevant links
 

package/framework/hooks/claude-code/pre-tool-use/task-tracking-guard.js

@@ -50,8 +50,8 @@ try {
   approve(
     `[morph-spec] WARNING: No active task tracking detected during implement phase.\n` +
     `Before writing code, start a task:\n` +
-    `  npx morph-spec task next ${name}        # see what's next\n` +
-    `  npx morph-spec task start ${name} <id>   # mark it in progress\n` +
+    `  morph-spec task next ${name}        # see what's next\n` +
+    `  morph-spec task start ${name} <id>   # mark it in progress\n` +
     `Task tracking ensures validators run, checkpoints fire, and progress is recorded.`
   );
 } catch {

package/framework/hooks/claude-code/session-start/inject-morph-context.js

@@ -140,7 +140,7 @@ try {
       if (trustLevel !== 'high' && trustLevel !== 'maximum') {
         lines.push('');
         lines.push(`⚠ Trust level: ${trustLevel} — approval gates require manual approval`);
-        lines.push(`  To auto-approve: npx morph-spec trust set ${name} high`);
+        lines.push(`  To auto-approve: morph-spec trust set ${name} high`);
       }
       if (!workflow && config?.workflowDetection?.confidence === 0) {
         lines.push('');

package/framework/hooks/claude-code/teammate-idle/teammate-idle.js

@@ -51,7 +51,7 @@ try {
 
   try {
     output = execSync(
-      `npx morph-spec validate-feature "${featureName}" --phase implement --quiet`,
+      `morph-spec validate-feature "${featureName}" --phase implement --quiet`,
       {
         cwd: process.cwd(),
         encoding: 'utf-8',
@@ -71,9 +71,9 @@ try {
     const feedback = [
       'MORPH-SPEC validation found issues — please fix before going idle:',
       '',
-      output.trim() || 'Run `npx morph-spec validate-feature to see details.',
+      output.trim() || 'Run `morph-spec validate-feature to see details.',
       '',
-      `Run: npx morph-spec validate-feature ${featureName} --phase implement`,
+      `Run: morph-spec validate-feature ${featureName} --phase implement`,
     ].join('\n');
 
     // Claude Code reads additionalContext from stdout for exit code 2

package/framework/hooks/claude-code/user-prompt/enrich-prompt.js

@@ -72,8 +72,8 @@ try {
         context.push(
           `[morph-spec] REMINDER: No task is currently in_progress for '${name}'.` +
           ` Start a task before coding:\n` +
-          `  npx morph-spec task next ${name}        # see what's next\n` +
-          `  npx morph-spec task start ${name} <id>   # mark it in progress`
+          `  morph-spec task next ${name}        # see what's next\n` +
+          `  morph-spec task start ${name} <id>   # mark it in progress`
         );
       }
     }

package/framework/hooks/git/pre-commit/agents.sh

@@ -10,7 +10,7 @@ if git diff --cached --name-only | grep -q 'agents\.json$'; then
   echo "Detected changes to agents.json"
 
   # Run validator
-  if ! npx morph-spec validate-agents-skills; then
+  if ! morph-spec validate-agents-skills; then
     echo ""
     echo "❌ COMMIT BLOCKED: agents.json validation failed"
     echo "   Fix errors above before committing"

package/framework/skills/level-0-meta/morph-brainstorming/SKILL.md

@@ -22,12 +22,12 @@ allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
 
 | Action | Tool | Alternative |
 |--------|------|-------------|
-| Load feature state | **Bash** `npx morph-spec state get $ARGUMENTS` | — |
+| Load feature state | **Bash** `morph-spec state get $ARGUMENTS` | — |
 | Read project config | **Read** `.morph/config/config.json` | — |
 | Scan existing code | **Glob** / **Grep** | — |
 | Research libraries | **Context7 MCP** `query_docs()` | **WebSearch** |
 | Ask clarifying questions | **AskUserQuestion** (never plain text) | — |
-| Render proposal template | **Bash** `npx morph-spec template render docs/proposal ...` | — |
+| Render proposal template | **Bash** `morph-spec template render docs/proposal ...` | — |
 
 ---
 
@@ -49,11 +49,11 @@ Update each to `in_progress` before its step and `completed` after.
 
 Gather information before generating ideas. This step is what makes morph-aware brainstorming different from generic brainstorming — it grounds your thinking in the actual project state and constraints.
 
-1. **Read state** — `npx morph-spec state get $ARGUMENTS` → current phase, active agents, existing outputs, task history
+1. **Read state** — `morph-spec state get $ARGUMENTS` → current phase, active agents, existing outputs, task history
 2. **Read config** — `.morph/config/config.json` → stack, architecture style (VSA vs standard), project name, integrations
 3. **Check architecture** — `cat .morph/config/config.json | grep -A3 architecture` → determines which agents and patterns apply
 4. **Read existing outputs** — proposal.md, spec.md, decisions.md (if they exist from prior work)
-5. **Check active agents** — `npx morph-spec dispatch-agents $ARGUMENTS design --table` → which specialists are available
+5. **Check active agents** — `morph-spec dispatch-agents $ARGUMENTS design --table` → which specialists are available
 6. **Scan codebase** — use Glob/Grep to understand existing patterns, domain models, and service boundaries relevant to the feature
 7. **Check MCP tools** — if Context7, GitHub, or other MCPs are available, use them for research
 
@@ -106,7 +106,7 @@ For each approach, document:
 
    **Phase 0 (Proposal):**
    ```bash
-   npx morph-spec template render docs/proposal ".morph/features/$ARGUMENTS/0-proposal/proposal.md" '{"FEATURE_NAME":"...", "DATE":"..."}'
+   morph-spec template render docs/proposal ".morph/features/$ARGUMENTS/0-proposal/proposal.md" '{"FEATURE_NAME":"...", "DATE":"..."}'
    ```
    Then edit the rendered file to add the brainstorming results.
 
@@ -115,12 +115,12 @@ For each approach, document:
 
 3. **Update state** (mandatory — do not skip):
    ```bash
-   npx morph-spec state mark-output $ARGUMENTS proposal    # Phase 0
-   npx morph-spec state mark-output $ARGUMENTS decisions    # Phase 2
+   morph-spec state mark-output $ARGUMENTS proposal    # Phase 0
+   morph-spec state mark-output $ARGUMENTS decisions    # Phase 2
    ```
    Then verify the output was recorded:
    ```bash
-   npx morph-spec state get $ARGUMENTS
+   morph-spec state get $ARGUMENTS
    ```
 
 ---

package/framework/skills/level-0-meta/morph-checklist/SKILL.md

@@ -14,9 +14,9 @@ Types: `deploy`, `security`, `seo`, `performance`, `accessibility`, `legal-brazi
 ## Deploy
 
 ### MORPH-SPEC Validation (run first)
-- [ ] `npx morph-spec validate-feature {feature}` — passes with 100% pass rate
-- [ ] `npx morph-spec approval-status {feature}` — all gates approved (design, plan, tasks)
-- [ ] `npx morph-spec state get {feature}` — phase is `implement`, all tasks `done`
+- [ ] `morph-spec validate-feature {feature}` — passes with 100% pass rate
+- [ ] `morph-spec approval-status {feature}` — all gates approved (design, plan, tasks)
+- [ ] `morph-spec state get {feature}` — phase is `implement`, all tasks `done`
 - [ ] Recap generated: `.morph/features/{feature}/5-implement/recap.md` exists
 
 ### Pre-Deploy

package/framework/skills/level-0-meta/morph-frontend-review/SKILL.md

@@ -57,7 +57,7 @@ Store `stack`, `frontendPath`, `startCommand` and the detected context — all s
 ## Step 1 — Design Outputs Validation (if context includes design validation)
 
 ```bash
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 ```
 
 Verify existence and quality of the 4 mandatory outputs in `.morph/features/$ARGUMENTS/2-ui/`:

package/framework/skills/level-0-meta/morph-init/SKILL.md

@@ -25,10 +25,10 @@ Before running any `morph-spec` command, detect how to invoke the CLI:
 
 ```bash
 # Try local first (project dependency), then global
-npx morph-spec --version
+morph-spec --version
 ```
 
-- If `npx morph-spec --version` succeeds → use `npx morph-spec` as the CLI prefix for all commands.
+- If `morph-spec --version` succeeds → use `morph-spec` as the CLI prefix for all commands.
 - If it fails → try `morph-spec --version` (global install). If that works → use `morph-spec`.
 - If both fail → **STOP** and show:
   ```
@@ -36,7 +36,7 @@ npx morph-spec --version
     npm install @polymorphism-tech/morph-spec
   ```
 
-Use the resolved CLI prefix (e.g. `npx morph-spec`) for ALL bash commands in the following steps.
+Use the resolved CLI prefix (e.g. `morph-spec`) for ALL bash commands in the following steps.
 
 ---
 
@@ -78,19 +78,19 @@ Check if `.morph/` exists in the current directory.
 
 **If MISSING:**
 ```bash
-npx morph-spec setup-infra
+morph-spec setup-infra
 ```
 Output confirms: `✓ MORPH-SPEC infrastructure installed.`
 
 **If EXISTS and argument is `refresh`:**
 Re-run setup-infra to update framework files, then continue with context/config refresh:
 ```bash
-npx morph-spec setup-infra
+morph-spec setup-infra
 ```
 
 **If EXISTS and no argument:**
 Ask: *"MORPH already initialized. Refresh context and config? (y/n)"*
-If `y` → re-run `npx morph-spec setup-infra` then continue.
+If `y` → re-run `morph-spec setup-infra` then continue.
 If `n` → STOP.
 
 ---
@@ -359,7 +359,7 @@ And inform the user:
 To create a new VSA project:
    dotnet new install https://github.com/polymorphism-tech/Morph_Template_VerticalSliceArchitecture
    dotnet new vsa -n MyProject
-   cd MyProject && npx morph-spec init
+   cd MyProject && morph-spec init
 ```
 
 ---
@@ -374,7 +374,7 @@ For each detected integration with an available MCP:
   ```json
   "supabase": { "type": "http", "url": "https://mcp.supabase.com/mcp" }
   ```
-- NO → show snippet + `npx morph-spec mcp setup supabase`
+- NO → show snippet + `morph-spec mcp setup supabase`
 
 **GitHub:**
 > *"Configure GitHub MCP? Requires Docker + a `GITHUB_PERSONAL_ACCESS_TOKEN`."*
@@ -386,7 +386,7 @@ For each detected integration with an available MCP:
     "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "<token>" }
   }
   ```
-- NO → show snippet + `npx morph-spec mcp setup github`
+- NO → show snippet + `morph-spec mcp setup github`
 
 **Vercel detected** (vercel.json exists OR stack is nextjs):
 > *"Configure Vercel MCP? Uses OAuth — no credentials needed."*
@@ -394,7 +394,7 @@ For each detected integration with an available MCP:
   ```json
   "vercel": { "type": "http", "url": "https://mcp.vercel.com" }
   ```
-- NO → show snippet + `npx morph-spec mcp setup vercel`
+- NO → show snippet + `morph-spec mcp setup vercel`
 
 Only offer Docker, Azure if explicitly detected in `.env.example`.
 
@@ -462,7 +462,7 @@ Use `AskUserQuestion` with header `"{MCP} failed"` and these options:
 After all configuration is complete, run the health check to verify everything is properly installed:
 
 ```bash
-npx morph-spec doctor
+morph-spec doctor
 ```
 
 This validates: config.json integrity, agents.json presence, hooks installation, skills distribution, required command files, and state.json schema version. Fix any reported issues before proceeding.