@polymorphism-tech/morph-spec 4.10.9 → 4.11.0

package/framework/skills/level-0-meta/morph-tool-usage-guide/references/tools-per-phase.md

@@ -14,10 +14,10 @@
 | Read project context | **Read** `.morph/context/README.md` | Single known file |
 | Read config | **Read** `.morph/config.json` | Single known file |
 | Find existing features | **Glob** `.morph/features/*/0-proposal/proposal.md` | Pattern search |
-| Detect project stack | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent` | agents.json is the source of truth |
+| Detect project stack | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `morph-spec state add-agent` | agents.json is the source of truth |
 | Research external requirement | **WebSearch** | Current information needed |
-| Render proposal template | **Bash** `npx morph-spec template render docs/proposal ...` | CLI command |
-| Update state | **Bash** `npx morph-spec state mark-output {feature} proposal` | CLI command |
+| Render proposal template | **Bash** `morph-spec template render docs/proposal ...` | CLI command |
+| Update state | **Bash** `morph-spec state mark-output {feature} proposal` | CLI command |
 
 **MCPs used:** None typically. GitHub MCP if feature comes from an issue.
 
@@ -34,14 +34,14 @@
 
 | Action | Tool | Why |
 |--------|------|-----|
-| Verify feature state | **Bash** `npx morph-spec state get {feature}` | CLI command |
-| Detect agents + standards | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent {f} {id}` per match | Keyword matching is fast inline |
+| Verify feature state | **Bash** `morph-spec state get {feature}` | CLI command |
+| Detect agents + standards | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `morph-spec state add-agent {f} {id}` per match | Keyword matching is fast inline |
 | Read project context | **Read** `.morph/context/README.md` | Single file |
 | Read config | **Read** `.morph/config.json` | Single file |
 | Scan project structure | **Glob** `src/**/*.{ts,tsx,cs}` | Understand codebase layout |
 | Get repo metadata | **GitHub MCP** `get_repo()` | Structured repo info (if MCP available) |
-| Get dispatch config for next phases | **Bash** `npx morph-spec dispatch-agents {feature} design` | Shows which agents will be dispatched in design phase |
-| Update state | **Bash** `npx morph-spec state set ...` | CLI command |
+| Get dispatch config for next phases | **Bash** `morph-spec dispatch-agents {feature} design` | Shows which agents will be dispatched in design phase |
+| Update state | **Bash** `morph-spec state set ...` | CLI command |
 
 **MCPs used:** GitHub (optional — for repo metadata).
 
@@ -67,9 +67,9 @@
 | Inspecionar estrutura da página | **Playwright MCP** `browser_snapshot()` | **WebFetch** + parse manual |
 | Testar layout responsivo | **Playwright MCP** `browser_resize()` + `browser_take_screenshot()` | Manual testing |
 | Search for design references | **WebSearch** + **WebFetch** | External inspiration |
-| Render UI templates | **Bash** `npx morph-spec template render docs/ui-mockups ...` | CLI command |
-| Generate design system from CSS | **Bash** `npx morph-spec generate design-system --scan` | CLI command |
-| Update state | **Bash** `npx morph-spec state mark-output {feature} uiDesignSystem && npx morph-spec state mark-output {feature} uiMockups && npx morph-spec state mark-output {feature} uiComponents && npx morph-spec state mark-output {feature} uiFlows` | CLI command |
+| Render UI templates | **Bash** `morph-spec template render docs/ui-mockups ...` | CLI command |
+| Generate design system from CSS | **Bash** `morph-spec generate design-system --scan` | CLI command |
+| Update state | **Bash** `morph-spec state mark-output {feature} uiDesignSystem && morph-spec state mark-output {feature} uiMockups && morph-spec state mark-output {feature} uiComponents && morph-spec state mark-output {feature} uiFlows` | CLI command |
 
 **MCPs used:** Playwright (live preview, page inspection), Context7 (component docs).
 
@@ -87,7 +87,7 @@
 | Action | Tool | Why |
 |--------|------|-----|
 | Read proposal + UI specs | **Read** output files | Single known files |
-| **Get dispatch config** | **Bash** `npx morph-spec dispatch-agents {feature} design` | Which agents to spawn + their task prompts |
+| **Get dispatch config** | **Bash** `morph-spec dispatch-agents {feature} design` | Which agents to spawn + their task prompts |
 | **Dispatch domain-architect** (parallel) | **Task** subagent with prompt from dispatch config | Analyze DDD complexity independently |
 | **Dispatch tech leads** (parallel) | **Task** subagents (dotnet-senior, nextjs-expert, etc.) | Validate architecture independently |
 | Get database schema | **Supabase MCP** `list_tables()`, `get_table_schema()` | **PREFERRED** — real schema data |
@@ -99,11 +99,11 @@
 | Look up library for ADR | **Context7 MCP** `query_docs()` | Compare library capabilities |
 | Check existing code patterns | **GitHub MCP** `search_code()` | Find patterns in large repos |
 | **Fallback:** Search codebase | **Grep** patterns across project | When no GitHub MCP |
-| Render contracts template (detected level) | **Bash** `npx morph-spec template render code/dotnet/contracts/contracts-level{N}.cs ...` where N = level detected | CLI command |
-| Render spec template | **Bash** `npx morph-spec template render docs/spec ...` | CLI command |
-| Render decisions template | **Bash** `npx morph-spec template render docs/decisions ...` | CLI command |
+| Render contracts template (detected level) | **Bash** `morph-spec template render code/dotnet/contracts/contracts-level{N}.cs ...` where N = level detected | CLI command |
+| Render spec template | **Bash** `morph-spec template render docs/spec ...` | CLI command |
+| Render decisions template | **Bash** `morph-spec template render docs/decisions ...` | CLI command |
 | Create schema-analysis.md | **Write** to output directory | Document findings |
-| Update state | **Bash** `npx morph-spec state mark-output {feature} schemaAnalysis && npx morph-spec state mark-output {feature} spec && npx morph-spec state mark-output {feature} contracts && npx morph-spec state mark-output {feature} decisions` | CLI command |
+| Update state | **Bash** `morph-spec state mark-output {feature} schemaAnalysis && morph-spec state mark-output {feature} spec && morph-spec state mark-output {feature} contracts && morph-spec state mark-output {feature} decisions` | CLI command |
 
 **MCPs used:** Supabase (schema analysis), Context7 (library research), GitHub (code search).
 
@@ -131,8 +131,8 @@
 | Check known issues/limitations | **GitHub MCP** `search_issues()` | Library bugs affecting design |
 | Research edge case behavior | **WebSearch** | External knowledge for edge cases |
 | Update spec with clarifications | **Edit** spec.md | Preserve existing content, add sections |
-| Create clarifications.md | **Bash** `npx morph-spec template render docs/clarifications ...` | Use template |
-| Update state | **Bash** `npx morph-spec state mark-output {feature} clarifications` | CLI command |
+| Create clarifications.md | **Bash** `morph-spec template render docs/clarifications ...` | Use template |
+| Update state | **Bash** `morph-spec state mark-output {feature} clarifications` | CLI command |
 
 **MCPs used:** Context7 (validate feasibility), GitHub (known issues).
 
@@ -150,16 +150,16 @@
 | Action | Tool | Why |
 |--------|------|-----|
 | Read spec + contracts + decisions | **Read** all output files | Full context needed |
-| **Get dispatch config** | **Bash** `npx morph-spec dispatch-agents {feature} tasks` | Which domain experts to consult |
+| **Get dispatch config** | **Bash** `morph-spec dispatch-agents {feature} tasks` | Which domain experts to consult |
 | Analyze implementation complexity | **Grep** patterns in existing code | Estimate effort from codebase size |
 | Count existing similar patterns | **Glob** `**/Services/**/*.cs` | Understand scope |
 | **Dispatch domain experts** (when spec is complex) | **Task** subagents per domain | Parallel per-domain task planning |
 | Look up implementation patterns | **Context7 MCP** `query_docs()` | Estimate task complexity accurately |
 | Create GitHub issues from tasks | **GitHub MCP** `create_issue()` | Sync tasks to project management |
 | **Fallback:** Create issues via CLI | **Bash** `gh issue create ...` | When no GitHub MCP |
-| Render tasks template | **Bash** `npx morph-spec template render docs/tasks ...` | CLI command |
-| Mark tasks output | **Bash** `npx morph-spec state mark-output {feature} tasks` | CLI command |
-| Update state with task count | **Bash** `npx morph-spec state set ... tasks.total N` | CLI command |
+| Render tasks template | **Bash** `morph-spec template render docs/tasks ...` | CLI command |
+| Mark tasks output | **Bash** `morph-spec state mark-output {feature} tasks` | CLI command |
+| Update state with task count | **Bash** `morph-spec state set ... tasks.total N` | CLI command |
 
 **MCPs used:** Context7 (complexity estimation), GitHub (issue creation).
 
@@ -178,7 +178,7 @@
 | Action | Tool | Why |
 |--------|------|-----|
 | Read task details | **Read** tasks.json, spec.md, contracts.cs | Implementation reference |
-| **Check parallelization viability** | **Bash** `npx morph-spec dispatch-agents {feature} implement` | Whether to dispatch parallel implementers |
+| **Check parallelization viability** | **Bash** `morph-spec dispatch-agents {feature} implement` | Whether to dispatch parallel implementers |
 | **Dispatch per-domain implementers** (when viable) | **Task** subagents — one per domain group | Backend tasks + frontend tasks run in parallel |
 | Create new files | **Write** new source files | New entities, services, pages |
 | Modify existing files | **Edit** existing source files | Add features to existing code |
@@ -187,15 +187,15 @@
 | **Fallback:** Run migrations | **Bash** `npx supabase migration ...` or `dotnet ef ...` | CLI tools |
 | Build project | **Bash** `dotnet build` or `npm run build` | Verify compilation |
 | Run tests | **Bash** `dotnet test` or `npm test` | Verify implementation |
-| Checkpoint validation | **Bash** `npx morph-spec checkpoint ...` | Every 3 tasks |
+| Checkpoint validation | **Bash** `morph-spec checkpoint ...` | Every 3 tasks |
 | Create RLS policies | **Supabase MCP** `query()` | Security policies |
 | Create infrastructure | **Bash** `az bicep ...` or Bicep files via Write | IaC |
 | Create PR | **GitHub MCP** `create_pull_request()` or **Bash** `gh pr create` | Ship code |
-| Mark task done | **Bash** `npx morph-spec task done T001` | State tracking |
+| Mark task done | **Bash** `morph-spec task done T001` | State tracking |
 | Smoke test feature no browser | **Playwright MCP** `browser_navigate()` + `browser_snapshot()` | Manual testing |
 | Verificar erros de console | **Playwright MCP** `browser_console_messages()` | Browser DevTools |
 | Screenshot para recap.md | **Playwright MCP** `browser_take_screenshot()` | Manual screenshot |
-| Mark recap output | **Bash** `npx morph-spec state mark-output {feature} recap` | CLI command |
+| Mark recap output | **Bash** `morph-spec state mark-output {feature} recap` | CLI command |
 
 **MCPs used:** Supabase (migrations, RLS), Context7 (API lookup), GitHub (PRs), Playwright (smoke test, verification).
 

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

@@ -86,16 +86,16 @@ allowed-tools: Read, Bash, Glob, Grep
 
 ```bash
 # Run full feature validation
-npx morph-spec validate-feature {feature-name}
+morph-spec validate-feature {feature-name}
 
 # Check feature state and phase
-npx morph-spec state get {feature-name}
+morph-spec state get {feature-name}
 
 # Check approval gates
-npx morph-spec approval-status {feature-name}
+morph-spec approval-status {feature-name}
 
 # Check overall project status
-npx morph-spec status
+morph-spec status
 ```
 
 ---
@@ -111,8 +111,8 @@ Before running `morph-spec task done`:
 
 ```bash
 # Verify before marking done
-npx morph-spec validate-feature {feature}
-npx morph-spec task done {feature} T001
+morph-spec validate-feature {feature}
+morph-spec task done {feature} T001
 ```
 
 ---
@@ -122,8 +122,8 @@ npx morph-spec task done {feature} T001
 Every 3 tasks, run full checkpoint validation:
 
 ```bash
-npx morph-spec checkpoint-save {feature}
-npx morph-spec validate-feature {feature}
+morph-spec checkpoint-save {feature}
+morph-spec validate-feature {feature}
 ```
 
 If validation fails:

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

@@ -4,7 +4,7 @@ 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.9"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Clarify — Phase 3
@@ -32,7 +32,7 @@ Eliminate spec ambiguities through an iterative question loop until the spec has
 | Ask clarifying questions | **AskUserQuestion** (never plain text) | — |
 | Update spec with clarifications | **Edit** spec.md | — |
 | Create clarifications.md | **Write** | — |
-| Update state | **Bash** `npx morph-spec state mark-output $ARGUMENTS clarifications` | — |
+| Update state | **Bash** `morph-spec state mark-output $ARGUMENTS clarifications` | — |
 
 ---
 
@@ -67,7 +67,7 @@ Before each round, calculate the **Satisfaction Score (0-100)** by evaluating th
 **Step 0 (BEFORE any writing) — Ensure clarify phase:**
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field in the output:
@@ -75,8 +75,8 @@ Check the `"phase"` field in the output:
 **If `"phase": "clarify"`** → correct phase, proceed.
 
 **If `"phase": "design"`** → run in sequence:
-1. `npx morph-spec approve $ARGUMENTS design`
-2. `npx morph-spec phase advance $ARGUMENTS` (→ clarify)
+1. `morph-spec approve $ARGUMENTS design`
+2. `morph-spec phase advance $ARGUMENTS` (→ clarify)
 
 **Any other value** → STOP — inconsistent state, report to user.
 
@@ -217,7 +217,7 @@ Write to `.morph/features/$ARGUMENTS/1-design/clarifications.md`:
 **Step 2: Update State**
 
 ```bash
-npx morph-spec state mark-output $ARGUMENTS clarifications
+morph-spec state mark-output $ARGUMENTS clarifications
 ```
 
 ---
@@ -241,7 +241,7 @@ npx morph-spec state mark-output $ARGUMENTS clarifications
 ---
 
 ```bash
-npx morph-spec phase advance $ARGUMENTS
+morph-spec phase advance $ARGUMENTS
 ```
 
 Continue automatically to Phase 4 (Plan) after clarifications.md is generated.

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.9"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase
@@ -154,7 +154,7 @@ This ensures `contracts.cs` can be generated mechanically, without manual interp
 The template is at `framework/templates/docs/schema-analysis.md`. Use it via:
 
 ```bash
-npx morph-spec template render docs/schema-analysis \
+morph-spec template render docs/schema-analysis \
   .morph/features/{feature}/1-design/schema-analysis.md \
   '{
     "FEATURE_NAME": "{feature}",
@@ -213,7 +213,7 @@ Create a map of:
 Use the template at `framework/templates/docs/schema-analysis.md`:
 
 ```bash
-npx morph-spec template render docs/schema-analysis \
+morph-spec template render docs/schema-analysis \
   .morph/features/{feature-name}/1-design/schema-analysis.md \
   '{ "FEATURE_NAME": "{feature-name}", "DATE": "..." }'
 ```
@@ -223,7 +223,7 @@ OR use **Write** tool to create directly with collected data.
 ### Step 5: Update State
 
 ```bash
-npx morph-spec state mark-output {feature-name} schema-analysis
+morph-spec state mark-output {feature-name} schema-analysis
 ```
 
 ---

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

@@ -4,7 +4,7 @@ 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.9"
+cliVersion: "4.11.0"
 ---
 
 # MORPH Design — Phase 2
@@ -37,11 +37,11 @@ Schema-first interactive design: read the real schema, validate with user, gener
 | Dispatch domain-architect | **Agent** `subagent_type=domain-architect` + `prompt=agent.taskPrompt` | — |
 | Dispatch tech leads | **Agent** for each active agent from dispatch config | — |
 | Research library | **Context7 MCP** `query_docs()` | **WebSearch** + **WebFetch** |
-| Render contracts VSA | **Bash** `npx morph-spec template render dotnet-contracts-vsa ...` | — |
-| Render contracts DDD | **Bash** `npx morph-spec template render dotnet-contracts-level{N} ...` | — |
-| Render spec.md | **Bash** `npx morph-spec template render docs/spec ...` | — |
-| Render decisions.md | **Bash** `npx morph-spec template render docs/decisions ...` | — |
-| Update state | **Bash** `npx morph-spec state mark-output $ARGUMENTS <type>` | — |
+| Render contracts VSA | **Bash** `morph-spec template render dotnet-contracts-vsa ...` | — |
+| Render contracts DDD | **Bash** `morph-spec template render dotnet-contracts-level{N} ...` | — |
+| Render spec.md | **Bash** `morph-spec template render docs/spec ...` | — |
+| Render decisions.md | **Bash** `morph-spec template render docs/decisions ...` | — |
+| Update state | **Bash** `morph-spec state mark-output $ARGUMENTS <type>` | — |
 
 **Anti-patterns:**
 - Do not generate contracts before reading the real schema — guessed field names corrupt the entire design
@@ -72,7 +72,7 @@ Update each to `in_progress` before starting and `completed` after finishing.
 **STEP 0 (BEFORE any reads or writes) — Ensure phase is design:**
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field in the output:
@@ -80,12 +80,12 @@ Check the `"phase"` field in the output:
 **If `"phase": "design"`** → phase is correct, proceed.
 
 **If `"phase": "proposal"`** → execute in sequence:
-1. `npx morph-spec state mark-output $ARGUMENTS proposal`
-2. `npx morph-spec phase advance $ARGUMENTS` (→ setup)
-3. `npx morph-spec phase advance $ARGUMENTS` (→ design)
+1. `morph-spec state mark-output $ARGUMENTS proposal`
+2. `morph-spec phase advance $ARGUMENTS` (→ setup)
+3. `morph-spec phase advance $ARGUMENTS` (→ design)
 
 **If `"phase": "setup"`** → execute:
-1. `npx morph-spec phase advance $ARGUMENTS` (→ design)
+1. `morph-spec phase advance $ARGUMENTS` (→ design)
 
 **Any other value** → do not proceed — inconsistent state, report to user.
 
@@ -197,7 +197,7 @@ Use `AskUserQuestion`:
 #### 2-VSA.1 Dispatch vsa-architect
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS design
+morph-spec dispatch-agents $ARGUMENTS design
 ```
 
 Use the `taskPrompt` from the `vsa-architect` agent in the result. Call:
@@ -255,7 +255,7 @@ Read the proposal and evaluate using the 5 detection questions in `framework/sta
 #### 2-DDD.2 Dispatch domain-architect
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS design
+morph-spec dispatch-agents $ARGUMENTS design
 ```
 
 Use the `taskPrompt` from the `domain-architect` agent in the result. Call:
@@ -314,7 +314,7 @@ Read the spec-authoring-guide first, then create `.morph/features/$ARGUMENTS/1-d
 **Mandatory source:** fields from `schema-analysis.md` + operations from the VSA Blueprint.
 
 ```bash
-npx morph-spec template render \
+morph-spec template render \
   dotnet-contracts-vsa \
   .morph/features/$ARGUMENTS/1-design/contracts.cs \
   '{
@@ -340,7 +340,7 @@ After rendering, fill in the `// placeholder:` sections with real fields from sc
 
 ```bash
 # Replace {N} with the detected level (1, 2, or 3):
-npx morph-spec template render \
+morph-spec template render \
   dotnet-contracts-level{N} \
   .morph/features/$ARGUMENTS/1-design/contracts.cs \
   '{
@@ -364,7 +364,7 @@ For TypeScript/Next.js projects, generate `contracts.ts` instead of `contracts.c
 ### Generate decisions.md
 
 ```bash
-npx morph-spec template render docs/decisions \
+morph-spec template render docs/decisions \
   .morph/features/$ARGUMENTS/1-design/decisions.md \
   '{"FEATURE_NAME": "$ARGUMENTS", "DATE": "{{TODAY}}", "decisions": []}'
 ```
@@ -448,15 +448,15 @@ Update spec.md, contracts, and decisions.md with the answers received. Recalcula
 ## Post-Loop: Update State
 
 ```bash
-npx morph-spec state mark-output $ARGUMENTS schema-analysis
-npx morph-spec state mark-output $ARGUMENTS spec
-npx morph-spec state mark-output $ARGUMENTS contracts
-npx morph-spec state mark-output $ARGUMENTS decisions
+morph-spec state mark-output $ARGUMENTS schema-analysis
+morph-spec state mark-output $ARGUMENTS spec
+morph-spec state mark-output $ARGUMENTS contracts
+morph-spec state mark-output $ARGUMENTS decisions
 ```
 
 If Azure costs were estimated:
 ```bash
-npx morph-spec state set $ARGUMENTS costs.estimated {X.XX}
+morph-spec state set $ARGUMENTS costs.estimated {X.XX}
 ```
 
 ## MANDATORY PAUSE
@@ -477,8 +477,8 @@ npx morph-spec state set $ARGUMENTS costs.estimated {X.XX}
 
 - **"Approve and continue"** →
   ```bash
-  npx morph-spec approve $ARGUMENTS design
-  npx morph-spec phase advance $ARGUMENTS
+  morph-spec approve $ARGUMENTS design
+  morph-spec phase advance $ARGUMENTS
   ```
 - **"I have feedback" / Other** → apply feedback and repeat PAUSE
 

package/framework/skills/level-1-workflows/morph-phase-design/references/architecture-analysis-guide.md

@@ -11,7 +11,7 @@
 
 **Ref:** `framework/standards/architecture/ddd/complexity-levels.md`
 
-**Obtenha o taskPrompt do dispatch config** (`npx morph-spec dispatch-agents $ARGUMENTS design`) e use o Task tool:
+**Obtenha o taskPrompt do dispatch config** (`morph-spec dispatch-agents $ARGUMENTS design`) e use o Task tool:
 
 ```
 [Task tool — domain-architect]

package/framework/skills/level-1-workflows/morph-phase-implement/.morph/logs/activity.json

@@ -0,0 +1,38 @@
+{
+  "sessionId": "",
+  "feature": "",
+  "phase": "",
+  "hooks": [
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:06:20"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:07"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:15"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:15"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:40"
+    }
+  ],
+  "skills": []
+}

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

@@ -5,7 +5,7 @@ argument-hint: "[feature-name]"
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.10.9"
+cliVersion: "4.11.0"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
 ---
 
@@ -27,7 +27,7 @@ Implement the tasks defined in Phase 4, with checkpoints every 3 tasks and a fin
 **Before any reads or writes — verify the current phase:**
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field:
@@ -35,9 +35,9 @@ Check the `"phase"` field:
 **If `"phase": "implement"`** → correct phase, proceed.
 
 **If `"phase": "tasks"`** → run in sequence:
-1. `npx morph-spec state mark-output $ARGUMENTS tasks`
-2. `npx morph-spec approve $ARGUMENTS tasks`
-3. `npx morph-spec phase advance $ARGUMENTS` (→ implement)
+1. `morph-spec state mark-output $ARGUMENTS tasks`
+2. `morph-spec approve $ARGUMENTS tasks`
+3. `morph-spec phase advance $ARGUMENTS` (→ implement)
 
 **Any other value** → STOP — inconsistent state, report to user.
 
@@ -51,13 +51,13 @@ Before any task work, validate that prior phases are truly complete. `state.json
 
 ```bash
 # 1. Verify mandatory outputs from all prior phases
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 
 # 2. Confirm all approval gates passed
-npx morph-spec approval-status $ARGUMENTS
+morph-spec approval-status $ARGUMENTS
 
 # 3. Verify activeAgents are populated
-npx morph-spec state get $ARGUMENTS | grep -A5 activeAgents
+morph-spec state get $ARGUMENTS | grep -A5 activeAgents
 ```
 
 If any check fails → **STOP**. Do not start any task. Report what's missing:
@@ -65,8 +65,8 @@ If any check fails → **STOP**. Do not start any task. Report what's missing:
 | Problem | Resolution |
 |---------|-----------|
 | Missing output (spec.md, contracts, etc.) | Return to corresponding phase and generate it |
-| Gate not approved (design, plan, tasks) | `npx morph-spec approve $ARGUMENTS <gate>` |
-| Invalid phase | `npx morph-spec phase advance $ARGUMENTS` |
+| Gate not approved (design, plan, tasks) | `morph-spec approve $ARGUMENTS <gate>` |
+| Invalid phase | `morph-spec phase advance $ARGUMENTS` |
 | Empty activeAgents | Run `/phase-setup $ARGUMENTS` first |
 
 **This step is not optional.** Only proceed when all commands return without errors.
@@ -111,7 +111,7 @@ Use `AskUserQuestion` with header `"{MCP}"` and options:
 
 | Action | Tool | Alternative |
 |--------|------|-------------|
-| Check execution mode (single/subagents/agent-teams) | **Bash** `npx morph-spec dispatch-agents $ARGUMENTS implement` | Task groups + subagent prompts |
+| Check execution mode (single/subagents/agent-teams) | **Bash** `morph-spec dispatch-agents $ARGUMENTS implement` | Task groups + subagent prompts |
 | **Dispatch implementers by domain** (subagents) | **Agent** `subagent_type=<taskGroups[group].subagentType>` + `prompt=taskPrompt` from dispatch config | Backend + frontend + infra in parallel |
 | **Create Agent Team** (critical multi-domain features) | Natural language — see Step 0.5b | — |
 | Read task details | **Read** tasks.md, spec.md, contracts.cs/.ts | — |
@@ -121,14 +121,14 @@ Use `AskUserQuestion` with header `"{MCP}"` and options:
 | Run migrations | **Supabase MCP** `query()` | **Bash** `npx supabase migration ...` |
 | Build project | **Bash** `dotnet build` or `npm run build` | — |
 | Run tests | **Bash** `dotnet test` or `npm test` | — |
-| Checkpoint validation | **Bash** `npx morph-spec validate-feature ...` | — |
-| Mark task complete | **Bash** `npx morph-spec task done $ARGUMENTS T001` | — |
+| Checkpoint validation | **Bash** `morph-spec validate-feature ...` | — |
+| Mark task complete | **Bash** `morph-spec task done $ARGUMENTS T001` | — |
 | Smoke test in browser | **Playwright MCP** `browser_navigate()` + `browser_snapshot()` | Manual |
 | Check console errors | **Playwright MCP** `browser_console_messages()` | — |
 | Screenshot for recap | **Playwright MCP** `browser_take_screenshot()` | — |
 | Deploy and logs Vercel | **Vercel MCP** `list_projects()`, `get_deployments()`, `manage_env_vars()` | **Bash** `vercel deploy` |
 | Create PR | **Bash** `gh pr create ...` | **GitHub MCP** `create_pull_request()` |
-| Update state | **Bash** `npx morph-spec state set ...` | — |
+| Update state | **Bash** `morph-spec state set ...` | — |
 
 **Phase MCPs:** Supabase (migrations, RLS), Context7 (API lookup), Playwright (smoke test), GitHub (PRs), Vercel (deploy, logs, env vars).
 
@@ -227,7 +227,7 @@ The strategy was defined and approved in the Plan phase. Use it directly:
 If `plan.md` doesn't exist or the field is missing, auto-detect via dispatch-agents:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement
+morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
 Check the `mode` field in the JSON output to determine the execution strategy.
@@ -239,7 +239,7 @@ Check the `mode` field in the JSON output to determine the execution strategy.
 **Step 0.5a: Get dispatch config:**
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement
+morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
 Parse the JSON output. Extract `taskGroups` and each group's `subagentType`.
@@ -252,7 +252,7 @@ For each group, verify `.claude/agents/{subagentType}.md` exists:
 ls .claude/agents/{subagentType}.md
 ```
 
-If missing → **STOP** with: `"Agent file .claude/agents/{subagentType}.md not found. Run: npx morph-spec setup-infra"`. Do NOT fall back to general-purpose agents for missing files.
+If missing → **STOP** with: `"Agent file .claude/agents/{subagentType}.md not found. Run: morph-spec setup-infra"`. Do NOT fall back to general-purpose agents for missing files.
 
 **Step 0.5c: Dispatch subagents:**
 
@@ -271,7 +271,7 @@ Each subagent receives a prompt with:
 - **MANDATORY verification before every `task done`** (see Step 2, item 6b)
 
 2. Dispatch subagents for groups in **parallel** (when no cross-group dependencies)
-3. After all complete, validate integration: `npx morph-spec validate-feature $ARGUMENTS --phase implement`
+3. After all complete, validate integration: `morph-spec validate-feature $ARGUMENTS --phase implement`
 
 **Fallback:** If `dispatch-agents` fails (non-zero exit or invalid JSON), log a warning and fall back to sequential single-agent mode (Step 2).
 
@@ -294,14 +294,14 @@ Create the team with natural language specifying:
 - Enable **plan approval**: teammates must get plans approved before implementing
 - Gate: only approve plans matching contracts.cs/.ts and spec.md
 
-After all teammates complete: `npx morph-spec validate-feature $ARGUMENTS --phase implement`
+After all teammates complete: `morph-spec validate-feature $ARGUMENTS --phase implement`
 
 ---
 
 ### Step 2: Task Loop
 
 ```bash
-npx morph-spec task next $ARGUMENTS
+morph-spec task next $ARGUMENTS
 ```
 
 For each task (T001 → T00N):
@@ -312,7 +312,7 @@ For each task (T001 → T00N):
    ```
 2. **Start via CLI:**
    ```bash
-   npx morph-spec task start $ARGUMENTS T001
+   morph-spec task start $ARGUMENTS T001
    ```
 3. **Read the task description** + contracts.cs/.ts for relevant DTOs/interfaces
 4. **Implement** using Write (new) or Edit (existing)
@@ -320,12 +320,12 @@ For each task (T001 → T00N):
 6. **MANDATORY — Verification before `task done`:**
    Run `validate-feature` before marking ANY task as done. This is non-negotiable — it catches broken code, missing files, and spec violations before they compound across tasks.
    ```bash
-   npx morph-spec validate-feature $ARGUMENTS --phase implement
+   morph-spec validate-feature $ARGUMENTS --phase implement
    ```
    Only proceed to step 7 if verification passes. If it fails → fix before marking `task done`.
 7. **Mark as done via CLI:**
    ```bash
-   npx morph-spec task done $ARGUMENTS T001
+   morph-spec task done $ARGUMENTS T001
    ```
 8. **If `task done` returns without error, update group task progress:**
    - Increment completed count for the task's group
@@ -339,10 +339,10 @@ For each task (T001 → T00N):
 
 ```bash
 # Save checkpoint
-npx morph-spec checkpoint-save $ARGUMENTS
+morph-spec checkpoint-save $ARGUMENTS
 
 # Run validation
-npx morph-spec validate-feature $ARGUMENTS --phase implement
+morph-spec validate-feature $ARGUMENTS --phase implement
 ```
 
 **If validation fails:**
@@ -392,7 +392,7 @@ await mcp__playwright__browser_take_screenshot({ type: 'png' });
 After ALL tasks completed:
 
 ```bash
-npx morph-spec generate recap $ARGUMENTS
+morph-spec generate recap $ARGUMENTS
 ```
 
 > For the full recap format, see `references/recap-example.md`
@@ -400,8 +400,8 @@ npx morph-spec generate recap $ARGUMENTS
 ### Step 7: Update State
 
 ```bash
-npx morph-spec state set $ARGUMENTS status done
-npx morph-spec state mark-output $ARGUMENTS recap
+morph-spec state set $ARGUMENTS status done
+morph-spec state mark-output $ARGUMENTS recap
 ```
 
 ### Step 8: Post-Implementation Review (mandatory before PR)
@@ -440,7 +440,7 @@ morph-spec uses its own agents and validators for implementation, dispatch, and
 
 Implementers are dispatched via `dispatch-agents`:
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement
+morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
 Use the `subagentType` from each group in the Agent tool: