@polymorphism-tech/morph-spec 4.10.4 → 4.10.6

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.4  
+**Version:** 4.10.6  
 **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                             |
 
 
 ---
@@ -358,7 +358,7 @@ npm install -g @polymorphism-tech/morph-spec
 
 ### Hook not triggering on SessionStart
 
-Ensure `.claude/settings.local.json` is not gitignored in your project. The file must be present for Claude Code to load hooks. If it is missing, re-run `morph-spec init --force`.
+Ensure `.claude/settings.local.json` is not gitignored in your project. The file must be present for Claude Code to load hooks. If it is missing, re-run `morph-spec setup-infra` or `morph-spec init --force`.
 
 ---
 
@@ -376,4 +376,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.10.4 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.10.6 by [Polymorphism Tech](https://polymorphism.tech)*

package/bin/morph-spec.js

@@ -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
@@ -197,6 +197,8 @@ phaseCommand
   .command('advance <feature>')
   .description('Validate current phase and advance to next')
   .option('--skip-optional', 'Skip optional phases (uiux, sync)')
+  .option('--skip-approval', 'Skip approval gate checks')
+  .option('--force', 'Force phase transition even if state machine rejects it')
   .action((feature, options) => advancePhaseCommand(feature, options));
 
 phaseCommand

package/bin/task-manager.js

@@ -121,6 +121,11 @@ class TaskManager {
       throw new Error(`tasks.md found but no tasks could be parsed for '${featureName}'.\n  Ensure tasks use the format: ### T001 — Title  or  ### T001: Title`);
     }
 
+    // Persist initial taskList so counters are visible in `state get` even if
+    // validation fails later and the completion save never runs.
+    syncCounters(feature);
+    saveState(state);
+
     const results = [];
     const tasksToComplete = [];
 
@@ -304,14 +309,20 @@ class TaskManager {
     }
 
     // Suggest next task
+    const activeTasks = taskList.filter(t => t.status !== 'expanded');
+    const allCompleted = activeTasks.length > 0 && activeTasks.every(t => t.status === 'completed');
     const nextTask = this.getNextTask(taskList);
-    if (nextTask) {
+
+    if (allCompleted) {
+      console.log(chalk.green('\n🎉 All tasks completed!'));
+    } else if (nextTask) {
       console.log(chalk.cyan(`\n⏭️  Next: ${nextTask.id} - ${nextTask.title}`));
       if (nextTask.dependencies && nextTask.dependencies.length > 0) {
         console.log(chalk.gray(`   Dependencies: ${nextTask.dependencies.join(', ')}`));
       }
     } else {
-      console.log(chalk.green('\n🎉 All tasks completed!'));
+      const remaining = activeTasks.filter(t => t.status !== 'completed');
+      console.log(chalk.yellow(`\n⏸️  No tasks available — ${remaining.length} task(s) have unmet dependencies`));
     }
 
     return results;
@@ -490,7 +501,7 @@ class TaskManager {
         const result = await runValidation('.', featureName, { verbose: false });
         validationNote = result.passed
           ? ' | Validation: PASSED'
-          : ` | Validation: ${result.errors.length} errors, ${result.warnings.length} warnings`;
+          : ` | Validation: ${result.errors} errors, ${result.warnings} warnings`;
       } catch {
         // No validation available
       }
@@ -743,9 +754,13 @@ class TaskManager {
     }
 
     const taskList = await ensureTaskList(feature, featureName);
+    const activeTasks = taskList.filter(t => t.status !== 'expanded');
+    const allCompleted = activeTasks.length > 0 && activeTasks.every(t => t.status === 'completed');
     const nextTask = this.getNextTask(taskList);
 
-    if (nextTask) {
+    if (allCompleted) {
+      console.log(chalk.green('🎉 All tasks completed!'));
+    } else if (nextTask) {
       console.log(chalk.cyan(`\n⏭️  Next task: ${nextTask.id} - ${nextTask.title}`));
       if (nextTask.dependencies && nextTask.dependencies.length > 0) {
         console.log(chalk.gray(`   Dependencies: ${nextTask.dependencies.join(', ')}`));
@@ -755,7 +770,8 @@ class TaskManager {
         nextTask.files.forEach(f => console.log(chalk.gray(`     - ${f}`)));
       }
     } else {
-      console.log(chalk.green('🎉 All tasks completed!'));
+      const remaining = activeTasks.filter(t => t.status !== 'completed');
+      console.log(chalk.yellow(`\n⏸️  No tasks available — ${remaining.length} task(s) have unmet dependencies`));
     }
   }
 }

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.10.4",
+  "version": "4.10.6",
   "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.4 by Polymorphism Tech*
+*morph-spec v4.10.6 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.4 by Polymorphism Tech*
+*morph-spec v4.10.6 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/backend/hangfire-orchestrator.md

@@ -3,7 +3,7 @@ name: hangfire-orchestrator
 description: Hangfire Orchestrator specialist for background job design, recurring task scheduling, queue management, and idempotent job patterns in .NET. Use when implementing background jobs, scheduling recurring tasks, managing job queues, or integrating Hangfire with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
+  - hangfire
 ---
 
 # Hangfire Orchestrator

package/framework/agents/backend/ms-agent-expert.md

@@ -3,7 +3,8 @@ name: ms-agent-expert
 description: Microsoft Agent Framework Expert for Semantic Kernel, AI extensions, function calling, MCP/A2A protocols, and agentic pipeline implementation. Use when building AI agents with Semantic Kernel, implementing tool/plugin calling, designing multi-agent workflows, or integrating LLMs with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
+  - semantic-kernel
+  - ms-agents
 ---
 
 # Agent Framework Expert

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/integrations/asaas-financial.md

@@ -3,7 +3,7 @@ name: asaas-financial
 description: Asaas Financial specialist for Asaas API integration, payment processing, Pix/boleto billing, and subscription management in Brazilian projects. Use when integrating Asaas payments, implementing billing flows, handling payment webhooks, or building subscription management features.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
+  - asaas
 ---
 
 # Asaas Financial

package/framework/agents/integrations/clerk-auth.md

@@ -3,8 +3,7 @@ name: clerk-auth
 description: Clerk Auth specialist for Clerk SDK integration, social login, JWT session management, and user management in Next.js and .NET projects. Use when integrating Clerk authentication, implementing social login flows, managing user sessions with Clerk JWT, or protecting routes with Clerk middleware.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
-  - nextjs
+  - clerk
 ---
 
 # Clerk Auth

package/framework/agents/integrations/hangfire-integration.md

@@ -3,7 +3,7 @@ name: hangfire-orchestrator-integration
 description: Hangfire integration specialist for connecting background jobs with external services, implementing webhook handlers, and building event-driven workflows in .NET. Use when integrating Hangfire with third-party APIs, processing webhooks asynchronously, or designing event-driven job pipelines.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
+  - hangfire
 ---
 
 # Hangfire Orchestrator

package/framework/agents/integrations/resend-email.md

@@ -3,7 +3,7 @@ name: resend-email
 description: Resend Email specialist for transactional email, HTML/React email templates, Resend API integration, and notification systems in .NET and Next.js. Use when implementing email notifications, integrating Resend API, creating transactional email templates, or configuring email delivery in MORPH-SPEC projects.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 stacks:
-  - dotnet
+  - resend
 ---
 
 # Resend Email

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/post-tool-use/context-refresh.js

@@ -102,7 +102,7 @@ function isContextInitialized() {
     const contextPath = join(process.cwd(), '.morph/context/README.md');
     if (!existsSync(contextPath)) return false;
     const content = readFileSync(contextPath, 'utf-8');
-    return !content.includes('Run /morph:init to generate');
+    return !content.includes('Run /morph-init to generate');
   } catch {
     return false;
   }

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/phases.json

@@ -19,7 +19,7 @@
       ],
       "agentTiers": [1],
       "requiredSkills": [
-        { "trigger": "beforePhaseStart", "skill": "morph:brainstorming" }
+        { "trigger": "beforePhaseStart", "skill": "morph-brainstorming" }
       ]
     },
     "setup": {
@@ -58,9 +58,9 @@
       ],
       "agentTiers": [1, 2, 3],
       "requiredSkills": [
-        { "trigger": "beforeArchitecturalDecision", "skill": "morph:brainstorming" },
-        { "trigger": "onHTMLPrototypeAvailable",    "skill": "morph:replicate" },
-        { "trigger": "beforePhaseComplete",         "skill": "morph:frontend-review" }
+        { "trigger": "beforeArchitecturalDecision", "skill": "morph-brainstorming" },
+        { "trigger": "onHTMLPrototypeAvailable",    "skill": "morph-replicate" },
+        { "trigger": "beforePhaseComplete",         "skill": "morph-frontend-review" }
       ]
     },
     "design": {
@@ -82,11 +82,11 @@
       ],
       "agentTiers": [1, 2, 3, 4],
       "requiredSkills": [
-        { "trigger": "beforePhaseStart",             "skill": "morph:phase-design" },
-        { "trigger": "beforePhaseStart",             "skill": "morph:phase-codebase-analysis" },
-        { "trigger": "beforeArchitecturalDecision",  "skill": "morph:brainstorming" },
-        { "trigger": "onExternalServiceIntegration", "skill": "morph:simulation-checklist" },
-        { "trigger": "beforePhaseComplete",          "skill": "morph:verification-before-completion" }
+        { "trigger": "beforePhaseStart",             "skill": "morph-phase-design" },
+        { "trigger": "beforePhaseStart",             "skill": "morph-phase-codebase-analysis" },
+        { "trigger": "beforeArchitecturalDecision",  "skill": "morph-brainstorming" },
+        { "trigger": "onExternalServiceIntegration", "skill": "morph-simulation-checklist" },
+        { "trigger": "beforePhaseComplete",          "skill": "morph-verification-before-completion" }
       ]
     },
     "clarify": {
@@ -105,8 +105,8 @@
       "pausePoints": [],
       "agentTiers": [1, 2],
       "requiredSkills": [
-        { "trigger": "beforePhaseStart",    "skill": "morph:phase-clarify" },
-        { "trigger": "beforePhaseComplete", "skill": "morph:verification-before-completion" }
+        { "trigger": "beforePhaseStart",    "skill": "morph-phase-clarify" },
+        { "trigger": "beforePhaseComplete", "skill": "morph-verification-before-completion" }
       ]
     },
     "plan": {
@@ -127,8 +127,8 @@
       ],
       "agentTiers": [1, 2],
       "requiredSkills": [
-        { "trigger": "beforePhaseStart",    "skill": "morph:phase-plan" },
-        { "trigger": "beforePhaseComplete", "skill": "morph:verification-before-completion" }
+        { "trigger": "beforePhaseStart",    "skill": "morph-phase-plan" },
+        { "trigger": "beforePhaseComplete", "skill": "morph-verification-before-completion" }
       ]
     },
     "tasks": {
@@ -150,7 +150,7 @@
       "agentTiers": [1, 2, 3],
       "requiredSkills": [
         { "trigger": "onParallelTasksIdentified", "skill": "superpowers:dispatching-parallel-agents" },
-        { "trigger": "beforePhaseComplete",       "skill": "morph:verification-before-completion" }
+        { "trigger": "beforePhaseComplete",       "skill": "morph-verification-before-completion" }
       ]
     },
     "implement": {
@@ -171,11 +171,11 @@
       "agentTiers": [1, 2, 3, 4],
       "requiredSkills": [
         { "trigger": "beforeEachTask",    "skill": "superpowers:test-driven-development" },
-        { "trigger": "beforeTaskDone",    "skill": "morph:verification-before-completion" },
+        { "trigger": "beforeTaskDone",    "skill": "morph-verification-before-completion" },
         { "trigger": "onBugOrUnexpected", "skill": "superpowers:systematic-debugging" },
-        { "trigger": "afterAllTasks",     "skill": "morph:post-implementation" },
+        { "trigger": "afterAllTasks",     "skill": "morph-post-implementation" },
         { "trigger": "afterAllTasks",     "skill": "superpowers:requesting-code-review" },
-        { "trigger": "beforePR",          "skill": "morph:checklist" }
+        { "trigger": "beforePR",          "skill": "morph-checklist" }
       ]
     },
     "sync": {

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-brainstorming/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: morph:brainstorming
+name: morph-brainstorming
 description: Morph-spec-aware brainstorming that loads project context, explores multiple design approaches, asks clarifying questions, and produces proposal.md or decisions.md. Use before designing a feature, when facing architectural decisions with multiple valid approaches, or when a feature needs requirements exploration before committing to a direction.
 user-invocable: true
 argument-hint: "[feature-name or topic]"

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

@@ -1,5 +1,5 @@
 ---
-name: morph:checklist
+name: morph-checklist
 description: Pre-deploy, security, SEO, performance, accessibility, and LGPD compliance checklists for MORPH-SPEC projects. Use before deploying to production, during security audits, when optimizing for SEO or performance, or when validating Brazilian LGPD data protection compliance.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
@@ -7,7 +7,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 # MORPH Checklists
 
-Types: `deploy`, `security`, `seo`, `performance`, `accessibility`, `legal-brazil`, `simulation` (see skill: `morph:simulation-checklist`)
+Types: `deploy`, `security`, `seo`, `performance`, `accessibility`, `legal-brazil`, `simulation` (see skill: `morph-simulation-checklist`)
 
 ---
 

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

@@ -1,5 +1,5 @@
 ---
-name: morph:code-review
+name: morph-code-review
 description: .NET/C# code review checklist covering naming conventions, architecture layer integrity, async patterns, logging, error handling, DI lifetimes, and DTO contracts. Use after implementing .NET code, before creating PRs, or when reviewing C# code for compliance with MORPH-SPEC standards.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep

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

@@ -1,5 +1,5 @@
 ---
-name: morph:code-review-nextjs
+name: morph-code-review-nextjs
 description: Next.js code review checklist covering naming conventions, component architecture (Server vs Client), data fetching patterns, form implementation, state management, TypeScript/Zod discipline, feature boundaries, and testing. Use after implementing Next.js code, before creating PRs, or when reviewing TSX/TS code for compliance with MORPH-SPEC Next.js standards.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep