@polymorphism-tech/morph-spec 4.10.4 → 4.10.6

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

@@ -1,5 +1,5 @@
 ---
-name: morph:frontend-review
+name: morph-frontend-review
 description: Complete frontend audit — validates design outputs (design-system, WCAG contrast,
   mockups), static accessibility scan (TSX + Razor), responsive screenshots at 3
   breakpoints via Playwright, axe-core a11y at runtime, and SEO (Next.js metadata). Covers Next.js
@@ -193,7 +193,7 @@ Request explicit user confirmation before skipping screenshots:
 Dev server not detected. Responsive screenshots via Playwright cannot be captured.
 
 Options:
-1. Start the server manually and re-run /morph:frontend-review
+1. Start the server manually and re-run /morph-frontend-review
 2. Explicitly confirm you want to skip screenshots and why
 
 Cannot proceed to axe-core without dev server.
@@ -300,7 +300,7 @@ Create consolidated summary file:
 mkdir -p ".morph/features/$ARGUMENTS/visual-screenshots"
 ```
 
-Save to `.morph/features/$ARGUMENTS/visual-screenshots/morph:frontend-review-summary.md`:
+Save to `.morph/features/$ARGUMENTS/visual-screenshots/morph-frontend-review-summary.md`:
 
 ```markdown
 # Frontend Review — {feature}

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

@@ -1,11 +1,11 @@
 ---
-name: morph:init
+name: morph-init
 description: >
   LLM-powered project initialization. Installs morph-spec infrastructure if
   needed, auto-installs required plugins (superpowers, context7), analyzes any
   project structure intelligently, generates rich context/README.md and
   config.json, and configures MCPs. Use once per project after installing
-  @polymorphism-tech/morph-spec. Re-run with /morph:init refresh to update
+  @polymorphism-tech/morph-spec. Re-run with /morph-init refresh to update
   context as the project evolves.
 argument-hint: "[refresh]"
 user-invocable: true
@@ -15,7 +15,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 # morph-init — LLM-Powered Project Initialization
 
 > Run once after `npm install @polymorphism-tech/morph-spec`.
-> Re-run as `/morph:init refresh` when your project evolves.
+> Re-run as `/morph-init refresh` when your project evolves.
 
 ---
 
@@ -55,7 +55,7 @@ claude plugin install superpowers@claude-plugins-official
 claude plugin install context7@claude-plugins-official
 ```
 
-**If the command succeeds:** `✓ {plugin} installed. Restart Claude Code after /morph:init completes.`
+**If the command succeeds:** `✓ {plugin} installed. Restart Claude Code after /morph-init completes.`
 
 **If the command fails:** Show this and **STOP** — do not continue:
 
@@ -63,7 +63,7 @@ claude plugin install context7@claude-plugins-official
 Plugin {plugin} could not be installed automatically.
 Run manually and restart Claude Code:
   claude plugin install {plugin}
-Then re-run /morph:init.
+Then re-run /morph-init.
 ```
 
 Both `superpowers` and `context7` are required. Do not continue if either is missing.
@@ -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:
 
@@ -318,7 +318,7 @@ For each MCP configured in Step 7, run a health check to verify it actually work
 Use `AskUserQuestion` with header `"{MCP} failed"` and these options:
 - **Reconfigure credentials** — Loop back to Step 7 for this specific MCP. Maximum 2 retries per MCP. After 2 failures, force option 2.
 - **Continue without {MCP}** — Show the `fallback` field from the registry (e.g., "WebSearch + WebFetch for library documentation") and proceed.
-- **Stop init** — Abort initialization. User must fix MCP configuration manually and re-run `/morph:init`.
+- **Stop init** — Abort initialization. User must fix MCP configuration manually and re-run `/morph-init`.
 
 **Retry tracking:** Keep a counter per MCP. On the 2nd failure for the same MCP, skip the "Reconfigure" option and only offer "Continue without" or "Stop".
 
@@ -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-0-meta/morph-post-implementation/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: morph:post-implementation
+name: morph-post-implementation
 description: Orchestrates the complete post-implementation flow: stack detection,
   automated scans (C#/Next.js), tests, validate-feature, smoke test via Playwright
   (mandatory if dev server active), code review checklist by stack, checkpoint, and
@@ -61,8 +61,8 @@ node .claude/skills/morph-code-review-nextjs/scripts/scan-nextjs.mjs --diff
 **🚫 BLOCK if any CRITICAL finding found.**
 
 Fix all CRITICALs before continuing. To review the full checklist:
-- .NET: `/morph:code-review`
-- Next.js: `/morph:code-review-nextjs`
+- .NET: `/morph-code-review`
+- Next.js: `/morph-code-review-nextjs`
 
 ---
 
@@ -222,7 +222,7 @@ Wait for both. **🚫 BLOCK if either returns unresolved CRITICAL.**
 [ ] DTOs with descriptive names + correct types
 ```
 
-> For full list: `/morph:code-review`
+> For full list: `/morph-code-review`
 
 ### If NEXTJS:
 
@@ -241,7 +241,7 @@ Wait for both. **🚫 BLOCK if either returns unresolved CRITICAL.**
 [ ] No any type annotation
 ```
 
-> For full list: `/morph:code-review-nextjs`
+> For full list: `/morph-code-review-nextjs`
 
 **🚫 BLOCK if any CRITICAL item is unresolved.**
 
@@ -296,7 +296,7 @@ This skill will:
 Before creating the PR, invoke the compliance checklist:
 
 ```
-Skill(morph:checklist)
+Skill(morph-checklist)
 ```
 
 This skill checks: security, SEO, performance, accessibility, and LGPD compliance.
@@ -353,7 +353,7 @@ EOF
 | Step 5 | Dev server not detected without explicit user confirmation |
 | Step 6 | Any unresolved CRITICAL item in manual checklist |
 | Step 8 | Tests failing in worktree before merge/PR |
-| Step 9 | Unresolved CRITICAL item in `morph:checklist` |
+| Step 9 | Unresolved CRITICAL item in `morph-checklist` |
 
 **All BLOCKs must be resolved before creating the PR.**
 

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

@@ -1,5 +1,5 @@
 ---
-name: morph:replicate
+name: morph-replicate
 description: Simplified workflow for converting HTML prototypes into functional Blazor components, extracting design patterns and mapping HTML elements to Fluent UI/MudBlazor equivalents. Use when an approved HTML prototype exists and needs conversion to Blazor without a full MORPH-SPEC spec pipeline.
 user-invocable: true
 argument-hint: "[feature-name] [prototype-path]"
@@ -16,12 +16,12 @@ stacks:
 ## Command
 
 ```bash
-/morph:replicate {feature-name} {prototype-path}
+/morph-replicate {feature-name} {prototype-path}
 ```
 
 **Example:**
 ```bash
-/morph:replicate ui-redesign prototipo/
+/morph-replicate ui-redesign prototipo/
 ```
 
 ---
@@ -162,7 +162,7 @@ npx morph-spec state mark-output {feature-name} recap
 ## Execution Example
 
 ```markdown
-/morph:replicate checkout-redesign prototipo/checkout/
+/morph-replicate checkout-redesign prototipo/checkout/
 
 📁 Analyzing prototype in prototipo/checkout/...
 

package/framework/skills/level-0-meta/morph-replicate/references/blazor-html-mapping.md

@@ -1,7 +1,7 @@
 # HTML → Blazor Component Mapping Reference
 
 > Reference for converting HTML prototype elements to Fluent UI / MudBlazor equivalents.
-> Used during FASE 1 of the `/morph:replicate` workflow.
+> Used during FASE 1 of the `/morph-replicate` workflow.
 
 ## Common Component Mappings
 

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

@@ -1,5 +1,5 @@
 ---
-name: morph:simulation-checklist
+name: morph-simulation-checklist
 description: Checklist for implementing mock/simulation clients for external .NET services (AI APIs, payments, email). Use when setting up simulation mode without real API access, when creating fake service implementations for development/testing, or when debugging external service integrations.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep

package/framework/skills/level-0-meta/morph-tool-usage-guide/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: morph:tool-usage-guide
+name: morph-tool-usage-guide
 description: Decision flowchart and per-phase reference for selecting the right Claude Code tool (Read, Grep, Glob, Bash, Task) or MCP tool in MORPH-SPEC workflows. Use when unsure which tool to use for a given action, when choosing between native tools and MCPs, or when deciding whether to use a subagent vs direct tools.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep

package/framework/skills/level-0-meta/morph-verification-before-completion/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: morph:verification-before-completion
+name: morph-verification-before-completion
 description: Phase-specific verification checklists and morph-spec validation commands for confirming MORPH-SPEC outputs are complete and correct. Use before marking any task done, before advancing to the next phase, before committing, or before creating PRs.
 user-invocable: true
 argument-hint: "[feature-name] [phase?]"

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

@@ -1,15 +1,15 @@
 ---
-name: morph:phase-clarify
+name: morph-phase-clarify
 description: MORPH-SPEC Phase 3 (Clarify). Iterative clarification loop driven by a satisfaction score (0-100). Generates targeted questions per round, always presents "End Clarify" as exit option, and stops when score >= 85 or user exits. Use after design approval to eliminate spec ambiguities before task breakdown begins.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -224,11 +224,11 @@ npx morph-spec state mark-output $ARGUMENTS clarifications
 
 ## Phase Outputs
 
-<!-- morph:outputs:clarify -->
+<!-- morph-outputs:clarify -->
 | Output | Path |
 |--------|------|
 | `clarifications` | `.morph/features/{feature}/1-design/clarifications.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 ## Advancement Criteria
 

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

@@ -1,9 +1,9 @@
 ---
-name: morph:phase-codebase-analysis
+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.4"
+cliVersion: "4.10.6"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase

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

@@ -1,15 +1,15 @@
 ---
-name: morph:phase-design
+name: morph-phase-design
 description: MORPH-SPEC Phase 2 (Design). Schema-first interactive design: reads EF models/Supabase/DB, validates findings with user, then routes to VSA Blueprint or DDD Architecture Blueprint based on config.architecture.style, producing spec.md, contracts.cs, schema-analysis.md, and decisions.md through a quality loop (score 0-100). Use after setup phase to create technical specifications grounded in the real database schema.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -485,7 +485,7 @@ npx morph-spec state set $ARGUMENTS costs.estimated {X.XX}
 
 ---
 
-<!-- morph:outputs:design -->
+<!-- morph-outputs:design -->
 | Output | Path |
 |--------|------|
 | `schemaAnalysis` | `.morph/features/{feature}/1-design/schema-analysis.md` |
@@ -494,6 +494,6 @@ npx morph-spec state set $ARGUMENTS costs.estimated {X.XX}
 | `contractsTs` | `.morph/features/{feature}/1-design/contracts.ts` |
 | `contractsVsa` | `.morph/features/{feature}/1-design/contracts-vsa.cs` |
 | `decisions` | `.morph/features/{feature}/1-design/decisions.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 Continue automatically to Phase 3 (Clarify) after approval.

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

@@ -1,18 +1,17 @@
 ---
-name: morph:phase-implement
+name: morph-phase-implement
 description: MORPH-SPEC Phase 5 (Implement). Executes feature tasks using TDD with checkpoint validation every 3 tasks, smoke tests via Playwright, and generates code + recap.md. Use after task list approval when starting feature implementation.
 argument-hint: "[feature-name]"
-disable-model-invocation: true
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 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 +97,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.
 
@@ -461,11 +460,11 @@ Agent(subagent_type=standards-architect, prompt=<filled prompts/code-quality-rev
 
 ## Phase Outputs
 
-<!-- morph:outputs:implement -->
+<!-- morph-outputs:implement -->
 | Output | Path |
 |--------|------|
 | `recap` | `.morph/features/{feature}/5-implement/recap.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 ---
 

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

@@ -1,16 +1,15 @@
 ---
-name: morph:phase-plan
+name: morph-phase-plan
 description: MORPH-SPEC Phase 4 (Plan). Generates a detailed implementation plan with exact file paths, TDD code blocks, and execution strategy analysis. Produces plan.md in 3-plan/. Use after clarify phase to create an actionable implementation plan before task breakdown.
 argument-hint: "[feature-name]"
-disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -118,7 +117,7 @@ Create `.morph/features/$ARGUMENTS/3-plan/plan.md` with this structure:
 ```markdown
 # {Feature Name} Implementation Plan
 
-> **For Claude:** Use morph:phase-implement to execute this plan.
+> **For Claude:** Use morph-phase-implement to execute this plan.
 
 **Goal:** {One sentence describing what will be built}
 
@@ -223,11 +222,11 @@ Use `AskUserQuestion` to capture approval before advancing. This gate prevents t
 
 ## Phase Outputs
 
-<!-- morph:outputs:plan -->
+<!-- morph-outputs:plan -->
 | Output | Path |
 |--------|------|
 | `plan` | `.morph/features/{feature}/3-plan/plan.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 ---
 

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

@@ -1,15 +1,15 @@
 ---
-name: morph:phase-setup
+name: morph-phase-setup
 description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech stack, activates relevant agents by reading agents.json, and confirms the feature environment. Use at the start of every MORPH-SPEC feature workflow after proposal approval to load standards and initialize the context.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -139,7 +139,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 npx morph-spec mcp setup`
 
 **Summary:** Show a status table for each MCP before proceeding:
 ```
@@ -161,10 +161,10 @@ npx 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 init --force` to install them.
+> ⚠ Some agents for your stack are not installed. Run `npx morph-spec setup-infra` to install them.
 
 Use `AskUserQuestion` with header `"Agents"` and options:
-- **Install now** — run `npx morph-spec init --force` to reinstall with current stack tags
+- **Install now** — run `npx 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.

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

@@ -1,16 +1,15 @@
 ---
-name: morph:phase-tasks
+name: morph-phase-tasks
 description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ordered implementation tasks (T001...TXXX) with dependencies, checkpoints every 3 tasks, and effort estimates, producing tasks.md. Use after design and clarification phases to create a structured implementation plan before coding starts.
 argument-hint: "[feature-name]"
-disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -301,12 +300,12 @@ Use `AskUserQuestion` to capture explicit approval before advancing. This gate p
 
 ## Phase Outputs
 
-<!-- morph:outputs:tasks -->
+<!-- morph-outputs:tasks -->
 | Output | Path |
 |--------|------|
 | `tasks` | `.morph/features/{feature}/4-tasks/tasks.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 ---
 
-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

@@ -1,15 +1,15 @@
 ---
-name: morph:phase-uiux
+name: morph-phase-uiux
 description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md, components.md, and flows.md using Playwright/Context7 MCPs. Use after setup for features with frontend UI components, pages, dashboards, forms, wizards, or visual interactions requiring design documentation.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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.
 
@@ -310,14 +310,14 @@ Use `AskUserQuestion` to capture explicit approval before advancing:
 
 ## Phase Outputs
 
-<!-- morph:outputs:uiux -->
+<!-- morph-outputs:uiux -->
 | Output | Path |
 |--------|------|
 | `uiDesignSystem` | `.morph/features/{feature}/2-ui/design-system.md` |
 | `uiMockups` | `.morph/features/{feature}/2-ui/mockups.md` |
 | `uiComponents` | `.morph/features/{feature}/2-ui/components.md` |
 | `uiFlows` | `.morph/features/{feature}/2-ui/flows.md` |
-<!-- /morph:outputs -->
+<!-- /morph-outputs -->
 
 ---
 

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

@@ -1,10 +1,10 @@
 ---
-name: morph:scope-escalation
+name: morph-scope-escalation
 description: Guided workflow for mid-implementation scope escalation — analyzes complexity discovery, recommends action, and executes phase regression or task expansion
 user-invocable: true
 argument-hint: "[feature-name]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.4"
+cliVersion: "4.10.6"
 ---
 
 # 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/framework/workflows/docs/STORY-DRIVEN-DEVELOPMENT.md

@@ -6,7 +6,7 @@
 
 ## 📋 Você Está Aqui
 
-Você acabou de terminar as fases 0-4 do MORPH:
+Você acabou de terminar as fases 0-4 do morph-
 - ✅ Criou `spec.md` (especificação técnica)
 - ✅ Criou `contracts.cs` (interfaces/DTOs)
 - ✅ Criou `tasks.json` (lista de tasks)

package/package.json

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

package/src/commands/project/doctor.js

@@ -707,7 +707,7 @@ export async function doctorCommand(options = {}) {
               checks.push({
                 name: 'agents completeness',
                 status: 'warn',
-                msg: `${missing.length} agent(s) missing for [${projectTags.join(', ')}]: ${names} — run morph-spec init --force`
+                msg: `${missing.length} agent(s) missing for [${projectTags.join(', ')}]: ${names} — run morph-spec setup-infra`
               });
               hasWarnings = true;
             } else {
@@ -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 {
@@ -871,7 +871,7 @@ export async function doctorCommand(options = {}) {
   logger.blank();
 
   if (hasErrors) {
-    logger.error('Some checks failed. Run "morph-spec init --force" to fix.');
+    logger.error('Some checks failed. Run "morph-spec setup-infra" to fix.');
     process.exit(1);
   } else if (hasWarnings) {
     logger.warn('Some checks need attention.');

package/src/commands/project/init.js

@@ -10,7 +10,7 @@ import {
   writeJson,
   writeFile
 } from '../../utils/file-copier.js';
-import { getInstalledCLIVersion } from '../../utils/version-checker.js';
+import { getInstalledCLIVersion, checkProjectOutdated } from '../../utils/version-checker.js';
 import { installClaudeHooks } from '../../utils/claude-settings-manager.js';
 import inquirer from 'inquirer';
 import { detectProject } from '../../lib/detectors/index.js';
@@ -27,6 +27,7 @@ import { setupInfra, installRulesForStack } from '../../scripts/setup-infra.js';
 import { installSkills } from '../../utils/skills-installer.js';
 import { installAgents, installDomainAgents } from '../../utils/agents-installer.js';
 import { getProjectTags } from '../../lib/stack-filter.js';
+import { updateCommand } from './update.js';
 
 export async function initCommand(options) {
   const targetPath = options.path || process.cwd();
@@ -39,7 +40,14 @@ export async function initCommand(options) {
   const morphPath = join(targetPath, '.morph');
   if (await pathExists(morphPath)) {
     if (!options.force) {
-      logger.warn('MORPH already initialized in this directory.');
+      // Check if project version is outdated — auto-update instead of blocking
+      const projectCheck = await checkProjectOutdated(targetPath);
+      if (projectCheck.isOutdated) {
+        logger.info(`MORPH already initialized (v${projectCheck.current}). Framework update available (v${projectCheck.cliVersion}).`);
+        logger.blank();
+        return updateCommand(options);
+      }
+      logger.warn('MORPH already initialized in this directory (up to date).');
       logger.dim('Use --force to overwrite existing installation.');
       process.exit(1);
     }
@@ -415,7 +423,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();