@polymorphism-tech/morph-spec 4.12.0 → 4.14.0

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ord
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.12.0"
+cliVersion: "4.14.0"
 ---
 
 # MORPH Tasks — Phase 4
@@ -15,9 +15,9 @@ Break the approved specification into executable tasks, define execution order,
 
 ## Prerequisites
 
-- [ ] Phase 3 (Clarify) completed
-- [ ] `spec.md` updated with clarifications
-- [ ] All edge cases documented
+- [ ] Design phase completed and approved
+- [ ] `spec.md` exists and approved
+- [ ] Plan phase completed
 
 ## Recommended Tools
 
@@ -42,7 +42,7 @@ Break the approved specification into executable tasks, define execution order,
 - Task agent to break down a simple single-domain spec (do it directly)
 - Creating tasks without reading all design outputs first
 - **(VSA)** Creating separate tasks for Handler, Validator, and Endpoint — one slice = one task
-- **(VSA)** Using DDD categories (`domain`, `application`, `infrastructure`) in VSA projects — use VSA categories: `entity`, `errors`, `tags`, `migration`, `slice`, `frontend`, `tests`
+- **(VSA)** Using generic layer categories (`domain`, `application`, `infrastructure`) in VSA projects — use VSA categories: `entity`, `errors`, `tags`, `migration`, `slice`, `frontend`, `tests`
 - **(VSA)** Creating a "Implement Service layer" task — there is no Service layer in VSA
 - Using vague effort labels ("Low", "Medium", "S/M") — always use specific minute estimates
 - Using non-standard task IDs (TASK-001, T01) — always use **T001** format (T + 3 digits)
@@ -61,9 +61,8 @@ Check the `"phase"` field:
 
 **If `"phase": "tasks"`** → correct phase, proceed.
 
-**If `"phase": "clarify"`** → run in sequence:
-1. `morph-spec state mark-output $ARGUMENTS clarifications`
-2. `morph-spec phase advance $ARGUMENTS` (→ tasks)
+**If `"phase": "plan"`** → run:
+1. `morph-spec phase advance $ARGUMENTS` (→ tasks)
 
 **Any other value** → STOP — inconsistent state, report to user.
 
@@ -83,10 +82,10 @@ Check the `"phase"` field:
 
 ```
 # Single parallel call, not sequential:
-Read: .morph/features/{feature}/1-design/spec.md
-    + Read: .morph/features/{feature}/1-design/contracts.cs  (or contracts.ts for TypeScript projects)
-    + Read: .morph/features/{feature}/1-design/decisions.md
-    + Read: .morph/features/{feature}/1-design/schema-analysis.md  (if exists)
+Read: .morph/features/{feature}/2-design/spec.md
+    + Read: .morph/features/{feature}/2-design/contracts.cs  (or contracts.ts for TypeScript projects)
+    + Read: .morph/features/{feature}/2-design/decisions.md
+    + Read: .morph/features/{feature}/2-design/schema-analysis.md  (if exists)
     + Read: .morph/config/config.json                               (→ architecture.style)
 ```
 
@@ -116,25 +115,25 @@ morph-spec approval-status $ARGUMENTS
 
 ### Step 0: Detect Architecture Style
 
-Before anything else, determine if the project is VSA or DDD:
+Before anything else, determine the architecture style:
 
 ```bash
 cat .morph/config/config.json | grep -A3 '"architecture"'
 ```
 
-**If `config.architecture.style === "vertical-slice"`** → follow **Step 0.5 (VSA)** and skip DDD path.
-**Otherwise** → follow **Step 0.6 (DDD)** below.
+**If `config.architecture.style === "vertical-slice"`** → follow **Step 0.5 (VSA)**.
+**Otherwise** → proceed to **Step 1 (Analyze Spec)** with standard layer-based task breakdown.
 
 ---
 
 ### Step 0.5: VSA Task Plan
 
-> For VSA task patterns and DDD-level mappings, see `references/task-planning-patterns.md`
+> For VSA task patterns, see `references/task-planning-patterns.md`
 
 Read the `## Architecture Style: Vertical Slice` section from spec.md for the **VSA Blueprint**:
 
 ```bash
-grep -A30 "## Architecture Style" ".morph/features/$ARGUMENTS/1-design/spec.md"
+grep -A30 "## Architecture Style" ".morph/features/$ARGUMENTS/2-design/spec.md"
 ```
 
 Create one task per slice following this order: entity → errors → tags → migration → CRUD slices → custom slices → frontend → tests. Each slice = Handler + Validator + Endpoint in a **single task**. `GetAll` operations do NOT have a Validator (no input parameters to validate).
@@ -145,30 +144,13 @@ Use VSA-specific categories: `entity`, `errors`, `tags`, `migration`, `slice`, `
 
 ---
 
-### Step 0.6: Read Domain Level — DDD
-
-Read the `## Domain Complexity` section from spec.md:
-
-```bash
-grep -A15 "## Domain Complexity" ".morph/features/$ARGUMENTS/1-design/spec.md"
-```
-
-> If the section doesn't exist, assume **Level 1 (CRUD)**.
-
-Use the level to constrain categories:
-- **Level 1**: domain → infrastructure → application → presentation → tests
-- **Level 2**: adds AggregateRoot, ValueObjects, DomainEvents, CQRS handlers
-- **Level 3**: adds BC setup, Integration Events
-
-See `references/task-planning-patterns.md` for the complete table.
-
 ---
 
 ### Step 1: Analyze Spec
 
 > **VSA:** If coming from Step 0.5, the task breakdown was already defined — use the generated examples as a base and skip to Step 3 (Dependencies).
 
-Read `.morph/features/$ARGUMENTS/1-design/spec.md` and identify:
+Read `.morph/features/$ARGUMENTS/2-design/spec.md` and identify:
 
 1. **Functional requirements** (FR001, FR002, ...)
 2. **Technical components** (Entities, Services/Slices, Controllers/Endpoints, Pages)
@@ -274,7 +256,7 @@ Use `AskUserQuestion` to capture explicit approval before advancing. This gate p
 
 - [x] `tasks.md` created with all tasks
 - [x] Tasks use T### format (T001, T002, ...) consistently
-- [x] Tasks categorized correctly (DDD layers or VSA categories)
+- [x] Tasks categorized correctly (VSA categories or standard layers)
 - [x] Dependencies mapped
 - [x] Checkpoints defined (every 3 tasks)
 - [x] Effort estimated in minutes per task
@@ -298,10 +280,10 @@ Use `AskUserQuestion` to capture explicit approval before advancing. This gate p
 
 ## Phase Outputs
 
-<!-- morph-outputs:tasks -->
-| Output | Caminho |
-|--------|---------|
-| `tasks` | `.morph/features/{feature}/4-tasks/tasks.md` |
+<!-- morph-outputs:tasks -->
+| Output | Caminho |
+|--------|---------|
+| `tasks` | `.morph/features/{feature}/4-tasks/tasks.md` |
 <!-- /morph-outputs -->
 
 ---

package/framework/skills/level-1-workflows/morph-phase-tasks/references/task-planning-patterns.md

@@ -1,172 +1,143 @@
-# Task Planning Patterns — VSA e DDD
-
-> Padrões detalhados de task planning para VSA e DDD.
-> Referenciado pelos Passos 0.5 e 0.6 de `phase-tasks/SKILL.md`.
-
----
-
-## Padrão VSA (Vertical Slice Architecture)
-
-**Ref:** `framework/standards/architecture/vertical-slice/vertical-slice.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)
-
-### Exemplos de tasks VSA
-
-```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"
-  ] }
-```
-
----
-
-## Padrão DDD — Mapeamento de Níveis para Categorias
-
-**Ref:** `framework/standards/architecture/ddd/complexity-levels.md`
-
-### Categorias por nível de complexidade
-
-| Nível | Categorias de Tasks |
-|-------|---------------------|
-| **1 — CRUD** | `domain` (Entity simples) → `infrastructure` (Repository, EF Config) → `application` (Service CRUD) → `presentation` (API/Page) → `tests` |
-| **2 — Business Logic** | `domain` (AggregateRoot, ValueObjects, DomainEvents) → `infrastructure` (Repository, EF Config) → `application` (Commands, Queries, Handlers) → `presentation` (API/Page) → `tests` |
-| **3 — Bounded Context** | `domain-bc` (BC setup, Aggregates, Events) → `infrastructure` (BC repositories, EF) → `application` (Commands, Queries, Integration handlers) → `presentation` → `tests` |
-
-**Nível 1:** Nenhuma task adicional obrigatória — apenas o padrão CRUD nas categorias listadas.
-
-### Tasks adicionais obrigatórias por nível
-
-**Nível 2 apenas:**
-- `T{N}: Implementar AggregateRoot {EntityName} com factory method e invariants` (domain)
-- `T{N}: Implementar ValueObjects: {lista do Aggregate Blueprint}` (domain)
-- `T{N}: Implementar DomainEvents: {lista do Aggregate Blueprint}` (domain)
-- `T{N}: Implementar Command Handlers com MediatR` (application)
-- `T{N}: Implementar Query Handlers com read models` (application)
-
-**Nível 3 apenas (além do Nível 2):**
-- `T{N}: Configurar namespace/pasta do Bounded Context {BoundedContext}` (infrastructure)
-- `T{N}: Implementar Integration Events para comunicação cross-BC` (domain-bc)
-- `T{N}: Implementar handlers de Integration Events` (application)
-
----
-
-## Estrutura de Task (formato JSON)
-
-```json
-{
-  "id": "T001",
-  "title": "Criar Entity {Nome}",
-  "description": "Implementar entity {Nome} com propriedades X, Y, Z seguindo padrões EF Core",
-  "category": "domain",
-  "dependencies": [],
-  "estimatedMinutes": 30,
-  "status": "pending",
-  "specSections": ["## Domain Model", "## Business Rules"],
-  "contractInterfaces": ["I{Nome}Repository"],
-  "files": [
-    "Domain/Entities/{Nome}.cs",
-    "Infrastructure/Data/Configurations/{Nome}Configuration.cs"
-  ]
-}
-```
-
-## Categorias de Tasks (DDD)
-
-| Categoria | Descrição | Exemplos |
-|-----------|-----------|----------|
-| **domain** | Entities, Value Objects, Enums | Entity, DomainException |
-| **application** | Services, DTOs, Interfaces | Service, Validator, Mapper |
-| **infrastructure** | DbContext, Repositories, External APIs | EF Config, Repository impl |
-| **presentation** | Controllers, Pages, Components | API endpoint, Blazor page |
-| **tests** | Unit tests, Integration tests | Service tests, API tests |
-| **infra** | Bicep, Migrations, Scripts | Azure resources, DB migration |
-| **docs** | README, API docs, Swagger | OpenAPI spec, README update |
-
-## Ordem de Implementação Bottom-Up
-
-```
-1. Domain (Entities, Enums, Value Objects)
-   ↓
-2. Infrastructure (Repositories, DbContext configs)
-   ↓
-3. Application (Services, DTOs, Business logic)
-   ↓
-4. Presentation (Controllers, Pages, Components)
-   ↓
-5. Tests (Unit → Integration)
-   ↓
-6. Infra (Bicep, Migrations, Deploy scripts)
-   ↓
-7. Docs (README, Swagger, Comments)
-```
+# Task Planning Patterns — VSA
+
+> Padrões detalhados de task planning para Vertical Slice Architecture.
+> Referenciado pelos Passos 0.5 e 0.6 de `phase-tasks/SKILL.md`.
+
+---
+
+## Padrão VSA (Vertical Slice Architecture)
+
+**Ref:** `framework/standards/architecture/vertical-slice/vertical-slice.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)
+
+### Exemplos de tasks VSA
+
+```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"
+  ] }
+```
+
+---
+
+## Estrutura de Task (formato JSON)
+
+```json
+{
+  "id": "T001",
+  "title": "Criar Entity {Nome}",
+  "description": "Implementar entity {Nome} com propriedades X, Y, Z seguindo padrões EF Core",
+  "category": "entity",
+  "dependencies": [],
+  "estimatedMinutes": 30,
+  "status": "pending",
+  "specSections": ["## Domain Model", "## Business Rules"],
+  "contractInterfaces": ["I{Nome}Repository"],
+  "files": [
+    "Entities/{Nome}.cs",
+    "Database/ApplicationDbContext.cs"
+  ]
+}
+```
+
+## Categorias de Tasks (VSA)
+
+| Categoria | Descrição | Exemplos |
+|-----------|-----------|----------|
+| **entity** | Entities, Enums | Entity class, DbSet registration |
+| **errors** | Error factory classes | `{Entity}Errors.cs` |
+| **tags** | API endpoint tags | `ApiTags.cs` constants |
+| **migration** | DB migrations | EF migrations |
+| **slice** | Complete VSA slice | Handler + Validator + Endpoint |
+| **tests** | Unit tests, Integration tests | Handler tests, API tests |
+| **infra** | Docker, Migrations, Scripts | docker-compose, Supabase migrations |
+| **docs** | README, API docs | OpenAPI spec, README update |
+
+## Ordem de Implementação Bottom-Up (VSA)
+
+```
+1. Entity + DbContext registration
+   ↓
+2. Errors + ApiTags
+   ↓
+3. Migrations
+   ↓
+4. Slices (Handler + Validator + Endpoint per operation)
+   ↓
+5. Tests (Unit → Integration)
+   ↓
+6. Infra (Docker, Supabase migrations)
+   ↓
+7. Docs (README, Swagger)
+```

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

@@ -81,7 +81,7 @@ Add `ProcessingJob` to `AppDbContext`, configure via Fluent API (column lengths,
 - **Type:** Infrastructure
 - **Priority:** 1
 - **Estimate:** 45min
-- **Assigned:** azure-architect
+- **Assigned:** infra-architect
 - **Dependencies:** None
 
 **Description:**
@@ -154,11 +154,11 @@ Create two endpoints per spec.md:
 - **Type:** UI
 - **Priority:** 2
 - **Estimate:** 1h
-- **Assigned:** blazor-builder
+- **Assigned:** nextjs-expert
 - **Dependencies:** T007
 
 **Description:**
-Blazor Server page at `/upload`. File input with client-side validation (type + size before submit). Loading state during upload. Redirect to `/processing/{jobId}` on success. Error message display per spec wireframe.
+Frontend page at `/upload`. File input with client-side validation (type + size before submit). Loading state during upload. Redirect to `/processing/{jobId}` on success. Error message display per spec wireframe.
 
 **Deliverables:**
 - [ ] Create: `src/Web/Pages/Upload.razor`
@@ -170,11 +170,11 @@ Blazor Server page at `/upload`. File input with client-side validation (type +
 - **Type:** UI
 - **Priority:** 3
 - **Estimate:** 1h
-- **Assigned:** blazor-builder
+- **Assigned:** nextjs-expert
 - **Dependencies:** T007
 
 **Description:**
-Blazor Server page at `/processing/{jobId}`. Polls `GET /api/status/{jobId}` every 5 seconds using `PeriodicTimer`. Shows status label + progress indicator. "Download" button when Completed. "Retry" suggestion when Failed. Stops polling on terminal state.
+Frontend page at `/processing/{jobId}`. Polls `GET /api/status/{jobId}` every 5 seconds using `PeriodicTimer`. Shows status label + progress indicator. "Download" button when Completed. "Retry" suggestion when Failed. Stops polling on terminal state.
 
 **Deliverables:**
 - [ ] Create: `src/Web/Pages/ProcessingStatus.razor`