@polymorphism-tech/morph-spec 4.8.8 → 4.8.9

package/README.md

@@ -3,7 +3,7 @@
 > Spec-driven development framework for multi-stack projects. Turns feature requests into implementation-ready code through structured, AI-orchestrated phases.
 
 **Package:** `@polymorphism-tech/morph-spec`
-**Version:** 4.8.8  
+**Version:** 4.8.9  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -376,4 +376,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.8.8 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.8.9 by [Polymorphism Tech](https://polymorphism.tech)*

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.8.8",
+  "version": "4.8.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",

package/docs/CHEATSHEET.md

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

package/docs/QUICKSTART.md

@@ -203,4 +203,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.8.8 by Polymorphism Tech*
+*morph-spec v4.8.9 by Polymorphism Tech*

package/framework/agents.json

@@ -35,7 +35,8 @@
           "code-analyzer",
           "troubleshooting-expert",
           "documentation-specialist",
-          "load-testing-expert"
+          "load-testing-expert",
+          "vsa-architect"
         ],
         "escalates_to": "user",
         "team_role": "lead"

package/framework/hooks/dev/guard-version-numbers.js

@@ -7,7 +7,7 @@
  * Scope: Framework codebase only (dev hook)
  *
  * Blocks Write/Edit to files that contain hardcoded version patterns
- * like "MORPH-SPEC v4.8.8". Version should only be in package.json.
+ * like "MORPH-SPEC v4.8.9". Version should only be in package.json.
  *
  * Checked extensions: .md, .cs, .css, .js (covers templates + source)
  * Exceptions: CHANGELOG.md, node_modules/, test/, package.json, package-lock.json

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 3 (Clarify). Reviews spec.md for ambiguities, gene
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH Clarify - FASE 3

package/framework/skills/level-1-workflows/phase-codebase-analysis/SKILL.md

@@ -3,7 +3,7 @@ name: 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
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH Codebase Analysis - Sub-fase de DESIGN

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

@@ -1,10 +1,10 @@
 ---
 name: phase-design
-description: MORPH-SPEC Phase 2 (Design). Analyzes codebase/schema, then produces spec.md, contracts-level{N}.cs, schema-analysis.md, and decisions.md for the feature. Use after setup phase to create a full technical specification with C# contracts based on the real database schema and architecture decision records.
+description: MORPH-SPEC Phase 2 (Design). Analyzes codebase/schema, then produces spec.md, contracts.cs (contracts-vsa.cs for VSA or contracts-level{N}.cs for DDD), schema-analysis.md, and decisions.md for the feature. Use after setup phase to create a full technical specification with C# contracts based on the real database schema and architecture decision records.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH Design - FASE 2

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

@@ -6,7 +6,7 @@ disable-model-invocation: true
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/skills/level-1-workflows/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
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH Setup - FASE 1

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

@@ -5,7 +5,7 @@ argument-hint: "[feature-name]"
 disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH Tasks - FASE 4
@@ -44,6 +44,9 @@ Quebre a especificação em tasks executáveis, defina ordem de execução e est
 - ✅ Task agent para specs multi-domínio (backend + frontend + infra = 3 planners em paralelo)
 - ✅ Task agent quando spec tem 20+ requisitos em múltiplos bounded contexts
 - ❌ Criar tasks.json sem ler todos os outputs primeiro
+- ❌ **(VSA)** Criar tasks separadas para Handler, Validator e Endpoint — um slice = uma task
+- ❌ **(VSA)** Usar categorias DDD (`domain`, `application`, `infrastructure`) em projetos VSA
+- ❌ **(VSA)** Criar task de "Implementar Service layer" — não existe em VSA
 
 ---
 
@@ -75,7 +78,111 @@ npx morph-spec approval get $ARGUMENTS design
 
 ---
 
-### Passo 0: Ler Nível de Domínio
+### Passo 0: Detectar Estilo de Arquitetura
+
+Antes de tudo, determine se o projeto é VSA ou DDD:
+
+```bash
+cat .morph/config/config.json | grep -A3 '"architecture"'
+```
+
+**Se `config.architecture.style === "vertical-slice"`** → siga o **Passo 0.5 (VSA)** e pule o Passo 0 DDD.
+**Caso contrário** → siga o **Passo 0.6 (DDD)** abaixo.
+
+---
+
+### Passo 0.5: Plano de Tasks — VSA
+
+**Ref:** `framework/standards/architecture/vertical-slice/vertical-slice.md`
+
+Leia a seção `## Architecture Style: Vertical Slice` do spec.md para o **VSA Blueprint** (entity fields, operações, rotas, validações):
+
+```bash
+grep -A30 "## Architecture Style" ".morph/features/$ARGUMENTS/1-design/spec.md"
+```
+
+**Categorias de tasks VSA** (uma task por slice — Handler + Validator + Endpoint juntos):
+
+| Categoria | Descrição | Arquivo(s) |
+|-----------|-----------|------------|
+| **entity** | Entity class + DbSet no ApplicationDbContext | `Entities/{Entity}.cs`, `Database/ApplicationDbContext.cs` |
+| **errors** | `{Entity}Errors` static class com factory methods | `Features/{Entity}Feature/{Entity}Errors.cs` |
+| **tags** | Constante em ApiTags (se tag nova) | `Constants/ApiTags.cs` |
+| **migration** | `dotnet ef migrations add` + `database update` | `Migrations/...` |
+| **slice** | Slice completo: Handler (+ Request + Response records) + Validator + Endpoint | `Features/{Entity}Feature/{Op}/{Op}Handler.cs`, `...Validator.cs`, `...Endpoint.cs` |
+| **tests** | Unit tests dos handlers | `Tests/Features/{Entity}Feature/...` |
+| **docs** | README, Swagger, comentários | — |
+
+**Ordem obrigatória (bottom-up VSA):**
+
+```
+T001: Entity + DbContext DbSet
+   ↓
+T002: {Entity}Errors (factory methods)
+   ↓
+T003: ApiTags constant (se tag ainda não existe)
+   ↓
+T004: Migration (Add{Entity} + database update)
+   ↓
+T005: Slice Create{Entity}     ← Handler+Validator+Endpoint = 1 task
+T006: Slice GetAll{Entity}s    ← Handler+Endpoint = 1 task (sem Validator)
+T007: Slice Get{Entity}ById    ← Handler+Validator+Endpoint = 1 task
+T008: Slice Update{Entity}     ← Handler+Validator+Endpoint = 1 task
+T009: Slice Delete{Entity}     ← Handler+Validator+Endpoint = 1 task
+   ↓
+T010+: Slices customizados (operações extra do VSA Blueprint)
+   ↓
+T0NN: Tests
+```
+
+**Regras VSA para tasks:**
+- 1 task = 1 slice completo (Handler + Validator + Endpoint num único task)
+- `GetAll` NÃO tem Validator — mencionar explicitamente no task
+- Cada task de slice lista os 3 arquivos que devem ser criados no campo `files`
+- Entity task deve incluir a linha `DbSet<{Entity}>` no `ApplicationDbContext`
+- Migration task é separada da entity task (pode rodar em paralelo com errors + tags)
+
+**Exemplo de tasks VSA geradas:**
+
+```json
+{ "id": "T001", "title": "Criar Entity Book + registrar DbSet no ApplicationDbContext",
+  "category": "entity", "dependencies": [],  "estimatedMinutes": 20,
+  "files": ["Entities/Book.cs", "Database/ApplicationDbContext.cs"] }
+
+{ "id": "T002", "title": "Criar BookErrors (NotFound + outros factory methods)",
+  "category": "errors", "dependencies": ["T001"], "estimatedMinutes": 10,
+  "files": ["Features/BookFeature/BookErrors.cs"] }
+
+{ "id": "T003", "title": "Adicionar ApiTags.Books em Constants/ApiTags.cs",
+  "category": "tags", "dependencies": [], "estimatedMinutes": 5,
+  "files": ["Constants/ApiTags.cs"] }
+
+{ "id": "T004", "title": "Criar migration AddBook + aplicar ao banco",
+  "category": "migration", "dependencies": ["T001"], "estimatedMinutes": 10,
+  "files": ["Migrations/...AddBook.cs"] }
+
+{ "id": "T005", "title": "Implementar slice CreateBook (Handler + Validator + Endpoint)",
+  "category": "slice", "dependencies": ["T001", "T002", "T003", "T004"],
+  "estimatedMinutes": 45,
+  "files": [
+    "Features/BookFeature/CreateBook/CreateBookHandler.cs",
+    "Features/BookFeature/CreateBook/CreateBookValidator.cs",
+    "Features/BookFeature/CreateBook/CreateBookEndpoint.cs"
+  ] }
+
+{ "id": "T006", "title": "Implementar slice GetAllBooks (Handler + Endpoint, sem Validator)",
+  "category": "slice", "dependencies": ["T001", "T004"], "estimatedMinutes": 25,
+  "files": [
+    "Features/BookFeature/GetAllBooks/GetAllBooksHandler.cs",
+    "Features/BookFeature/GetAllBooks/GetAllBooksEndpoint.cs"
+  ] }
+```
+
+**Após definir tasks VSA, pule direto para o Passo 3 (Dependências).**
+
+---
+
+### Passo 0.6: Ler Nível de Domínio — DDD
 
 **Ref:** `framework/standards/architecture/ddd/complexity-levels.md`
 
@@ -115,10 +222,12 @@ Use o nível para **restringir** as categorias de tasks às listadas para o nív
 
 ### Passo 1: Analisar Spec
 
+> **VSA:** Se veio do Passo 0.5, o breakdown de tasks já foi definido — use os exemplos gerados como base e pule para o Passo 3 (Dependências).
+
 Leia `.morph/features/$ARGUMENTS/1-design/spec.md` e identifique:
 
 1. **Requisitos funcionais** (FR001, FR002, ...)
-2. **Componentes técnicos** (Entities, Services, Controllers, Pages)
+2. **Componentes técnicos** (Entities, Services/Slices, Controllers/Endpoints, Pages)
 3. **Infraestrutura** (Bicep, migrations, configs)
 4. **Testes** (Unit tests, integration tests)
 

package/framework/skills/level-1-workflows/phase-tasks/references/tasks-example.md

@@ -228,4 +228,177 @@ Integration tests using `WebApplicationFactory` + in-memory SQLite (or TestConta
 
 ---
 
+---
+
+# Tasks - Book CRUD (VSA Example)
+
+> Example of tasks.md for a Vertical Slice Architecture (VSA) feature.
+> Key rule: 1 task = 1 complete slice (Handler + Validator + Endpoint together).
+> GetAll slices have no Validator — stated explicitly in the task.
+
+| Task ID | Category | Title | Status |
+|---------|----------|-------|--------|
+| T001 | entity | Criar Entity Book + registrar DbSet no ApplicationDbContext | Pending |
+| T002 | errors | Criar BookErrors (NotFound + outros factory methods) | Pending |
+| T003 | tags | Adicionar ApiTags.Books em Constants/ApiTags.cs | Pending |
+| T004 | migration | Criar migration AddBook + aplicar ao banco | Pending |
+| T005 | slice | Implementar slice CreateBook (Handler + Validator + Endpoint) | Pending |
+| T006 | slice | Implementar slice GetAllBooks (Handler + Endpoint, sem Validator) | Pending |
+| T007 | slice | Implementar slice GetBookById (Handler + Validator + Endpoint) | Pending |
+| T008 | slice | Implementar slice UpdateBook (Handler + Validator + Endpoint) | Pending |
+| T009 | slice | Implementar slice DeleteBook (Handler + Validator + Endpoint) | Pending |
+
+**Status Values:** `Pending | In Progress | Blocked | Done`
+
+---
+
+## Phase 1: Foundation
+
+### T001: Criar Entity Book + registrar DbSet no ApplicationDbContext
+- **Category:** entity
+- **Estimate:** 20min
+- **Dependencies:** None
+
+**Description:**
+Criar a entity `Book` com todos os campos definidos no spec.md. Registrar `DbSet<Book>` no `ApplicationDbContext`. Usar `Guid.CreateVersion7()` para o campo Id — não `Guid.NewGuid()`. Propriedades obrigatórias como `sealed` ou com setters `private init`.
+
+**Deliverables:**
+- [ ] Create: `Entities/Book.cs`
+- [ ] Update: `Database/ApplicationDbContext.cs` (add `public DbSet<Book> Books { get; set; } = null!;`)
+
+---
+
+### T002: Criar BookErrors (NotFound + outros factory methods)
+- **Category:** errors
+- **Estimate:** 10min
+- **Dependencies:** T001
+
+**Description:**
+Criar a classe `BookErrors` static com factory methods para cada tipo de erro da feature. Cada method retorna um `Error` com code e description. Esses erros são compartilhados por todos os slices da BookFeature.
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/BookErrors.cs`
+
+---
+
+### T003: Adicionar ApiTags.Books em Constants/ApiTags.cs
+- **Category:** tags
+- **Estimate:** 5min
+- **Dependencies:** None
+
+**Description:**
+Adicionar a constante `Books` em `ApiTags` para uso em todos os endpoints da feature. Se a constante já existir, pular esta task.
+
+**Deliverables:**
+- [ ] Update: `Constants/ApiTags.cs` (add `public const string Books = "books";`)
+
+---
+
+### T004: Criar migration AddBook + aplicar ao banco
+- **Category:** migration
+- **Estimate:** 10min
+- **Dependencies:** T001
+
+**Description:**
+Gerar a migration EF Core para a entity `Book` e aplicar ao banco local. Verificar que a migration foi gerada corretamente antes de aplicar.
+
+**Deliverables:**
+- [ ] Run: `dotnet ef migrations add AddBook`
+- [ ] Run: `dotnet ef database update`
+- [ ] Verify: migration applies without errors
+
+---
+
+## Phase 2: Slices
+
+### T005: Implementar slice CreateBook (Handler + Validator + Endpoint)
+- **Category:** slice
+- **Estimate:** 45min
+- **Dependencies:** T001, T002, T003, T004
+
+**Description:**
+Implementar o slice completo de criação. O arquivo Handler deve conter os records `CreateBookRequest` e `CreateBookResponse` no mesmo arquivo. O Validator deve herdar de `AbstractValidator<CreateBookRequest>`. O Endpoint deve ser `internal sealed` e usar `result.Match()` — nunca `result.Value` sem checar `IsSuccess`.
+
+Handler injeta: `IRepository<Book>` + `IUnitOfWork`.
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/CreateBook/CreateBookHandler.cs`
+- [ ] Create: `Features/BookFeature/CreateBook/CreateBookValidator.cs`
+- [ ] Create: `Features/BookFeature/CreateBook/CreateBookEndpoint.cs`
+
+---
+
+### T006: Implementar slice GetAllBooks (Handler + Endpoint, sem Validator)
+- **Category:** slice
+- **Estimate:** 25min
+- **Dependencies:** T001, T004
+
+**Description:**
+Implementar o slice de listagem. GetAll NÃO tem Validator (sem parâmetros de entrada para validar). Handler injeta apenas `IRepository<Book>` — não precisa de `IUnitOfWork` (read-only).
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/GetAllBooks/GetAllBooksHandler.cs`
+- [ ] Create: `Features/BookFeature/GetAllBooks/GetAllBooksEndpoint.cs`
+
+---
+
+### T007: Implementar slice GetBookById (Handler + Validator + Endpoint)
+- **Category:** slice
+- **Estimate:** 30min
+- **Dependencies:** T001, T002, T004
+
+**Description:**
+Implementar o slice de busca por ID. Validator verifica que o Guid não é empty. Handler retorna `BookErrors.NotFound()` se o livro não existir. Handler injeta apenas `IRepository<Book>`.
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/GetBookById/GetBookByIdHandler.cs`
+- [ ] Create: `Features/BookFeature/GetBookById/GetBookByIdValidator.cs`
+- [ ] Create: `Features/BookFeature/GetBookById/GetBookByIdEndpoint.cs`
+
+---
+
+### T008: Implementar slice UpdateBook (Handler + Validator + Endpoint)
+- **Category:** slice
+- **Estimate:** 45min
+- **Dependencies:** T001, T002, T003, T004
+
+**Description:**
+Implementar o slice de atualização. Handler retorna `BookErrors.NotFound()` se o livro não existir antes de atualizar. Handler injeta: `IRepository<Book>` + `IUnitOfWork`.
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/UpdateBook/UpdateBookHandler.cs`
+- [ ] Create: `Features/BookFeature/UpdateBook/UpdateBookValidator.cs`
+- [ ] Create: `Features/BookFeature/UpdateBook/UpdateBookEndpoint.cs`
+
+---
+
+### T009: Implementar slice DeleteBook (Handler + Validator + Endpoint)
+- **Category:** slice
+- **Estimate:** 30min
+- **Dependencies:** T001, T002, T003, T004
+
+**Description:**
+Implementar o slice de deleção. Handler verifica existência antes de deletar, retorna `BookErrors.NotFound()` se não existir. Handler injeta: `IRepository<Book>` + `IUnitOfWork`.
+
+**Deliverables:**
+- [ ] Create: `Features/BookFeature/DeleteBook/DeleteBookHandler.cs`
+- [ ] Create: `Features/BookFeature/DeleteBook/DeleteBookValidator.cs`
+- [ ] Create: `Features/BookFeature/DeleteBook/DeleteBookEndpoint.cs`
+
+---
+
+## Summary
+
+| Phase | Tasks | Estimate |
+|-------|-------|----------|
+| Foundation (entity + errors + tags + migration) | T001–T004 | 45min |
+| Slices (Create + GetAll + GetById + Update + Delete) | T005–T009 | 2h55m |
+| **Total** | **9 tasks** | **~3h40m** |
+
+> **VSA Note:** No manual DI registration needed — `AddHandlersFromAssembly()`,
+> `RegisterApiEndpointsFromAssembly()`, and `AddValidatorsFromAssembly()` discover
+> all handlers, endpoints and validators automatically via assembly scanning (Scrutor).
+
+---
+
 *MORPH-SPEC by Polymorphism Tech*

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md,
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-cliVersion: "4.8.8"
+cliVersion: "4.8.9"
 ---
 
 # MORPH UI/UX Design - FASE 1.5

package/framework/templates/docs/spec.md

@@ -99,9 +99,41 @@ public interface I{{pascalCase FEATURE_NAME}}Service
 
 ---
 
+## Architecture Style: Vertical Slice
+
+> Preencher SOMENTE se `config.architecture.style === "vertical-slice"`. Omitir em projetos DDD.
+
+**Architecture Style:** Vertical Slice Architecture (VSA)
+
+**Entity Fields:**
+| Field | Type | Constraints |
+|-------|------|-------------|
+| Id | Guid | PK, `Guid.CreateVersion7()` |
+| {Field} | {C# Type} | {Required / Optional / Unique} |
+| CreatedAt | DateTimeOffset | Auto |
+
+**Operations:**
+| Slice | HTTP | Route | Has Validator |
+|-------|------|-------|---------------|
+| Create{Entity} | POST | {ROUTE} | Yes |
+| GetAll{Entity}s | GET | {ROUTE} | No |
+| Get{Entity}ById | GET | {ROUTE}/{id} | Yes |
+| Update{Entity} | PUT | {ROUTE}/{id} | Yes |
+| Delete{Entity} | DELETE | {ROUTE}/{id} | Yes |
+
+**Error Types ({Entity}Errors):**
+- `{Entity}Errors.{ErrorName}()` — {description}
+
+**Validation Rules:**
+| Field | Rules |
+|-------|-------|
+| {Field} | NotEmpty(), MaxLength({N}), {etc.} |
+
+---
+
 ## Aggregate Blueprint (Nível 2+ apenas)
 
-> Omitir esta seção se Nível 1 (CRUD).
+> Omitir esta seção se Nível 1 (CRUD) ou se Architecture Style = Vertical Slice.
 
 ### Aggregate Root: {EntityName}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "4.8.8",
+  "version": "4.8.9",
   "description": "MORPH-SPEC: AI-First development framework with validation pipeline and multi-stack support",
   "keywords": [
     "claude-code",

package/src/commands/project/doctor.js

@@ -136,6 +136,7 @@ const FRAMEWORK_STANDARDS = [
   'framework/standards/architecture/ddd/aggregates.md',
   'framework/standards/architecture/ddd/entities.md',
   'framework/standards/architecture/ddd/value-objects.md',
+  'framework/standards/architecture/vertical-slice/vertical-slice.md',
   'framework/standards/data/vector-search/azure-ai-search.md',
   'framework/standards/data/vector-search/rag-chunking.md',
   'framework/standards/context/priming.md',