@polymorphism-tech/morph-spec 4.10.10 → 4.11.1

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.10"
+cliVersion: "4.11.1"
 ---
 
 # 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
@@ -53,26 +53,20 @@ Schema-first interactive design: read the real schema, validate with user, gener
 
 ## PRE-FLIGHT
 
-### Create session tasks for visibility
+## MANDATORY: Session Tasks
 
-```
-TaskCreate: "Pre-flight validation"       → activeForm: "Validating pre-flight"
-TaskCreate: "Schema analysis"             → activeForm: "Analyzing schema"
-TaskCreate: "Architecture blueprint"      → activeForm: "Designing architecture"
-TaskCreate: "Generate spec.md"            → activeForm: "Writing spec"
-TaskCreate: "Generate contracts"          → activeForm: "Writing contracts"
-TaskCreate: "Generate decisions.md"       → activeForm: "Documenting decisions"
-TaskCreate: "Design approval"             → activeForm: "Awaiting design approval"
-```
-
-Update each to `in_progress` before starting and `completed` after finishing.
+> **BEFORE starting any design work**, analyze the workflow below and create session tasks.
+>
+> **Rules:** Minimum 3 tasks, typically 5-7. Mark `in_progress` before starting, `completed` after.
+>
+> **Typical tasks:** pre-flight validation, schema analysis, architecture blueprint, spec generation, contracts generation, decisions documentation, design approval
 
 ---
 
 **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 +74,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 +191,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 +249,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 +308,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 +334,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 +358,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 +442,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 +471,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/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[feature-name]"
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.10.10"
+cliVersion: "4.11.1"
 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).
 
@@ -150,6 +150,12 @@ Use `AskUserQuestion` with header `"{MCP}"` and options:
 
 ## Context Loading
 
+## MANDATORY: Session Tasks
+
+> **You MUST create one native task per T001-T00N from tasks.md BEFORE starting implementation.**
+> After creating all tasks, wire dependencies using `addBlockedBy`.
+> Update each to `in_progress` before starting and `completed` after `task done` succeeds.
+
 ### 1. Read full context in PARALLEL
 
 ```
@@ -227,7 +233,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 +245,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 +258,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 +277,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 +300,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 +318,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 +326,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 +345,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 +398,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 +406,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 +446,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:

package/framework/skills/level-1-workflows/morph-phase-implement/prompts/implementer-prompt.md

@@ -20,7 +20,7 @@ You are implementing tasks for the feature '{{FEATURE_NAME}}' as agent '{{AGENT_
 ## Execution Rules
 
 1. Before starting each task:
-   - Execute: `npx morph-spec task start {{FEATURE_NAME}} {{TASK_ID}}`
+   - Execute: `morph-spec task start {{FEATURE_NAME}} {{TASK_ID}}`
 
 2. For each task, follow TDD:
    - Write the failing test first
@@ -32,11 +32,11 @@ You are implementing tasks for the feature '{{FEATURE_NAME}}' as agent '{{AGENT_
 3. Before marking any task done:
    - Verify build compiles: `dotnet build` or `npm run build`
    - Run relevant tests
-   - Execute: `npx morph-spec task done {{FEATURE_NAME}} {{TASK_ID}}`
+   - Execute: `morph-spec task done {{FEATURE_NAME}} {{TASK_ID}}`
 
 4. Every 3 tasks:
-   - Execute: `npx morph-spec checkpoint-save {{FEATURE_NAME}}`
-   - Execute: `npx morph-spec validate-feature {{FEATURE_NAME}} --phase implement`
+   - Execute: `morph-spec checkpoint-save {{FEATURE_NAME}}`
+   - Execute: `morph-spec validate-feature {{FEATURE_NAME}} --phase implement`
 
 5. Contracts are the source of truth — all DTOs, interfaces, and types MUST match `contracts.cs` exactly
 

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Plan). Generates a detailed implementation plan
 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 Plan — Phase 4
@@ -28,8 +28,8 @@ Generate a detailed implementation plan with exact paths, TDD code, and executio
 | Read spec + contracts + decisions | **Read** all outputs | — |
 | Analyze existing codebase | **Glob** + **Grep** patterns | — |
 | Look up library docs | **Context7 MCP** `query_docs()` | **WebSearch** |
-| Dispatch agents for analysis | **Bash** `npx morph-spec dispatch-agents $ARGUMENTS plan` | — |
-| Update state | **Bash** `npx morph-spec state mark-output $ARGUMENTS plan` | — |
+| Dispatch agents for analysis | **Bash** `morph-spec dispatch-agents $ARGUMENTS plan` | — |
+| Update state | **Bash** `morph-spec state mark-output $ARGUMENTS plan` | — |
 
 **Anti-patterns:**
 - Generating plan without reading contracts (contracts are the source of truth!)
@@ -45,15 +45,23 @@ Generate a detailed implementation plan with exact paths, TDD code, and executio
 ### 0. Ensure plan phase
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Check the `"phase"` field:
 - `"phase": "plan"` → correct phase, proceed
-- any other value → run `npx morph-spec phase advance $ARGUMENTS` and re-check
+- any other value → run `morph-spec phase advance $ARGUMENTS` and re-check
 
 > **Rule:** Never write to `3-plan/` until the phase is `plan`.
 
+## MANDATORY: Session Tasks
+
+> **BEFORE reading any files**, analyze the planning workflow and create session tasks.
+>
+> **Rules:** Minimum 2 tasks, typically 3-5. Mark `in_progress` before starting, `completed` after.
+>
+> **Typical tasks:** feature analysis, execution strategy, plan.md generation, plan approval
+
 ### 1. Read all prerequisites in PARALLEL
 
 ```
@@ -65,17 +73,6 @@ Read: .morph/features/{feature}/1-design/spec.md
     + Read: .morph/config/config.json
 ```
 
-### 1.5 Create session tasks for visibility
-
-```
-TaskCreate: "Analyze feature for execution strategy"  → activeForm: "Analyzing feature"
-TaskCreate: "Determine execution strategy"            → activeForm: "Planning strategy"
-TaskCreate: "Generate plan.md"                        → activeForm: "Writing plan"
-TaskCreate: "Plan approval"                           → activeForm: "Awaiting plan approval"
-```
-
-Update each to `in_progress` before starting and `completed` after finishing.
-
 ---
 
 ## Workflow
@@ -101,7 +98,7 @@ cat .morph/config/config.json | grep -A3 '"architecture"'
 Run the dispatch analysis:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS plan
+morph-spec dispatch-agents $ARGUMENTS plan
 ```
 
 **Factors for recommendation:**
@@ -185,7 +182,7 @@ git commit -m "{message}"
 ### Step 4: Update State
 
 ```bash
-npx morph-spec state mark-output $ARGUMENTS plan
+morph-spec state mark-output $ARGUMENTS plan
 ```
 
 ---
@@ -224,8 +221,8 @@ Use `AskUserQuestion` to capture approval before advancing. This gate prevents t
 
 - **"Approve plan"** →
   ```bash
-  npx morph-spec approve $ARGUMENTS plan
-  npx morph-spec phase advance $ARGUMENTS
+  morph-spec approve $ARGUMENTS plan
+  morph-spec phase advance $ARGUMENTS
   ```
 - **"I have feedback" or "Other"** → apply the feedback and repeat this PAUSE
 

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech sta
 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 Setup — Phase 1
@@ -26,19 +26,19 @@ Initialize the context and prepare the environment for an approved feature.
 
 | Action | Tool | Alternative |
 |--------|------|-------------|
-| Verify state | **Bash** `npx morph-spec state get` | — |
-| Detect agents + standards | **Bash** `npx morph-spec detect-agents $ARGUMENTS --json` → parse → **Bash** `npx morph-spec state add-agent` | **Read** agents.json manually |
+| Verify state | **Bash** `morph-spec state get` | — |
+| Detect agents + standards | **Bash** `morph-spec detect-agents $ARGUMENTS --json` → parse → **Bash** `morph-spec state add-agent` | **Read** agents.json manually |
 | Read project context | **Read** `.morph/context/README.md` | — |
 | Read config | **Read** `.morph/config/config.json` | — |
 | Detect VSA architecture | **Read** `.morph/config/config.json` → check `config.architecture.style` | — |
 | Scan project structure | **Glob** `src/**/*.{ts,tsx,cs}` | — |
 | Repository metadata | **GitHub MCP** `get_repo()` | **Bash** `gh repo view --json` |
-| Update state | **Bash** `npx morph-spec state set` | — |
+| Update state | **Bash** `morph-spec state set` | — |
 
 **MCPs for this phase:** GitHub (optional — repo metadata).
 
 **Anti-patterns:**
-- Do not read agents.json manually for keyword matching — use `npx morph-spec detect-agents` CLI
+- Do not read agents.json manually for keyword matching — use `morph-spec detect-agents` CLI
 - Do not use a Task agent for agent detection (CLI is faster and consistent)
 - Do not use WebSearch for local project info (use Read/Glob)
 
@@ -58,16 +58,13 @@ If any checkbox is NOT checked → go back to Phase 0 (Proposal).
 
 ---
 
-### Create session tasks for visibility
+## MANDATORY: Session Tasks
 
-```
-TaskCreate: "Detect agents and load standards"  → activeForm: "Detecting agents"
-TaskCreate: "Validate MCP connections"          → activeForm: "Validating MCPs"
-TaskCreate: "Confirm stack with user"           → activeForm: "Confirming stack"
-TaskCreate: "Configure feature state"           → activeForm: "Configuring state"
-```
-
-Update each task to `in_progress` before its step and `completed` after.
+> **BEFORE starting any setup work**, analyze the steps below and create session tasks.
+>
+> **Rules:** Minimum 2 tasks, typically 3-5. Mark `in_progress` before starting, `completed` after.
+>
+> **Typical tasks:** agent detection, MCP validation, stack confirmation, state configuration
 
 ---
 
@@ -76,7 +73,7 @@ Update each task to `in_progress` before its step and `completed` after.
 Read these files first — they inform all subsequent decisions:
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 If the feature doesn't exist in state, go back to Phase 0.
@@ -93,8 +90,8 @@ Read `.morph/config/config.json` and check `config.architecture.style`:
 
 | Value | Action |
 |-------|--------|
-| `"vertical-slice"` | `npx morph-spec state add-agent $ARGUMENTS vsa-architect` |
-| absent / any other value | `npx morph-spec state add-agent $ARGUMENTS domain-architect` |
+| `"vertical-slice"` | `morph-spec state add-agent $ARGUMENTS vsa-architect` |
+| absent / any other value | `morph-spec state add-agent $ARGUMENTS domain-architect` |
 
 Proceed with normal keyword detection for all other agents. The architect was already added above — skip it during keyword matching to avoid duplication.
 
@@ -103,7 +100,7 @@ Proceed with normal keyword detection for all other agents. The architect was al
 Use the `detect-agents` CLI to match agent keywords against the proposal (excludes architects already handled in Step 2.0):
 
 ```bash
-npx morph-spec detect-agents $ARGUMENTS --exclude domain-architect,vsa-architect --json
+morph-spec detect-agents $ARGUMENTS --exclude domain-architect,vsa-architect --json
 ```
 
 This reads the proposal from `.morph/features/$ARGUMENTS/0-proposal/proposal.md` and agents.json, returning JSON with `detected[]` and `skipped[]` arrays. Agents with `active_phases: ['*']` are always included.
@@ -111,7 +108,7 @@ This reads the proposal from `.morph/features/$ARGUMENTS/0-proposal/proposal.md`
 Parse the JSON output and add each detected agent to state:
 
 ```bash
-npx morph-spec state add-agent $ARGUMENTS {agent-id}
+morph-spec state add-agent $ARGUMENTS {agent-id}
 ```
 
 Run `add-agent` once per detected agent ID from the `detected[]` array.
@@ -156,7 +153,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 morph-spec mcp setup`
 
 **Summary:** Show a status table for each MCP before proceeding:
 ```
@@ -173,15 +170,15 @@ MCP Readiness:
 Run a quick check to verify all expected agents are installed for this project's stack:
 
 ```bash
-npx morph-spec doctor 2>&1 | grep -A 1 "agents completeness"
+morph-spec doctor 2>&1 | grep -A 1 "agents completeness"
 ```
 
 If the output shows **missing agents**, inform the user:
 
-> ⚠ Some agents for your stack are not installed. Run `npx morph-spec setup-infra` to install them.
+> ⚠ Some agents for your stack are not installed. Run `morph-spec setup-infra` to install them.
 
 Use `AskUserQuestion` with header `"Agents"` and options:
-- **Install now** — run `npx morph-spec setup-infra` to reinstall with current stack tags
+- **Install now** — run `morph-spec setup-infra` to reinstall with current stack tags
 - **Continue without** — proceed with available agents (may lack specialized support)
 
 If "Install now" is selected, run the command and continue.
@@ -200,7 +197,7 @@ Based on the proposal and context, confirm:
 Show the agents detected from the proposal:
 
 ```bash
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 ```
 
 Parse the JSON and list `activeAgents` with their emojis/icons and responsibilities (look up each agent in `.morph/framework/agents.json` for the `icon` field).
@@ -208,7 +205,7 @@ Parse the JSON and list `activeAgents` with their emojis/icons and responsibilit
 **If there are 2+ specialist agents active**, show the dispatch plan for the next phase:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS design
+morph-spec dispatch-agents $ARGUMENTS design
 ```
 
 This shows which agents will be dispatched in parallel during the design phase and which tasks they'll execute.
@@ -222,7 +219,7 @@ This shows which agents will be dispatched in parallel during the design phase a
 Update the feature state:
 
 ```bash
-npx morph-spec state set $ARGUMENTS status in_progress
+morph-spec state set $ARGUMENTS status in_progress
 ```
 
 **Determine the next phase** based on active agents: