@polymorphism-tech/morph-spec 4.10.9 → 4.11.0

package/framework/agents/infrastructure/infra-architect.md

@@ -1,48 +1,48 @@
----
-name: infra-architect
-description: Infrastructure Squad Leader for cloud-agnostic infrastructure coordination. Use when planning deployments, provisioning any cloud resources, setting up CI/CD pipelines, containerizing applications, or designing infrastructure architecture regardless of cloud provider.
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-stacks:
-  - azure
-  - docker
----
-
-# Infrastructure Squad Leader
-
-Cloud-agnostic infrastructure coordinator. Delegates to cloud-specific specialists.
-
-## Responsabilidades
-
-1. **Coordenar especialistas de infra** independente do cloud provider
-2. **Decidir stack de infra** com base no config do projeto
-3. **Garantir IaC** — tudo via código, nada manual
-4. **CI/CD** — pipelines para todos os ambientes
-
-## Quando ativar sub-especialistas
-
-| Cenário | Especialista |
-|---------|-------------|
-| Deploy em Azure | azure-architect |
-| Templates Bicep | bicep-architect (via azure-architect) |
-| Pipelines CI/CD | devops-engineer |
-| Docker / containers | container-specialist |
-| Logs / métricas | observability-expert |
-| Auth Microsoft/Entra | azure-identity (via azure-architect) |
-
-## Princípio: Infrastructure as Code
-
-> Nunca criar recursos de infra manualmente. Toda infra via código (Bicep, Terraform, Pulumi, Compose).
-
-## Checklist de Infra
-
-- [ ] Cloud provider definido em config.json
-- [ ] IaC templates criados e validados
-- [ ] Ambientes dev/staging/prod separados
-- [ ] Secrets nunca hardcoded
-- [ ] CI/CD pipeline configurado
-- [ ] Observability básica (logs + métricas)
-- [ ] Estimativa de custos documentada
-
----
-
-*MORPH-SPEC by Polymorphism Tech*
+---
+name: infra-architect
+description: Infrastructure Squad Leader for cloud-agnostic infrastructure coordination. Use when planning deployments, provisioning any cloud resources, setting up CI/CD pipelines, containerizing applications, or designing infrastructure architecture regardless of cloud provider.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
+  - docker
+---
+
+# Infrastructure Squad Leader
+
+Cloud-agnostic infrastructure coordinator. Delegates to cloud-specific specialists.
+
+## Responsabilidades
+
+1. **Coordenar especialistas de infra** independente do cloud provider
+2. **Decidir stack de infra** com base no config do projeto
+3. **Garantir IaC** — tudo via código, nada manual
+4. **CI/CD** — pipelines para todos os ambientes
+
+## Quando ativar sub-especialistas
+
+| Cenário | Especialista |
+|---------|-------------|
+| Deploy em Azure | azure-architect |
+| Templates Bicep | bicep-architect (via azure-architect) |
+| Pipelines CI/CD | devops-engineer |
+| Docker / containers | container-specialist |
+| Logs / métricas | observability-expert |
+| Auth Microsoft/Entra | azure-identity (via azure-architect) |
+
+## Princípio: Infrastructure as Code
+
+> Nunca criar recursos de infra manualmente. Toda infra via código (Bicep, Terraform, Pulumi, Compose).
+
+## Checklist de Infra
+
+- [ ] Cloud provider definido em config.json
+- [ ] IaC templates criados e validados
+- [ ] Ambientes dev/staging/prod separados
+- [ ] Secrets nunca hardcoded
+- [ ] CI/CD pipeline configurado
+- [ ] Observability básica (logs + métricas)
+- [ ] Estimativa de custos documentada
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*

package/framework/commands/morph-apply.md

@@ -23,10 +23,10 @@ Implement the feature by executing its task breakdown, tracking progress through
 |--------|------|-------------|
 | Read spec, tasks, contracts | **Read** all outputs | — |
 | Detect architecture style | **Bash** `cat .morph/config/config.json \| grep architecture` | — |
-| Agent dispatch config | **Bash** `npx morph-spec dispatch-agents $ARGUMENTS implement` | — |
+| Agent dispatch config | **Bash** `morph-spec dispatch-agents $ARGUMENTS implement` | — |
 | Parallel task execution | **Agent** subagent per task group | Sequential fallback |
 | Look up implementation patterns | **Context7 MCP** `query_docs()` | **WebSearch** |
-| Track progress | **Bash** `npx morph-spec state get $ARGUMENTS` | — |
+| Track progress | **Bash** `morph-spec state get $ARGUMENTS` | — |
 
 ---
 
@@ -37,9 +37,9 @@ Before writing any code, verify all prior phases are complete. This gate prevent
 ### 1. Check state and approvals
 
 ```bash
-npx morph-spec state get $ARGUMENTS
-npx morph-spec approval-status $ARGUMENTS
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec state get $ARGUMENTS
+morph-spec approval-status $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 ```
 
 **All three must pass.** If any fails:
@@ -87,13 +87,13 @@ cat .morph/config/config.json | grep -A3 '"architecture"'
 ### 4. Get agent dispatch config
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement --table
+morph-spec dispatch-agents $ARGUMENTS implement --table
 ```
 
 This shows which agents are active for implementation and how tasks can be grouped. If agent teams are enabled and tasks have no dependencies between groups, consider dispatching parallel agents:
 
 ```bash
-npx morph-spec dispatch-agents $ARGUMENTS implement
+morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
 The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for multi-agent coordination.
@@ -105,7 +105,7 @@ The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for mult
 ### Step 1: Advance to implement phase
 
 ```bash
-npx morph-spec phase advance $ARGUMENTS
+morph-spec phase advance $ARGUMENTS
 ```
 
 This validates phase eligibility and emits a SKILL DISPATCH block listing required skills for implementation (verification-before-completion, morph-checklist, etc.).
@@ -113,7 +113,7 @@ This validates phase eligibility and emits a SKILL DISPATCH block listing requir
 ### Step 2: Initialize state tracking
 
 ```bash
-npx morph-spec state set $ARGUMENTS tasks.total {N}
+morph-spec state set $ARGUMENTS tasks.total {N}
 ```
 
 Where `{N}` is the number of tasks in tasks.md (e.g., 6 for T001-T006).
@@ -124,7 +124,7 @@ For each task in the breakdown, follow this cycle:
 
 ```bash
 # 1. Start the task (activates task-tracking guard)
-npx morph-spec task start $ARGUMENTS {task-id}
+morph-spec task start $ARGUMENTS {task-id}
 
 # 2. Implement the task
 #    - Follow spec.md and contracts
@@ -136,7 +136,7 @@ npx morph-spec task start $ARGUMENTS {task-id}
 #    matches the spec and contracts before marking done
 
 # 4. Complete the task (triggers Tier-4 validators automatically)
-npx morph-spec task done $ARGUMENTS {task-id}
+morph-spec task done $ARGUMENTS {task-id}
 ```
 
 **If validation fails on `task done`:**
@@ -153,8 +153,8 @@ If `dispatch-agents` identified parallelizable task groups and agent teams are e
 After every 3 completed tasks, save a checkpoint:
 
 ```bash
-npx morph-spec checkpoint-save $ARGUMENTS "after-T003"
-npx morph-spec state get $ARGUMENTS
+morph-spec checkpoint-save $ARGUMENTS "after-T003"
+morph-spec state get $ARGUMENTS
 ```
 
 Checkpoints validate architecture compliance, check package versions, scan for security issues, and save a restorable snapshot. The cadence is every 3 tasks — for 6 tasks: checkpoint after T003 and T006. For 10 tasks: after T003, T006, T009, and at completion.
@@ -162,7 +162,7 @@ Checkpoints validate architecture compliance, check package versions, scan for s
 After each checkpoint, check progress:
 
 ```bash
-npx morph-spec state list
+morph-spec state list
 ```
 
 ### Step 5: Finalize implementation
@@ -171,16 +171,16 @@ After all tasks are complete:
 
 ```bash
 # Final validation
-npx morph-spec validate-feature $ARGUMENTS
+morph-spec validate-feature $ARGUMENTS
 
 # Generate recap (auto-marks 'recap' output in state)
-npx morph-spec generate recap $ARGUMENTS
+morph-spec generate recap $ARGUMENTS
 
 # Verify final state
-npx morph-spec state get $ARGUMENTS
+morph-spec state get $ARGUMENTS
 
 # Advance to next phase
-npx morph-spec phase advance $ARGUMENTS
+morph-spec phase advance $ARGUMENTS
 ```
 
 ### Step 6: Post-implementation review

package/framework/commands/morph-preflight.md

@@ -26,9 +26,9 @@ These checks verify that the morph-spec workflow is complete for the feature bei
 
 ```bash
 # Verify implementation is complete
-npx morph-spec state get {feature}
-npx morph-spec approval-status {feature}
-npx morph-spec validate-feature {feature}
+morph-spec state get {feature}
+morph-spec approval-status {feature}
+morph-spec validate-feature {feature}
 ```
 
 | Check | Command | Pass Criteria |

package/framework/commands/morph-proposal.md

@@ -15,7 +15,7 @@ Guide a feature through the full planning pipeline (proposal through tasks) with
 Check if the feature already has state:
 
 ```bash
-npx morph-spec state get {feature-name}
+morph-spec state get {feature-name}
 ```
 
 - **Exists:** Read the current phase and resume from where it stopped (skip completed phases)
@@ -40,7 +40,7 @@ Read `framework/agents.json` (or `.morph/framework/agents.json` in client projec
 
 Register each selected agent:
 ```bash
-npx morph-spec state add-agent {feature-name} {agent-id}
+morph-spec state add-agent {feature-name} {agent-id}
 ```
 
 ### Step 3: Determine if UI/UX phase is needed
@@ -70,9 +70,9 @@ Fill every section of the template. In particular:
 ### Step 5: Register state
 
 ```bash
-npx morph-spec state init {feature-name}
-npx morph-spec state set {feature-name} status draft
-npx morph-spec state mark-output {feature-name} proposal
+morph-spec state init {feature-name}
+morph-spec state set {feature-name} status draft
+morph-spec state mark-output {feature-name} proposal
 ```
 
 ### MANDATORY PAUSE
@@ -88,8 +88,8 @@ Options: Approve proposal / Request changes / Reject
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} proposal
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} proposal
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -112,8 +112,8 @@ Check if `ui-designer` is in `activeAgents`:
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} uiux
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} uiux
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -130,8 +130,8 @@ Present: spec, contracts, decisions, effort estimate. Use `AskUserQuestion` with
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} design
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} design
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -158,8 +158,8 @@ Present: implementation plan with recommended strategy. Use `AskUserQuestion` wi
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} plan
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} plan
+morph-spec phase advance {feature-name}
 ```
 
 ---
@@ -176,8 +176,8 @@ Present: task breakdown, execution order, total estimate. Use `AskUserQuestion`
 
 After approval:
 ```bash
-npx morph-spec approve {feature-name} tasks
-npx morph-spec phase advance {feature-name}
+morph-spec approve {feature-name} tasks
+morph-spec phase advance {feature-name}
 ```
 
 ---

package/framework/commands/morph-status.md

@@ -13,7 +13,7 @@ Show the current MORPH project status and features in development.
 **ALWAYS** use the state-manager CLI to get status:
 
 ```bash
-npx morph-spec state list
+morph-spec state list
 ```
 
 This command automatically shows:
@@ -35,7 +35,7 @@ This command automatically shows:
 To get detailed JSON for a feature:
 
 ```bash
-npx morph-spec state get {feature-name}
+morph-spec state get {feature-name}
 ```
 
 ### 3. Archived Features
@@ -51,7 +51,7 @@ Check `.morph/specs/` for consolidated specs.
 
 ## Output
 
-The `npx morph-spec state list` command automatically generates a formatted dashboard:
+The `morph-spec state list` command automatically generates a formatted dashboard:
 
 ```
 ╔════════════════════════════════════════════════════════════════╗

package/framework/commands/morph-troubleshoot.md

@@ -72,7 +72,7 @@ site:learn.microsoft.com/azure {error}
 **WebSearch usage example:**
 
 If the user asks about a SignalR error:
-1. First: `npx morph-spec troubleshoot SignalR connection`
+1. First: `morph-spec troubleshoot SignalR connection`
 2. If not found: WebSearch with `site:github.com/dotnet/aspnetcore SignalR connection closed`
 3. Return formatted relevant links