@polymorphism-tech/morph-spec 4.10.3 → 4.10.4

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.3  
+**Version:** 4.10.4  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -125,10 +125,10 @@ These commands are available inside Claude Code after init.
 
 | Command                     | Description                                               |
 | --------------------------- | --------------------------------------------------------- |
-| `/morph-proposal {feature}` | Full spec pipeline (phases 0-4, pauses at approval gates) |
-| `/morph-apply {feature}`    | Implement approved feature (phase 5)                      |
-| `/morph-status`             | Feature status dashboard                                  |
-| `/morph-preflight`          | Pre-implementation validation                             |
+| `/morph:proposal {feature}` | Full spec pipeline (phases 0-4, pauses at approval gates) |
+| `/morph:apply {feature}`    | Implement approved feature (phase 5)                      |
+| `/morph:status`             | Feature status dashboard                                  |
+| `/morph:preflight`          | Pre-implementation validation                             |
 
 
 ---
@@ -376,4 +376,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.10.3 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.10.4 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';
@@ -77,13 +77,13 @@ program
 
 program
   .command('setup-infra')
-  .description('Install MORPH-SPEC infrastructure (headless, no prompts). Called by /morph-init skill.')
+  .description('Install MORPH-SPEC infrastructure (headless, no prompts). Called by /morph:init skill.')
   .option('-p, --path <path>', 'Target path (default: current directory)')
   .action(setupInfraCommand);
 
 program
   .command('install-plugin <name>')
-  .description('Install a Claude Code plugin (superpowers, context7). Called by /morph-init skill.')
+  .description('Install a Claude Code plugin (superpowers, context7). Called by /morph:init skill.')
   .action(installPluginCommand);
 
 program

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.10.3",
+  "version": "4.10.4",
   "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

@@ -39,10 +39,10 @@ Phases in brackets are optional.
 
 | Command | Description |
 |---------|-------------|
-| `/morph-proposal {feature}` | Full spec pipeline — phases 0–4 with approval gates |
-| `/morph-apply {feature}` | Implement approved feature — phase 5 |
-| `/morph-status` | Project-wide feature status dashboard |
-| `/morph-preflight` | Pre-implementation validation (7 checks) |
+| `/morph:proposal {feature}` | Full spec pipeline — phases 0–4 with approval gates |
+| `/morph:apply {feature}` | Implement approved feature — phase 5 |
+| `/morph:status` | Project-wide feature status dashboard |
+| `/morph:preflight` | Pre-implementation validation (7 checks) |
 
 ---
 
@@ -198,4 +198,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.10.3 by Polymorphism Tech*
+*morph-spec v4.10.4 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -45,7 +45,7 @@ morph-spec doctor
 Open your project in Claude Code and run:
 
 ```
-/morph-proposal my-feature
+/morph:proposal my-feature
 ```
 
 Replace `my-feature` with a short kebab-case name for your feature (e.g., `user-notifications`, `payment-flow`).
@@ -90,7 +90,7 @@ Claude breaks the spec into atomic tasks (`T001`, `T002`, …) saved to `3-tasks
 At this point, planning is complete:
 
 ```
-✅ Planning complete — run /morph-apply my-feature to implement
+✅ Planning complete — run /morph:apply my-feature to implement
 ```
 
 ---
@@ -98,7 +98,7 @@ At this point, planning is complete:
 ## Implement
 
 ```
-/morph-apply my-feature
+/morph:apply my-feature
 ```
 
 Claude reads `spec.md`, `contracts.cs`, and `tasks.md`, then implements task by task:
@@ -184,7 +184,7 @@ morph-spec doctor
 
 ## Tips
 
-**Use `/morph-proposal` even for small features.** The proposal phase catches scope creep, identifies the right agents, and generates contracts early — before implementation makes it expensive to change direction.
+**Use `/morph:proposal` even for small features.** The proposal phase catches scope creep, identifies the right agents, and generates contracts early — before implementation makes it expensive to change direction.
 
 **Approve explicitly at each gate.** The design gate exists to prevent implementing the wrong thing. If something in `spec.md` or `contracts.cs` looks off, say so before approving.
 
@@ -203,4 +203,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.10.3 by Polymorphism Tech*
+*morph-spec v4.10.4 by Polymorphism Tech*

package/framework/CLAUDE.md

@@ -23,10 +23,10 @@
 
 | Command | Purpose |
 |---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (pauses for approval) |
-| `/morph-apply {feature}` | Implement feature |
-| `/morph-status` | Status dashboard |
-| `/morph-preflight` | Pre-deploy validation |
+| `/morph:proposal {feature}` | Full spec pipeline (pauses for approval) |
+| `/morph:apply {feature}` | Implement feature |
+| `/morph:status` | Status dashboard |
+| `/morph:preflight` | Pre-deploy validation |
 
 ## Agents
 

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

@@ -256,7 +256,7 @@ O projeto nao possui arquivos de infraestrutura em `infra/`.
 
 Opcoes:
 1. **Criar agora** - Gerar templates baseado no projeto detectado
-2. **Usar /morph-infra** - Rodar comando de setup de infra primeiro
+2. **Usar /morph:infra** - Rodar comando de setup de infra primeiro
 3. **Cancelar** - Abortar deploy
 
 Qual opcao voce prefere?

package/framework/agents/quality/code-analyzer.md

@@ -18,7 +18,7 @@ Deep code analysis specialist. Automates architecture review, clean code checks,
 
 | Trigger | Automatic? | Scope |
 |---------|-----------|-------|
-| FASE 5 completion (`/morph-apply` done) | Yes | Full feature code |
+| FASE 5 completion (`/morph:apply` done) | Yes | Full feature code |
 | Checkpoint (every 3 tasks) | Yes | Code since last checkpoint |
 | Manual: `analyze`, `review code`, `code quality` | No | Specified scope |
 | Pre-merge review | Recommended | All changed files |

package/framework/commands/morph-apply.md

@@ -4,14 +4,14 @@ argument-hint: <feature-name>
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
 ---
 
-# /morph-apply — Feature Implementation
+# /morph:apply — Feature Implementation
 
 Implement the feature by executing its task breakdown, tracking progress through the morph-spec state machine, and producing a recap at the end.
 
 ## Usage
 
 ```
-/morph-apply {feature-name}
+/morph:apply {feature-name}
 ```
 
 ## Recommended Tools
@@ -46,7 +46,7 @@ npx morph-spec validate-feature $ARGUMENTS
 
 ```
 Feature is not ready for implementation.
-Run /morph-proposal $ARGUMENTS to complete planning phases.
+Run /morph:proposal $ARGUMENTS to complete planning phases.
 (Resumes automatically from the current phase.)
 ```
 
@@ -192,7 +192,7 @@ After implementation, present a summary to the user:
 3. Validation results
 4. Any deviations from spec
 
-For Azure projects, remind the user: "Run `/morph-preflight` before deploying to validate packages, migrations, Docker, and secrets."
+For Azure projects, remind the user: "Run `/morph:preflight` before deploying to validate packages, migrations, Docker, and secrets."
 
 ---
 

package/framework/commands/morph-infra.md

@@ -4,14 +4,14 @@ argument-hint: [up|down|plan|status]
 allowed-tools: Read, Write, Edit, Bash, Glob, AskUserQuestion
 ---
 
-# /morph-infra - Infrastructure Management
+# /morph:infra - Infrastructure Management
 
 Manage Azure infrastructure using Bicep templates.
 
 ## Usage
 
 ```
-/morph-infra [action] [options]
+/morph:infra [action] [options]
 ```
 
 ### Actions
@@ -30,7 +30,7 @@ Manage Azure infrastructure using Bicep templates.
 
 ### 1. INIT - Initialize IaC
 
-When the user requests `/morph-infra init`:
+When the user requests `/morph:infra init`:
 
 1. Create the `infra/` structure in the project:
    ```
@@ -60,7 +60,7 @@ When the user requests `/morph-infra init`:
 
 ### 2. VALIDATE - Validate Templates
 
-When the user requests `/morph-infra validate`:
+When the user requests `/morph:infra validate`:
 
 1. Run Bicep validation:
    ```bash
@@ -75,7 +75,7 @@ When the user requests `/morph-infra validate`:
 
 ### 3. PLAN - Preview Changes
 
-When the user requests `/morph-infra plan [env]`:
+When the user requests `/morph:infra plan [env]`:
 
 1. Check if Azure CLI is authenticated:
    ```bash
@@ -102,7 +102,7 @@ When the user requests `/morph-infra plan [env]`:
 
 ### 4. DEPLOY - Execute Deploy
 
-When the user requests `/morph-infra deploy [env]`:
+When the user requests `/morph:infra deploy [env]`:
 
 1. Verify plan was approved
 
@@ -130,7 +130,7 @@ When the user requests `/morph-infra deploy [env]`:
 
 ### 5. DESTROY - Remove Resources
 
-When the user requests `/morph-infra destroy [env]`:
+When the user requests `/morph:infra destroy [env]`:
 
 1. **WARN** that this action is irreversible
 
@@ -177,14 +177,14 @@ Before any deploy, check with Cost Guardian:
 ## Usage Example
 
 ```
-User: /morph-infra init
+User: /morph:infra init
 Claude: Creating IaC structure...
         - infra/main.bicep
         - infra/parameters.dev.json
         - infra/modules/*.bicep
-        Done! Run /morph-infra validate to verify.
+        Done! Run /morph:infra validate to verify.
 
-User: /morph-infra plan dev
+User: /morph:infra plan dev
 Claude: Analyzing changes for dev environment...
 
         CREATE:

package/framework/commands/morph-preflight.md

@@ -11,7 +11,7 @@ Validates project readiness before deploying to Azure.
 ## Usage
 
 ```
-/morph-preflight azure
+/morph:preflight azure
 ```
 
 ## Purpose
@@ -39,7 +39,7 @@ npx morph-spec validate-feature {feature}
 | All tasks complete | `state get` → tasks array | 0 tasks in `pending` or `in_progress` |
 | Recap generated | Read `5-implement/recap.md` | File exists and is non-empty |
 
-**If any MORPH check fails:** Show which check failed and recommend: `Run /morph-apply {feature} to complete implementation before deploying.`
+**If any MORPH check fails:** Show which check failed and recommend: `Run /morph:apply {feature} to complete implementation before deploying.`
 
 ---
 
@@ -222,7 +222,7 @@ Recommended fixes:
 ### Before creating PR for production
 
 ```bash
-/morph-preflight azure
+/morph:preflight azure
 ```
 
 ### In CI/CD pipeline

package/framework/commands/morph-proposal.md

@@ -1,5 +1,5 @@
 ---
-description: MORPH Spec Pipeline — creates or resumes feature planning through phases 0-6 with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph-proposal. This is the primary entry point for all MORPH-SPEC feature work.
+description: MORPH Spec Pipeline — creates or resumes feature planning through phases 0-6 with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph:proposal. This is the primary entry point for all MORPH-SPEC feature work.
 argument-hint: <feature-name>
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
@@ -187,7 +187,7 @@ npx morph-spec phase advance {feature-name}
 After task approval:
 
 ```
-Planning complete! Run /morph-apply {feature-name} to start implementation.
+Planning complete! Run /morph:apply {feature-name} to start implementation.
 ```
 
 ---

package/framework/commands/morph-status.md

@@ -83,9 +83,9 @@ The `npx morph-spec state list` command automatically generates a formatted dash
 ## Available Actions
 
 Suggest next actions:
-- `/morph-proposal {feature}` - Create a new feature
-- `/morph-apply {feature}` - Implement a feature
-- `/morph-archive {feature}` - Archive a completed feature
+- `/morph:proposal {feature}` - Create a new feature
+- `/morph:apply {feature}` - Implement a feature
+- `/morph:archive {feature}` - Archive a completed feature
 
 ---
 

package/framework/hooks/claude-code/pre-compact/save-morph-context.js

@@ -35,7 +35,7 @@ const PHASE_POSITIONS = {
 const PIPELINE_TOTAL = 5;
 
 const NEXT_STEP_HINT = {
-  proposal:  (n) => `Continue spec pipeline: /morph-proposal ${n}`,
+  proposal:  (n) => `Continue spec pipeline: /morph:proposal ${n}`,
   design:    (n) => `Approve design gate: morph-spec approve ${n} design`,
   uiux:      (n) => `Approve UI gate: morph-spec approve ${n} uiux`,
   tasks:     (n) => `Approve tasks gate: morph-spec approve ${n} tasks`,

package/framework/rules/morph-workflow.md

@@ -37,9 +37,9 @@ Use `morph-spec status {feature}` to see current phase and pending approval gate
 
 | Command | Purpose |
 |---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1-4, pauses for approval) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Feature dashboard |
+| `/morph:proposal {feature}` | Full spec pipeline (phases 1-4, pauses for approval) |
+| `/morph:apply {feature}` | Implement feature (phase 5) |
+| `/morph:status` | Feature dashboard |
 
 ---
 

package/framework/skills/README.md

@@ -32,7 +32,7 @@ Each skill is a directory: `{name}/SKILL.md` + optional `scripts/`, `references/
 
 ## level-1-workflows — Phase Workflow Skills
 
-Invoked internally by `/morph-proposal` and `/morph-apply`. Not user-invocable.
+Invoked internally by `/morph:proposal` and `/morph:apply`. Not user-invocable.
 
 | Skill | Phase | Description |
 |-------|-------|-------------|

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

@@ -218,7 +218,7 @@ And inform the user:
   → morph-spec will use vsa-architect + contracts-vsa.cs for features
 ```
 
-> This key is what activates `vsa-architect` instead of `domain-architect` during `/morph-proposal`.
+> This key is what activates `vsa-architect` instead of `domain-architect` during `/morph:proposal`.
 
 **If the project doesn't exist yet (new VSA project from scratch)**, also inform:
 
@@ -377,5 +377,5 @@ Before printing the summary, check `~/.claude/settings.local.json` for `env.CLAU
 [If any plugin was newly installed:]
 ○ Restart Claude Code to activate newly installed plugins.
 
-Next: /morph-proposal [feature-name]
+Next: /morph:proposal [feature-name]
 ```

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

@@ -4,12 +4,12 @@ description: MORPH-SPEC Phase 3 (Clarify). Iterative clarification loop driven b
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Clarify — Phase 3
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Eliminate spec ambiguities through an iterative question loop until the spec has sufficient quality to generate tasks.
 

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

@@ -3,7 +3,7 @@ name: morph:phase-codebase-analysis
 description: MORPH-SPEC Design sub-phase that analyzes existing codebase and database schema, producing schema-analysis.md with real column names, types, relationships, and field mismatches. Use at the start of Design phase before generating contracts.cs to prevent incorrect field names or types.
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase

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

@@ -4,12 +4,12 @@ description: MORPH-SPEC Phase 2 (Design). Schema-first interactive design: reads
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Design — Phase 2
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Schema-first interactive design: read the real schema, validate with user, generate blueprint, produce artifacts through a quality loop.
 

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

@@ -6,13 +6,13 @@ disable-model-invocation: true
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
 ---
 
 # MORPH Implement — Phase 5
 
-> INTERNAL: Workflow skill used by /morph-apply during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:apply during automated phase orchestration. Not a user command.
 
 Implement the tasks defined in Phase 4, with checkpoints every 3 tasks and a final recap.
 
@@ -98,7 +98,7 @@ Before starting tasks, verify that MCPs needed for the implement phase are worki
 Use `AskUserQuestion` with header `"{MCP}"` and options:
 - **Continue without {MCP}** — Show `fallback` from registry. Implementation will use the fallback automatically.
 - **Reconfigure credentials** — Collect credentials and update `.claude/settings.local.json`. Re-test after reconfiguring.
-- **Stop implementation** — Abort. User must fix the MCP and re-run `/morph-apply`.
+- **Stop implementation** — Abort. User must fix the MCP and re-run `/morph:apply`.
 
 > **Design:** This check is fail-open — consistent with morph-spec philosophy. The user gets explicit choice instead of tasks failing silently.
 

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

@@ -5,12 +5,12 @@ argument-hint: "[feature-name]"
 disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Plan — Phase 4
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Generate a detailed implementation plan with exact paths, TDD code, and execution strategy.
 

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

@@ -4,12 +4,12 @@ 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.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Setup — Phase 1
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Initialize the context and prepare the environment for an approved feature.
 

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

@@ -5,12 +5,12 @@ argument-hint: "[feature-name]"
 disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH Tasks — Phase 4
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Break the approved specification into executable tasks, define execution order, and establish checkpoints.
 
@@ -309,4 +309,4 @@ Use `AskUserQuestion` to capture explicit approval before advancing. This gate p
 
 ---
 
-After approval: "Planning complete! Run `/morph-apply $ARGUMENTS` to start implementation."
+After approval: "Planning complete! Run `/morph:apply $ARGUMENTS` to start implementation."

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

@@ -4,12 +4,12 @@ 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.3"
+cliVersion: "4.10.4"
 ---
 
 # MORPH UI/UX Design - Phase 1.5
 
-> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+> INTERNAL: Workflow skill used by /morph:proposal during automated phase orchestration. Not a user command.
 
 Conditional phase for features with front-end. Collects UI/UX requirements, generates wireframes, component specs, and user flows.
 

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.3"
+cliVersion: "4.10.4"
 ---
 
 # Scope Escalation Workflow
@@ -133,7 +133,7 @@ npx morph-spec scope escalate <feature> --task <id> --reason "<reason>" --target
 
 After escalation:
 
-- **If regressed to tasks:** "Re-analyze the affected tasks. Rewrite tasks.md with accurate scope. Run `/morph-proposal <feature>` to continue from the tasks phase."
+- **If regressed to tasks:** "Re-analyze the affected tasks. Rewrite tasks.md with accurate scope. Run `/morph:proposal <feature>` to continue from the tasks phase."
 - **If regressed to design:** "Re-analyze the spec. Update spec.md with the discovered architecture. Then regenerate tasks."
 - **If expanded:** "Continue implementing. Use `morph-spec task start <feature> <sub-task-id>` to start the first sub-task."
 

package/framework/standards/ai-agents/team-orchestration.md

@@ -406,7 +406,7 @@ morph-spec state set {feature} workflow full-morph
 
 ```bash
 # FASES 0-4: Single Claude session
-/morph-proposal scheduled-reports
+/morph:proposal scheduled-reports
 # ... proposal approved, design approved, tasks generated ...
 
 # FASE 5: Create agent team

package/package.json

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

package/src/commands/project/doctor.js

@@ -780,7 +780,7 @@ export async function doctorCommand(options = {}) {
       } catch { /* non-fatal */ }
 
       // ── Claude Code Plugins ──────────────────────────────────────────────────
-      console.log(chalk.cyan('\n  Claude Code Plugins (required for /morph-init)'));
+      console.log(chalk.cyan('\n  Claude Code Plugins (required for /morph:init)'));
       const pluginsFile = join(homedir(), '.claude', 'plugins', 'installed_plugins.json');
       let pluginData = { plugins: {} };
       try {

package/src/commands/project/init.js

@@ -415,7 +415,7 @@ export async function initCommand(options) {
     // Suggest tutorial for first-time users
     if (integrationsCreated) {
       logger.blank();
-      logger.info('First time using morph-spec? Run `/morph-proposal <feature>` to start a new feature.');
+      logger.info('First time using morph-spec? Run `/morph:proposal <feature>` to start a new feature.');
     }
 
     logger.blank();

package/src/commands/state/advance-phase.js

@@ -468,38 +468,38 @@ export async function advancePhaseCommand(feature, options = {}) {
 function getPhaseGuidance(phase, feature) {
   const guides = {
     'setup': [
-      `Resume spec pipeline: /morph-proposal ${feature}`,
+      `Resume spec pipeline: /morph:proposal ${feature}`,
       'Auto-continues from setup phase'
     ],
     'uiux': [
-      `Resume spec pipeline: /morph-proposal ${feature}`,
+      `Resume spec pipeline: /morph:proposal ${feature}`,
       'Provide layout references and preferences',
       'Review wireframes before proceeding'
     ],
     'design': (() => {
       const { isDotnet } = getStackProfile();
       return [
-        `Resume spec pipeline: /morph-proposal ${feature}`,
+        `Resume spec pipeline: /morph:proposal ${feature}`,
         'Review DECISION POINTS carefully',
         isDotnet ? 'Approve spec.md and contracts.cs' : 'Approve spec.md and contracts.ts (TypeScript + Zod schemas)'
       ];
     })(),
     'clarify': [
-      `Resume spec pipeline: /morph-proposal ${feature}`,
+      `Resume spec pipeline: /morph:proposal ${feature}`,
       'Resolve edge cases and unknowns'
     ],
     'plan': [
-      `Resume spec pipeline: /morph-proposal ${feature}`,
+      `Resume spec pipeline: /morph:proposal ${feature}`,
       'Review implementation plan for completeness',
       'Approve plan before generating task breakdown'
     ],
     'tasks': [
-      `Resume spec pipeline: /morph-proposal ${feature}`,
+      `Resume spec pipeline: /morph:proposal ${feature}`,
       'Review task order and dependencies',
       'Approve task list before implementing'
     ],
     'implement': [
-      `Start implementing: /morph-apply ${feature}`,
+      `Start implementing: /morph:apply ${feature}`,
       'Complete tasks one by one with: morph-spec task done',
       'Validators run automatically on task completion'
     ],

package/src/lib/detectors/index.js

@@ -29,21 +29,28 @@ export function detectProject(targetPath, opts = {}) {
 
   try {
     // ── Package.json analysis ──────────────────────────────────────────────
-    const pkgPath = join(targetPath, 'package.json');
-    let pkg = null;
-    if (existsSync(pkgPath)) {
+    // Collect deps from root and common monorepo subfolders
+    const pkgLocations = ['.', 'src/frontend', 'frontend', 'apps/web', 'packages/app'];
+    const allDeps = {};
+    let rootPkg = null;
+    let scripts = [];
+    for (const loc of pkgLocations) {
+      const pkgPath = join(targetPath, loc, 'package.json');
+      if (!existsSync(pkgPath)) continue;
       try {
-        pkg = JSON.parse(readFileSync(pkgPath, 'utf8'));
+        const pkg = JSON.parse(readFileSync(pkgPath, 'utf8'));
+        if (loc === '.') rootPkg = pkg;
+        Object.assign(allDeps, pkg.dependencies, pkg.devDependencies);
+        scripts.push(...Object.keys(pkg.scripts || {}));
+        // Track frontend path for config
+        if (loc !== '.' && (pkg.dependencies?.next || pkg.dependencies?.react || pkg.dependencies?.vue)) {
+          structure.frontendPath = loc;
+        }
       } catch { /* invalid JSON */ }
     }
+    const depNames = Object.keys(allDeps);
 
-    if (pkg) {
-      const allDeps = {
-        ...pkg.dependencies,
-        ...pkg.devDependencies,
-      };
-      const depNames = Object.keys(allDeps);
-      const scripts = Object.keys(pkg.scripts || {});
+    if (depNames.length > 0) {
 
       // Stack detection from deps
       if (depNames.includes('next')) {
@@ -54,12 +61,12 @@ export function detectProject(targetPath, opts = {}) {
         structure.stack = 'vue';
       } else if (depNames.includes('express') || depNames.includes('fastify') || depNames.includes('hono')) {
         structure.stack = 'nodejs';
-      } else if (pkg.name) {
+      } else if (rootPkg?.name) {
         structure.stack = 'nodejs';
       }
 
       // UI library detection
-      if (existsSync(join(targetPath, 'components.json')) || depNames.includes('@shadcn/ui')) {
+      if (existsSync(join(targetPath, 'components.json')) || existsSync(join(targetPath, structure.frontendPath || '.', 'components.json')) || depNames.includes('@shadcn/ui')) {
         structure.uiLibrary = 'shadcn';
       } else if (depNames.some(d => d.includes('mudblazor'))) {
         structure.uiLibrary = 'mudblazor';
@@ -79,8 +86,7 @@ export function detectProject(targetPath, opts = {}) {
       }
 
       // Vercel detection
-      if (depNames.includes('vercel') || scripts.includes('vercel') ||
-          scripts.some(s => (pkg.scripts[s] || '').includes('vercel'))) {
+      if (depNames.includes('vercel') || scripts.includes('vercel')) {
         structure.hasVercel = true;
       }
     }
@@ -89,22 +95,34 @@ export function detectProject(targetPath, opts = {}) {
     let hasDotnet = false;
     let hasBlazer = false;
     const csprojLocations = ['.', 'src', 'src/Api', 'src/Web', 'src/backend'];
+
+    function checkCsproj(filePath) {
+      hasDotnet = true;
+      try {
+        const content = readFileSync(filePath, 'utf8');
+        if (content.includes('Microsoft.AspNetCore.Components') || content.includes('Blazor')) {
+          hasBlazer = true;
+        }
+        if (content.includes('Hangfire')) {
+          if (!structure.integrations.includes('hangfire')) structure.integrations.push('hangfire');
+        }
+      } catch { /* ignore */ }
+    }
+
     for (const loc of csprojLocations) {
       try {
         const dir = join(targetPath, loc);
-        if (existsSync(dir)) {
-          const entries = readdirSyncSafe(dir);
-          for (const entry of entries.filter(e => e.endsWith('.csproj'))) {
-            hasDotnet = true;
-            try {
-              const content = readFileSync(join(dir, entry), 'utf8');
-              if (content.includes('Microsoft.AspNetCore.Components') || content.includes('Blazor')) {
-                hasBlazer = true;
-              }
-              if (content.includes('Hangfire')) {
-                if (!structure.integrations.includes('hangfire')) structure.integrations.push('hangfire');
-              }
-            } catch { /* ignore */ }
+        if (!existsSync(dir)) continue;
+        const entries = readdirSyncSafe(dir);
+        // Direct .csproj files
+        for (const e of entries.filter(f => f.endsWith('.csproj'))) {
+          checkCsproj(join(dir, e));
+        }
+        // One level deeper (e.g., src/backend/MyProject/*.csproj)
+        for (const sub of entries) {
+          const subDir = join(dir, sub);
+          for (const e of readdirSyncSafe(subDir).filter(f => f.endsWith('.csproj'))) {
+            checkCsproj(join(subDir, e));
           }
         }
       } catch { /* ignore */ }

package/src/scripts/setup-infra.js

@@ -3,7 +3,7 @@
  *
  * Headless infrastructure setup for MORPH-SPEC.
  * Extracted from init.js (steps 1-10) so it can be called by the
- * /morph-init Claude Code skill via `morph-spec setup-infra` without
+ * /morph:init Claude Code skill via `morph-spec setup-infra` without
  * interactive prompts or stack detection.
  *
  * Usage: