@polymorphism-tech/morph-spec 4.10.7 → 4.10.9

package/bin/morph-spec.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 import { program } from 'commander';
 import chalk from 'chalk';

package/claude-plugin.json

@@ -1,14 +1,14 @@
-{
-  "name": "morph-spec",
-  "version": "4.10.7",
-  "displayName": "MORPH-SPEC Framework",
-  "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
-  "publisher": "polymorphism-tech",
-  "skills": {
-    "directory": "framework/skills",
-    "namespace": "morph-spec"
-  },
-  "hooks": {
-    "directory": "framework/hooks/claude-code"
-  }
-}
+{
+  "name": "morph-spec",
+  "version": "4.10.9",
+  "displayName": "MORPH-SPEC Framework",
+  "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
+  "publisher": "polymorphism-tech",
+  "skills": {
+    "directory": "framework/skills",
+    "namespace": "morph-spec"
+  },
+  "hooks": {
+    "directory": "framework/hooks/claude-code"
+  }
+}

package/docs/CHEATSHEET.md

@@ -198,4 +198,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.10.7 by Polymorphism Tech*
+*morph-spec v4.10.9 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -1,206 +1,206 @@
-# morph-spec Quick Start
-
-## Install
-
-```bash
-npm install -g @polymorphism-tech/morph-spec
-```
-
-Or use `npx` without a global install:
-
-```bash
-npx @polymorphism-tech/morph-spec init
-```
-
-> **Windows / nvm-windows:** Global installs may not appear on PATH. Use `npx` or add the npm prefix to PATH manually: `npm config get prefix`, then add `{prefix}` to your PATH.
-
----
-
-## Initialize a project
-
-Navigate to your project root and run:
-
-```bash
-morph-spec init
-```
-
-`init` does the following:
-- Auto-detects your stack (Blazor, Next.js, Node.js, monorepo)
-- Creates `.morph/` with framework files, standards, and templates
-- Creates `.morph/context/` with inferred project context
-- Installs `.claude/skills/`, `.claude/agents/`, `.claude/rules/`
-- Writes `.claude/settings.local.json` with 10 Claude Code hooks
-- Copies `CLAUDE.md` with runtime instructions
-
-Verify the installation:
-
-```bash
-morph-spec doctor
-```
-
----
-
-## Your first feature
-
-Open your project in Claude Code and run:
-
-```
-/morph-proposal my-feature
-```
-
-Replace `my-feature` with a short kebab-case name for your feature (e.g., `user-notifications`, `payment-flow`).
-
-The proposal pipeline runs phases 0–4 with three approval gates:
-
-### Phase 0 — Proposal
-
-Claude analyzes your request, detects which agents are relevant, and produces `0-proposal/proposal.md`. You review it and approve (or request changes).
-
-### Phase 1 — Setup
-
-Loads project context from `.morph/context/`, confirms stack and active agents. No approval needed.
-
-### Phase 1.5 — UI/UX (conditional)
-
-Only runs if frontend agents are active. Claude generates:
-- `2-ui/design-system.md` — colors, typography, spacing
-- `2-ui/mockups.md` — ASCII wireframes
-- `2-ui/components.md` — component specs
-- `2-ui/flows.md` — user flows and edge cases
-
-You approve the UI design before design phase begins.
-
-### Phase 2 — Design
-
-Claude produces the technical specification:
-- `1-design/spec.md` — full requirements, use cases, validations
-- `1-design/contracts.cs` — C# interfaces, DTOs, enums
-- `1-design/decisions.md` — architectural decision records (ADRs)
-
-You review and approve the design.
-
-### Phase 3 — Clarify
-
-Claude identifies 3–7 ambiguities in the spec, asks you to resolve them, then updates the spec. No gate.
-
-### Phase 4 — Tasks
-
-Claude breaks the spec into atomic tasks (`T001`, `T002`, …) saved to `3-tasks/tasks.md`. You approve the task list.
-
-At this point, planning is complete:
-
-```
-✅ Planning complete — run /morph-apply my-feature to implement
-```
-
----
-
-## Implement
-
-```
-/morph-apply my-feature
-```
-
-Claude reads `spec.md`, `contracts.cs`, and `tasks.md`, then implements task by task:
-- Starts each task, writes the code, marks it done
-- Runs 5 validators automatically after each task: security, architecture, packages, design system, Blazor concurrency
-- Auto-checkpoints every 3 tasks (validates, saves state)
-- Generates `4-implement/recap.md` on completion
-
----
-
-## During development
-
-Check feature state:
-
-```bash
-morph-spec state get my-feature
-morph-spec status my-feature
-```
-
-Advance to the next phase manually (when needed):
-
-```bash
-morph-spec phase advance my-feature
-```
-
-Mark a task complete:
-
-```bash
-morph-spec task done my-feature T001
-```
-
-Run validators at any time:
-
-```bash
-morph-spec validate                    # all validators
-morph-spec validate architecture       # specific validator
-morph-spec validate packages
-```
-
----
-
-## Multiple features
-
-You can have multiple features in progress simultaneously. Each has its own directory under `.morph/features/`:
-
-```
-.morph/features/
-├── user-notifications/
-│   ├── 0-proposal/
-│   ├── 1-design/
-│   └── 3-tasks/
-└── payment-flow/
-    ├── 0-proposal/
-    └── 1-design/
-```
-
-See all feature states:
-
-```bash
-morph-spec state list
-```
-
----
-
-## Keeping up to date
-
-When a new version of `@polymorphism-tech/morph-spec` is published:
-
-```bash
-# Update the CLI
-npm install -g @polymorphism-tech/morph-spec@latest
-
-# Update framework files in your project
-morph-spec update
-
-# Verify
-morph-spec doctor
-```
-
-`morph-spec update` re-syncs `.morph/framework/`, `.claude/skills/`, `.claude/agents/`, `.claude/rules/`, and `CLAUDE.md`. It does not touch your config, context, or feature outputs.
-
----
-
-## Tips
-
-**Use `/morph-proposal` even for small features.** The proposal phase catches scope creep, identifies the right agents, and generates contracts early — before implementation makes it expensive to change direction.
-
-**Approve explicitly at each gate.** The design gate exists to prevent implementing the wrong thing. If something in `spec.md` or `contracts.cs` looks off, say so before approving.
-
-**ADRs belong in `decisions.md`.** When Claude makes an architectural choice, it documents it there. Read it after Design completes. Decisions drive the validators that run during implementation.
-
-**`morph-spec doctor` is your first debugging step.** If something is behaving unexpectedly, doctor will surface version mismatches, missing files, and hook configuration issues.
-
----
-
-## Next steps
-
-- [CHEATSHEET.md](CHEATSHEET.md) — command reference
-- [ARCHITECTURE.md](ARCHITECTURE.md) — system design and agent hierarchy
-- [CHANGELOG.md](../CHANGELOG.md) — release history
-- `.morph/framework/standards/` — all coding and architecture standards
-
----
-
-*morph-spec v4.10.7 by Polymorphism Tech*
+# morph-spec Quick Start
+
+## Install
+
+```bash
+npm install -g @polymorphism-tech/morph-spec
+```
+
+Or use `npx` without a global install:
+
+```bash
+npx @polymorphism-tech/morph-spec init
+```
+
+> **Windows / nvm-windows:** Global installs may not appear on PATH. Use `npx` or add the npm prefix to PATH manually: `npm config get prefix`, then add `{prefix}` to your PATH.
+
+---
+
+## Initialize a project
+
+Navigate to your project root and run:
+
+```bash
+morph-spec init
+```
+
+`init` does the following:
+- Auto-detects your stack (Blazor, Next.js, Node.js, monorepo)
+- Creates `.morph/` with framework files, standards, and templates
+- Creates `.morph/context/` with inferred project context
+- Installs `.claude/skills/`, `.claude/agents/`, `.claude/rules/`
+- Writes `.claude/settings.local.json` with 10 Claude Code hooks
+- Copies `CLAUDE.md` with runtime instructions
+
+Verify the installation:
+
+```bash
+morph-spec doctor
+```
+
+---
+
+## Your first feature
+
+Open your project in Claude Code and run:
+
+```
+/morph-proposal my-feature
+```
+
+Replace `my-feature` with a short kebab-case name for your feature (e.g., `user-notifications`, `payment-flow`).
+
+The proposal pipeline runs phases 0–4 with three approval gates:
+
+### Phase 0 — Proposal
+
+Claude analyzes your request, detects which agents are relevant, and produces `0-proposal/proposal.md`. You review it and approve (or request changes).
+
+### Phase 1 — Setup
+
+Loads project context from `.morph/context/`, confirms stack and active agents. No approval needed.
+
+### Phase 1.5 — UI/UX (conditional)
+
+Only runs if frontend agents are active. Claude generates:
+- `2-ui/design-system.md` — colors, typography, spacing
+- `2-ui/mockups.md` — ASCII wireframes
+- `2-ui/components.md` — component specs
+- `2-ui/flows.md` — user flows and edge cases
+
+You approve the UI design before design phase begins.
+
+### Phase 2 — Design
+
+Claude produces the technical specification:
+- `1-design/spec.md` — full requirements, use cases, validations
+- `1-design/contracts.cs` — C# interfaces, DTOs, enums
+- `1-design/decisions.md` — architectural decision records (ADRs)
+
+You review and approve the design.
+
+### Phase 3 — Clarify
+
+Claude identifies 3–7 ambiguities in the spec, asks you to resolve them, then updates the spec. No gate.
+
+### Phase 4 — Tasks
+
+Claude breaks the spec into atomic tasks (`T001`, `T002`, …) saved to `3-tasks/tasks.md`. You approve the task list.
+
+At this point, planning is complete:
+
+```
+✅ Planning complete — run /morph-apply my-feature to implement
+```
+
+---
+
+## Implement
+
+```
+/morph-apply my-feature
+```
+
+Claude reads `spec.md`, `contracts.cs`, and `tasks.md`, then implements task by task:
+- Starts each task, writes the code, marks it done
+- Runs 5 validators automatically after each task: security, architecture, packages, design system, Blazor concurrency
+- Auto-checkpoints every 3 tasks (validates, saves state)
+- Generates `4-implement/recap.md` on completion
+
+---
+
+## During development
+
+Check feature state:
+
+```bash
+morph-spec state get my-feature
+morph-spec status my-feature
+```
+
+Advance to the next phase manually (when needed):
+
+```bash
+morph-spec phase advance my-feature
+```
+
+Mark a task complete:
+
+```bash
+morph-spec task done my-feature T001
+```
+
+Run validators at any time:
+
+```bash
+morph-spec validate                    # all validators
+morph-spec validate architecture       # specific validator
+morph-spec validate packages
+```
+
+---
+
+## Multiple features
+
+You can have multiple features in progress simultaneously. Each has its own directory under `.morph/features/`:
+
+```
+.morph/features/
+├── user-notifications/
+│   ├── 0-proposal/
+│   ├── 1-design/
+│   └── 3-tasks/
+└── payment-flow/
+    ├── 0-proposal/
+    └── 1-design/
+```
+
+See all feature states:
+
+```bash
+morph-spec state list
+```
+
+---
+
+## Keeping up to date
+
+When a new version of `@polymorphism-tech/morph-spec` is published:
+
+```bash
+# Update the CLI
+npm install -g @polymorphism-tech/morph-spec@latest
+
+# Update framework files in your project
+morph-spec update
+
+# Verify
+morph-spec doctor
+```
+
+`morph-spec update` re-syncs `.morph/framework/`, `.claude/skills/`, `.claude/agents/`, `.claude/rules/`, and `CLAUDE.md`. It does not touch your config, context, or feature outputs.
+
+---
+
+## Tips
+
+**Use `/morph-proposal` even for small features.** The proposal phase catches scope creep, identifies the right agents, and generates contracts early — before implementation makes it expensive to change direction.
+
+**Approve explicitly at each gate.** The design gate exists to prevent implementing the wrong thing. If something in `spec.md` or `contracts.cs` looks off, say so before approving.
+
+**ADRs belong in `decisions.md`.** When Claude makes an architectural choice, it documents it there. Read it after Design completes. Decisions drive the validators that run during implementation.
+
+**`morph-spec doctor` is your first debugging step.** If something is behaving unexpectedly, doctor will surface version mismatches, missing files, and hook configuration issues.
+
+---
+
+## Next steps
+
+- [CHEATSHEET.md](CHEATSHEET.md) — command reference
+- [ARCHITECTURE.md](ARCHITECTURE.md) — system design and agent hierarchy
+- [CHANGELOG.md](../CHANGELOG.md) — release history
+- `.morph/framework/standards/` — all coding and architecture standards
+
+---
+
+*morph-spec v4.10.9 by Polymorphism Tech*

package/framework/agents/README.md

@@ -1,14 +1,14 @@
-# Level 2: Domains
-
-Domain expertise skills organized by squad.
-
-**Purpose:** Skills that provide deep domain knowledge (backend, frontend, infra, quality, ai-agents, integrations).
-
-**Squads:**
-- backend/ - Backend Squad (led by dotnet-senior)
-- frontend/ - Frontend Squad (led by ui-designer)
-- infrastructure/ - Infrastructure Squad (led by infra-architect)
-- quality/ - Quality Squad (coordinated by standards-architect)
-- ai-agents/ - AI/Agent specialists
-- integrations/ - External integration specialists
-- architecture/ - Architecture and planning
+# Level 2: Domains
+
+Domain expertise skills organized by squad.
+
+**Purpose:** Skills that provide deep domain knowledge (backend, frontend, infra, quality, ai-agents, integrations).
+
+**Squads:**
+- backend/ - Backend Squad (led by dotnet-senior)
+- frontend/ - Frontend Squad (led by ui-designer)
+- infrastructure/ - Infrastructure Squad (led by infra-architect)
+- quality/ - Quality Squad (coordinated by standards-architect)
+- ai-agents/ - AI/Agent specialists
+- integrations/ - External integration specialists
+- architecture/ - Architecture and planning