@polymorphism-tech/morph-spec 4.10.10 → 4.11.1

package/framework/rules/morph-task-tracking.md

@@ -0,0 +1,49 @@
+---
+stacks:
+  - "*"
+---
+
+# MORPH-SPEC Task Tracking
+
+> Session tasks are MANDATORY in every MORPH-SPEC phase. They track real progress and must be
+> created BEFORE any phase work begins.
+
+## Rules
+
+1. **Every phase skill MUST create session tasks** using `TaskCreate` before reading files or generating outputs
+2. **Tasks are dynamic** — analyze the phase workflow and create tasks that reflect YOUR actual planned actions for this session
+3. **Every task MUST be updated**: `in_progress` before starting, `completed` after finishing
+4. **Pipeline orchestrators** (`/morph-proposal`, `/morph-apply`) MUST create master tasks for each phase
+5. **Never skip task creation** — even if resuming mid-phase, create tasks for remaining steps
+6. **Granularity**: minimum 2, typically 3-7 tasks per phase — adjust to complexity
+7. **For iterative work** (clarification rounds, quality loops): update task `subject` with round/score progress
+
+## Task Update Pattern
+
+```
+TaskUpdate(taskId, status="in_progress")   // before starting the step
+// ... do the work ...
+TaskUpdate(taskId, status="completed")     // after step finishes
+```
+
+For iterative tasks:
+```
+TaskUpdate(taskId, subject="Round 3 — score 82/100")
+```
+
+## Deviation Tracking
+
+When completing a task differently than originally planned, record the reason:
+
+```
+morph-spec task done <feature> <taskId> --note "Reason for deviation"
+```
+
+For after-the-fact annotation (supports multiple types):
+```
+morph-spec task annotate <feature> <taskId> "Reason" --type deviation
+morph-spec task annotate <feature> <taskId> "Context info" --type context
+morph-spec task annotate <feature> <taskId> "Resolved" --type blocker-resolved
+```
+
+Note types: `deviation` (default), `context`, `blocker-resolved`

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

@@ -22,38 +22,34 @@ allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
 
 | Action | Tool | Alternative |
 |--------|------|-------------|
-| Load feature state | **Bash** `npx morph-spec state get $ARGUMENTS` | — |
+| Load feature state | **Bash** `morph-spec state get $ARGUMENTS` | — |
 | Read project config | **Read** `.morph/config/config.json` | — |
 | Scan existing code | **Glob** / **Grep** | — |
 | Research libraries | **Context7 MCP** `query_docs()` | **WebSearch** |
 | Ask clarifying questions | **AskUserQuestion** (never plain text) | — |
-| Render proposal template | **Bash** `npx morph-spec template render docs/proposal ...` | — |
+| Render proposal template | **Bash** `morph-spec template render docs/proposal ...` | — |
 
 ---
 
 ## Workflow
 
-### Step 0: Create session tasks
+## MANDATORY: Session Tasks
 
-```
-TaskCreate: "Explore project context"   → activeForm: "Exploring context"
-TaskCreate: "Ask clarifying questions"  → activeForm: "Asking questions"
-TaskCreate: "Propose 2-3 approaches"    → activeForm: "Analyzing approaches"
-TaskCreate: "Present design"            → activeForm: "Presenting design"
-TaskCreate: "Document recommendation"   → activeForm: "Documenting"
-```
-
-Update each to `in_progress` before its step and `completed` after.
+> **BEFORE starting any brainstorming work**, analyze what you need to do and create session tasks.
+>
+> **Rules:** Minimum 2 tasks, typically 3-5. Mark `in_progress` before starting, `completed` after.
+>
+> **Typical tasks:** context exploration, clarifying questions, approach analysis, recommendation, documentation
 
 ### Step 1: Explore Context
 
 Gather information before generating ideas. This step is what makes morph-aware brainstorming different from generic brainstorming — it grounds your thinking in the actual project state and constraints.
 
-1. **Read state** — `npx morph-spec state get $ARGUMENTS` → current phase, active agents, existing outputs, task history
+1. **Read state** — `morph-spec state get $ARGUMENTS` → current phase, active agents, existing outputs, task history
 2. **Read config** — `.morph/config/config.json` → stack, architecture style (VSA vs standard), project name, integrations
 3. **Check architecture** — `cat .morph/config/config.json | grep -A3 architecture` → determines which agents and patterns apply
 4. **Read existing outputs** — proposal.md, spec.md, decisions.md (if they exist from prior work)
-5. **Check active agents** — `npx morph-spec dispatch-agents $ARGUMENTS design --table` → which specialists are available
+5. **Check active agents** — `morph-spec dispatch-agents $ARGUMENTS design --table` → which specialists are available
 6. **Scan codebase** — use Glob/Grep to understand existing patterns, domain models, and service boundaries relevant to the feature
 7. **Check MCP tools** — if Context7, GitHub, or other MCPs are available, use them for research
 
@@ -106,7 +102,7 @@ For each approach, document:
 
    **Phase 0 (Proposal):**
    ```bash
-   npx morph-spec template render docs/proposal ".morph/features/$ARGUMENTS/0-proposal/proposal.md" '{"FEATURE_NAME":"...", "DATE":"..."}'
+   morph-spec template render docs/proposal ".morph/features/$ARGUMENTS/0-proposal/proposal.md" '{"FEATURE_NAME":"...", "DATE":"..."}'
    ```
    Then edit the rendered file to add the brainstorming results.
 
@@ -115,12 +111,12 @@ For each approach, document:
 
 3. **Update state** (mandatory — do not skip):
    ```bash
-   npx morph-spec state mark-output $ARGUMENTS proposal    # Phase 0
-   npx morph-spec state mark-output $ARGUMENTS decisions    # Phase 2
+   morph-spec state mark-output $ARGUMENTS proposal    # Phase 0
+   morph-spec state mark-output $ARGUMENTS decisions    # Phase 2
    ```
    Then verify the output was recorded:
    ```bash
-   npx morph-spec state get $ARGUMENTS
+   morph-spec state get $ARGUMENTS
    ```
 
 ---

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

@@ -14,9 +14,9 @@ Types: `deploy`, `security`, `seo`, `performance`, `accessibility`, `legal-brazi
 ## Deploy
 
 ### MORPH-SPEC Validation (run first)
-- [ ] `npx morph-spec validate-feature {feature}` — passes with 100% pass rate
-- [ ] `npx morph-spec approval-status {feature}` — all gates approved (design, plan, tasks)
-- [ ] `npx morph-spec state get {feature}` — phase is `implement`, all tasks `done`
+- [ ] `morph-spec validate-feature {feature}` — passes with 100% pass rate
+- [ ] `morph-spec approval-status {feature}` — all gates approved (design, plan, tasks)
+- [ ] `morph-spec state get {feature}` — phase is `implement`, all tasks `done`
 - [ ] Recap generated: `.morph/features/{feature}/5-implement/recap.md` exists
 
 ### Pre-Deploy

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

@@ -57,7 +57,7 @@ Store `stack`, `frontendPath`, `startCommand` and the detected context — all s
 ## Step 1 — Design Outputs Validation (if context includes design validation)
 
 ```bash
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 ```
 
 Verify existence and quality of the 4 mandatory outputs in `.morph/features/$ARGUMENTS/2-ui/`:

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

@@ -25,10 +25,10 @@ Before running any `morph-spec` command, detect how to invoke the CLI:
 
 ```bash
 # Try local first (project dependency), then global
-npx morph-spec --version
+morph-spec --version
 ```
 
-- If `npx morph-spec --version` succeeds → use `npx morph-spec` as the CLI prefix for all commands.
+- If `morph-spec --version` succeeds → use `morph-spec` as the CLI prefix for all commands.
 - If it fails → try `morph-spec --version` (global install). If that works → use `morph-spec`.
 - If both fail → **STOP** and show:
   ```
@@ -36,7 +36,7 @@ npx morph-spec --version
     npm install @polymorphism-tech/morph-spec
   ```
 
-Use the resolved CLI prefix (e.g. `npx morph-spec`) for ALL bash commands in the following steps.
+Use the resolved CLI prefix (e.g. `morph-spec`) for ALL bash commands in the following steps.
 
 ---
 
@@ -78,19 +78,19 @@ Check if `.morph/` exists in the current directory.
 
 **If MISSING:**
 ```bash
-npx morph-spec setup-infra
+morph-spec setup-infra
 ```
 Output confirms: `✓ MORPH-SPEC infrastructure installed.`
 
 **If EXISTS and argument is `refresh`:**
 Re-run setup-infra to update framework files, then continue with context/config refresh:
 ```bash
-npx morph-spec setup-infra
+morph-spec setup-infra
 ```
 
 **If EXISTS and no argument:**
 Ask: *"MORPH already initialized. Refresh context and config? (y/n)"*
-If `y` → re-run `npx morph-spec setup-infra` then continue.
+If `y` → re-run `morph-spec setup-infra` then continue.
 If `n` → STOP.
 
 ---
@@ -359,7 +359,7 @@ And inform the user:
 To create a new VSA project:
    dotnet new install https://github.com/polymorphism-tech/Morph_Template_VerticalSliceArchitecture
    dotnet new vsa -n MyProject
-   cd MyProject && npx morph-spec init
+   cd MyProject && morph-spec init
 ```
 
 ---
@@ -374,7 +374,7 @@ For each detected integration with an available MCP:
   ```json
   "supabase": { "type": "http", "url": "https://mcp.supabase.com/mcp" }
   ```
-- NO → show snippet + `npx morph-spec mcp setup supabase`
+- NO → show snippet + `morph-spec mcp setup supabase`
 
 **GitHub:**
 > *"Configure GitHub MCP? Requires Docker + a `GITHUB_PERSONAL_ACCESS_TOKEN`."*
@@ -386,7 +386,7 @@ For each detected integration with an available MCP:
     "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "<token>" }
   }
   ```
-- NO → show snippet + `npx morph-spec mcp setup github`
+- NO → show snippet + `morph-spec mcp setup github`
 
 **Vercel detected** (vercel.json exists OR stack is nextjs):
 > *"Configure Vercel MCP? Uses OAuth — no credentials needed."*
@@ -394,7 +394,7 @@ For each detected integration with an available MCP:
   ```json
   "vercel": { "type": "http", "url": "https://mcp.vercel.com" }
   ```
-- NO → show snippet + `npx morph-spec mcp setup vercel`
+- NO → show snippet + `morph-spec mcp setup vercel`
 
 Only offer Docker, Azure if explicitly detected in `.env.example`.
 
@@ -462,7 +462,7 @@ Use `AskUserQuestion` with header `"{MCP} failed"` and these options:
 After all configuration is complete, run the health check to verify everything is properly installed:
 
 ```bash
-npx morph-spec doctor
+morph-spec doctor
 ```
 
 This validates: config.json integrity, agents.json presence, hooks installation, skills distribution, required command files, and state.json schema version. Fix any reported issues before proceeding.

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

@@ -95,7 +95,7 @@ Do not proceed while tests are failing. Fix failures and re-run before continuin
 ## Step 4 — Framework Validation
 
 ```bash
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 ```
 
 **🚫 BLOCK if it fails.**
@@ -251,10 +251,10 @@ Wait for both. **🚫 BLOCK if either returns unresolved CRITICAL.**
 
 ```bash
 # Save post-review checkpoint
-npx morph-spec checkpoint-save $ARGUMENTS --note "post-implementation review"
+morph-spec checkpoint-save $ARGUMENTS --note "post-implementation review"
 
 # Generate final recap
-npx morph-spec generate recap $ARGUMENTS
+morph-spec generate recap $ARGUMENTS
 ```
 
 ---

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

@@ -152,7 +152,7 @@ All outputs go in `.morph/features/{feature-name}/5-implement/`:
 
 After completion, mark the output:
 ```bash
-npx morph-spec state mark-output {feature-name} recap
+morph-spec state mark-output {feature-name} recap
 ```
 
 **Does NOT generate:** proposal.md, spec.md, contracts.cs, tasks.md

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

@@ -60,13 +60,13 @@ When implementing simulation as a morph-spec task:
 
 ```bash
 # Track the simulation setup task
-npx morph-spec task start {feature} {task-id}
+morph-spec task start {feature} {task-id}
 
 # After implementation, validate the feature
-npx morph-spec validate-feature {feature}
+morph-spec validate-feature {feature}
 
 # Complete the task (triggers Tier-4 validators)
-npx morph-spec task done {feature} {task-id}
+morph-spec task done {feature} {task-id}
 ```
 
 Reference the project's service lifetime patterns:
@@ -80,7 +80,7 @@ grep -r "AddSingleton\|AddScoped\|AddTransient" src/ --include="*.cs" -l
 - [ ] Validate DI: `dotnet build && dotnet run` + health check
 - [ ] Test full flow end-to-end (not just unit tests)
 - [ ] Verify simulation logs — confirm mocks are being called
-- [ ] Run `npx morph-spec validate-feature {feature}` to check architecture compliance
+- [ ] Run `morph-spec validate-feature {feature}` to check architecture compliance
 
 ## Common Errors
 

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.10"
+cliVersion: "4.11.1"
 ---
 
 # 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.
 
@@ -94,6 +94,15 @@ Read: .morph/features/$ARGUMENTS/1-design/spec.md
 
 Calculate the initial score. Track accumulated answers from prior rounds to avoid repeating already-answered questions.
 
+## MANDATORY: Session Tasks
+
+> **BEFORE starting clarification work**, analyze the spec quality and create session tasks.
+>
+> **Rules:** Minimum 2 tasks, typically 2-4. Mark `in_progress` before starting, `completed` after.
+> For the clarification loop, update the task `subject` with round and score progress.
+>
+> **Typical tasks:** initial score calculation, clarification rounds (iterative), output generation
+
 ---
 
 ### Main Loop
@@ -217,7 +226,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 +250,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.10"
+cliVersion: "4.11.1"
 ---
 
 # 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
 ```
 
 ---