aw-spec-cli 0.1.18 → 0.1.20

package/assets/guardrails/domain/healthcare/auditing.domain.md

@@ -2,7 +2,7 @@
 
 > Technology base: [[auditing]]. NON-NEGOTIABLE. Consumed by `/aw-spec-specify` (LIFTS the
 > auditing requirement into the spec) and `/aw-spec-gate` (VALIDATES the spec/design realise it).
-> `/aw-spec-design` and `/aw-spec-implement` never load this file — auditing reaches them through
+> `/aw-spec-plan` and `/aw-spec-implement` never load this file — auditing reaches them through
 > the spec's **declared audit level per aggregate**, and the enablement mechanics live in the
 > technical base [[auditing]]. Keep this file technology-agnostic (levels + rules, **no code**).
 
@@ -24,7 +24,7 @@ audit interceptor populates every audit field automatically (handlers NEVER assi
 
 > Code realisation — marker interfaces (Basic = `IAuditedObject` / `IFullAuditedObject`; Advanced =
 > `+ IFieldAudited`), the one-time composition, and the audit query API — lives in the technical
-> base. See [[auditing]]; `/aw-spec-design` and `/aw-spec-implement` get the HOW from there.
+> base. See [[auditing]]; `/aw-spec-plan` and `/aw-spec-implement` get the HOW from there.
 
 ## Aggregate assignment rule (how specify decides the level)
 
@@ -35,7 +35,7 @@ spec as an explicit, developer-editable declaration:
   history requires field-level before/after).
 - **Supporting aggregates** (collaborating/referenced roots, no PHI) → **Basic** by default.
 - A developer MAY raise or lower a level afterwards by editing the spec declaration — the level is
-  a **spec** decision, never a design or implementation one. `/aw-spec-design` then follows the
+  a **spec** decision, never a design or implementation one. `/aw-spec-plan` then follows the
   declared level.
 
 Lift it as one line the gate can check, e.g. under Constraints:

package/assets/guardrails/domain/pharma/auditing.domain.md

@@ -2,7 +2,7 @@
 
 > Technology base: [[auditing]]. NON-NEGOTIABLE. Consumed by `/aw-spec-specify` (LIFTS the
 > auditing requirement into the spec) and `/aw-spec-gate` (VALIDATES the spec/design realise it).
-> `/aw-spec-design` and `/aw-spec-implement` never load this file — auditing reaches them through
+> `/aw-spec-plan` and `/aw-spec-implement` never load this file — auditing reaches them through
 > the spec's **declared audit level per aggregate**, and the enablement mechanics live in the
 > technical base [[auditing]]. Keep this file technology-agnostic (levels + rules, **no code**).
 
@@ -22,7 +22,7 @@ audit field automatically (handlers NEVER assign audit fields):
 
 > Code realisation — marker interfaces (Basic = `IAuditedObject` / `IFullAuditedObject`; Advanced =
 > `+ IFieldAudited`), the one-time composition, and the audit query API — lives in the technical
-> base. See [[auditing]]; `/aw-spec-design` and `/aw-spec-implement` get the HOW from there.
+> base. See [[auditing]]; `/aw-spec-plan` and `/aw-spec-implement` get the HOW from there.
 
 ## Aggregate assignment rule (how specify decides the level)
 
@@ -32,7 +32,7 @@ spec as an explicit, developer-editable declaration:
 - The **main aggregate** of the requirement (the aggregate root the story is about) → **Advanced**.
 - **Supporting aggregates** (collaborating/referenced roots) → **Basic** by default.
 - A developer MAY raise or lower a level afterwards by editing the spec declaration — the level is
-  a **spec** decision, never a design or implementation one. `/aw-spec-design` then follows the
+  a **spec** decision, never a design or implementation one. `/aw-spec-plan` then follows the
   declared level.
 
 Lift it as one line the gate can check, e.g. under Constraints:

package/assets/guardrails/technology/dotnet-webapi/api-versioning.md

@@ -1,6 +1,6 @@
 # API Versioning Policy
 
-> Pure technology (domain-agnostic) — domain (e.g. FHIR) versioning in [[api-versioning.domain]]. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain (e.g. FHIR) versioning in [[api-versioning.domain]]. Commands: `/aw-spec-plan`.
 
 ## REST versioning
 

package/assets/guardrails/technology/dotnet-webapi/auditing.md

@@ -1,6 +1,6 @@
 # Auditing & Observability Standards
 
-> Pure technology (domain-agnostic) — domain audit additions in [[auditing.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain audit additions in [[auditing.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`.
 
 ## Observability baseline
 

package/assets/guardrails/technology/dotnet-webapi/authorization.md

@@ -1,6 +1,6 @@
 # Authorization Standards
 
-> Pure technology (domain-agnostic) — domain roles & matrix in [[authorization.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain roles & matrix in [[authorization.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`.
 
 ## Authorization model
 

package/assets/guardrails/technology/dotnet-webapi/clean-architecture.md

@@ -1,6 +1,6 @@
 # Clean Architecture Standards
 
-> Pure technology (domain-agnostic). NON-NEGOTIABLE. Commands: `/aw-spec-design`, `/aw-spec-build`.
+> Pure technology (domain-agnostic). NON-NEGOTIABLE. Commands: `/aw-spec-plan`, `/aw-spec-build`.
 
 ## Dependency direction
 

package/assets/guardrails/technology/dotnet-webapi/cqrs.md

@@ -1,6 +1,6 @@
 # CQRS + Mediator Standards
 
-> Pure technology (domain-agnostic) — domain additions in [[cqrs.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain additions in [[cqrs.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`.
 
 ## Command / query patterns
 

package/assets/guardrails/technology/dotnet-webapi/data-classification.md

@@ -1,6 +1,6 @@
 # Data Classification Standards
 
-> Pure technology (domain-agnostic) — domain data categories in [[data-classification.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain data categories in [[data-classification.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`.
 
 ## Classification framework
 

package/assets/guardrails/technology/dotnet-webapi/eventing.md

@@ -1,6 +1,6 @@
 # Eventing Standards
 
-> Pure technology (domain-agnostic) — domain additions in [[eventing.domain]]. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain additions in [[eventing.domain]]. Commands: `/aw-spec-plan`.
 
 ## Domain events
 

package/assets/guardrails/technology/dotnet-webapi/folder-structure.md

@@ -1,6 +1,6 @@
 # Mandatory Folder Structure
 
-> Pure technology (domain-agnostic) — domain additions (Interop adapters, conformance tests, fixtures) in [[folder-structure.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-design`, `/aw-spec-implement`, `/aw-spec-implement-delta`.
+> Pure technology (domain-agnostic) — domain additions (Interop adapters, conformance tests, fixtures) in [[folder-structure.domain]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`, `/aw-spec-implement`, `/aw-spec-implement-delta`.
 >
 > Replace `<SampleProjectName>` with the project name (e.g. `Acme.Billing`).
 

package/assets/guardrails/technology/dotnet-webapi/modular-monolith.md

@@ -1,6 +1,6 @@
 # Modular Monolith Standards
 
-> Pure technology (domain-agnostic). NON-NEGOTIABLE where marked. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic). NON-NEGOTIABLE where marked. Commands: `/aw-spec-plan`.
 
 ## Module boundaries
 

package/assets/guardrails/technology/dotnet-webapi/persistence.md

@@ -1,6 +1,6 @@
 # Persistence Standards
 
-> Pure technology (domain-agnostic) — domain additions in [[persistence.domain]]. NON-NEGOTIABLE where marked. Commands: `/aw-spec-design`, `/aw-spec-run`.
+> Pure technology (domain-agnostic) — domain additions in [[persistence.domain]]. NON-NEGOTIABLE where marked. Commands: `/aw-spec-plan`, `/aw-spec-run`.
 
 ## EF Core conventions
 

package/assets/guardrails/technology/dotnet-webapi/vertical-slices.md

@@ -1,6 +1,6 @@
 # Vertical Slice Standards
 
-> Pure technology (domain-agnostic) — domain additions in [[vertical-slices.domain]]. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain additions in [[vertical-slices.domain]]. Commands: `/aw-spec-plan`.
 
 ## Feature organization
 

package/assets/guardrails/technology/dotnet-webapi/zero-trust.md

@@ -1,6 +1,6 @@
 # Zero-Trust Standards
 
-> Pure technology (domain-agnostic) — domain additions in [[zero-trust.domain]]. NON-NEGOTIABLE where marked. Commands: `/aw-spec-design`.
+> Pure technology (domain-agnostic) — domain additions in [[zero-trust.domain]]. NON-NEGOTIABLE where marked. Commands: `/aw-spec-plan`.
 
 ## Transport security (mTLS / TLS)
 

package/assets/guardrails/technology/nextjs/accessibility-implementation.md

@@ -1,7 +1,7 @@
 # Accessibility Standards — nextjs (frontend lane)
 
 > Pure technology (domain-agnostic). NON-NEGOTIABLE.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-I (accessibility floor).
 
 UX-I makes the floor non-negotiable; this file is what meeting it means in practice. The

package/assets/guardrails/technology/nextjs/api-integration.dotnet-webapi.md

@@ -2,7 +2,7 @@
 
 > The CROSS-LANE pairing rules: how the `nextjs` frontend lane consumes an
 > `dotnet-webapi` service lane. NON-NEGOTIABLE where marked.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-IV (the contract is the only server input).
 
 This file is named for the service lane it pairs with, and a project maps it through the

package/assets/guardrails/technology/nextjs/api-integration.java-spring.md

@@ -2,7 +2,7 @@
 
 > The CROSS-LANE pairing rules: how the `nextjs` frontend lane consumes a `java-spring`
 > (Spring Boot) service lane. NON-NEGOTIABLE where marked.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-IV (the contract is the only server input).
 
 This file is named for the service lane it pairs with, and a project maps it through the

package/assets/guardrails/technology/nextjs/auth-session.md

@@ -1,7 +1,7 @@
 # Authentication & Session Standards — nextjs (frontend lane)
 
 > Pure technology (domain-agnostic). NON-NEGOTIABLE.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-VIII (client state carries no secret) and
 > UX-IV (the contract is the only server input).
 

package/assets/guardrails/technology/nextjs/component-architecture.md

@@ -1,6 +1,6 @@
 # Component Architecture Standards — nextjs (frontend lane)
 
-> Pure technology (domain-agnostic). Commands: `/aw-spec-design-ui`.
+> Pure technology (domain-agnostic). Commands: `/aw-spec-plan-ui`.
 > Detail layer under `constitution.ui.md` UX-II (design system) and UX-III (server components).
 
 The rules the UI design author composes a feature's `§3 Component Structure` from. They

package/assets/guardrails/technology/nextjs/design-system.md

@@ -1,7 +1,7 @@
 # Design System Standards — nextjs (frontend lane)
 
 > Pure technology (domain-agnostic). NON-NEGOTIABLE.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-II (the design system is the only source of
 > visual truth).
 

package/assets/guardrails/technology/nextjs/error-handling.md

@@ -1,6 +1,6 @@
 # Interaction & Error State Standards — nextjs (frontend lane)
 
-> Pure technology (domain-agnostic). Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Pure technology (domain-agnostic). Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-V (every interaction state is specified).
 
 The rules behind `design.ui.md §4 Interaction & Flow` — the section a backend-shaped

package/assets/guardrails/technology/nextjs/forms-and-validation.md

@@ -1,7 +1,7 @@
 # Forms & Validation Standards — nextjs (frontend lane)
 
 > Pure technology (domain-agnostic). NON-NEGOTIABLE where marked.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-V (every interaction state is specified) and
 > UX-VII (mutations flow through one path).
 

package/assets/guardrails/technology/nextjs/i18n.md

@@ -1,6 +1,6 @@
 # Internationalization Standards — nextjs (frontend lane)
 
-> Pure technology (domain-agnostic). Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Pure technology (domain-agnostic). Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-X (internationalization is structural).
 
 Internationalization is structural: it is cheap while the surface is being designed and

package/assets/guardrails/technology/nextjs/performance-budgets.md

@@ -1,7 +1,7 @@
 # Performance Budget Standards — nextjs (frontend lane)
 
 > Pure technology (domain-agnostic). NON-NEGOTIABLE.
-> Commands: `/aw-spec-design-ui`, `/aw-spec-implement-ui`.
+> Commands: `/aw-spec-plan-ui`, `/aw-spec-implement-ui`.
 > Detail layer under `constitution.ui.md` UX-IX (the performance budget is a gate).
 
 A budget that is not enforced is an aspiration. Core Web Vitals thresholds and a per-route

package/assets/guardrails/technology/nextjs/routing-navigation.md

@@ -1,6 +1,6 @@
 # Routing & Navigation Standards — nextjs (frontend lane)
 
-> Pure technology (domain-agnostic). Commands: `/aw-spec-design-ui`.
+> Pure technology (domain-agnostic). Commands: `/aw-spec-plan-ui`.
 > Detail layer under `constitution.ui.md` UX-III (server components) and UX-V (every
 > interaction state specified).
 

package/assets/guardrails/technology/nextjs/state-management.md

@@ -1,6 +1,6 @@
 # Client State Standards — nextjs (frontend lane)
 
-> Pure technology (domain-agnostic). Commands: `/aw-spec-design-ui`.
+> Pure technology (domain-agnostic). Commands: `/aw-spec-plan-ui`.
 > Detail layer under `constitution.ui.md` UX-VI (caching declared), UX-VII (one mutation
 > path) and UX-VIII (client state carries no secret).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aw-spec-cli",
-  "version": "0.1.18",
+  "version": "0.1.20",
   "description": "AppWeaver Spec-Driven Development CLI - scaffolds projects with vertical slices, DDD, CQRS, and agent skills",
   "type": "module",
   "main": "dist/index.js",