@polymorphism-tech/morph-spec 4.10.3 → 4.10.5

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.5  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -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.5 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';
@@ -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.3",
+  "version": "4.10.5",
   "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.3 by Polymorphism Tech*
+*morph-spec v4.10.5 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -203,4 +203,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.10.3 by Polymorphism Tech*
+*morph-spec v4.10.5 by Polymorphism Tech*

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/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/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

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.
@@ -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".
 

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,10 +1,10 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Clarify — Phase 3
@@ -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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase

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

@@ -1,10 +1,10 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Design — Phase 2
@@ -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,12 +1,11 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
 ---
 
@@ -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,11 +1,10 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Plan — Phase 4
@@ -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,10 +1,10 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Setup — Phase 1
@@ -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:
 ```

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

@@ -1,11 +1,10 @@
 ---
-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.3"
+cliVersion: "4.10.5"
 ---
 
 # MORPH Tasks — Phase 4
@@ -301,11 +300,11 @@ 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 -->
 
 ---