@polymorphism-tech/morph-spec 4.3.7 → 4.6.0

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

@@ -0,0 +1,254 @@
+---
+name: phase-implement
+description: MORPH-SPEC Phase 5 (Implement). Executes feature tasks using TDD with checkpoint validation every 3 tasks, smoke tests via Playwright, and generates code + recap.md. Use after task list approval when starting feature implementation.
+argument-hint: "[feature-name]"
+disable-model-invocation: true
+context: fork
+agent: general-purpose
+user-invocable: false
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# MORPH Implement - FASE 5
+
+> INTERNAL: Workflow skill used by /morph-apply during automated phase orchestration. Not a user command.
+
+Implemente as tasks definidas na FASE 4, com checkpoints a cada 3 tasks e recap final.
+
+## Pré-requisitos
+
+- [ ] FASE 4 (Tasks) concluída
+- [ ] `tasks.md` ou `tasks.json` aprovado pelo usuário
+- [ ] Tasks gate (`morph-spec approve $ARGUMENTS tasks`) aprovado
+- [ ] Todos os outputs de design existem (spec.md, contracts.cs, decisions.md)
+
+## Ferramentas Recomendadas
+
+> **Ref:** `framework/skills/level-0-meta/tool-usage-guide/SKILL.md` para guia completo.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` para referência MCP.
+> **Example:** `references/recap-example.md` — filled-in recap.md showing expected output quality.
+
+| Ação | Ferramenta | Alternativa |
+|------|------------|-------------|
+| Ler task details | **Read** tasks.json, spec.md, contracts.cs | — |
+| Criar novos arquivos | **Write** source files | — |
+| Modificar arquivos existentes | **Edit** source files | — |
+| Consultar API de biblioteca | **Context7 MCP** `query_docs()` | **WebSearch** + **WebFetch** |
+| Executar migrations | **Supabase MCP** `query()` | **Bash** `npx supabase migration ...` |
+| Build do projeto | **Bash** `dotnet build` ou `npm run build` | — |
+| Rodar testes | **Bash** `dotnet test` ou `npm test` | — |
+| Checkpoint validation | **Bash** `npx morph-spec validate-feature ...` | — |
+| Marcar task concluída | **Bash** `npx morph-spec task done $ARGUMENTS T001` | — |
+| Smoke test no browser | **Playwright MCP** `browser_navigate()` + `browser_snapshot()` | Manual |
+| Verificar erros de console | **Playwright MCP** `browser_console_messages()` | — |
+| Screenshot para recap | **Playwright MCP** `browser_take_screenshot()` | — |
+| Criar PR | **Bash** `gh pr create ...` | **GitHub MCP** `create_pull_request()` |
+| Atualizar state | **Bash** `npx morph-spec state set ...` | — |
+
+**MCPs desta fase:** Supabase (migrations, RLS), Context7 (API lookup), Playwright (smoke test), GitHub (PRs).
+
+**Anti-padrões:**
+- ❌ Task agent para editar um único arquivo (use Edit direto)
+- ✅ Task agent para implementar service layer em 5+ arquivos (multi-file legítimo)
+- ❌ Bash `cat` para criar arquivos (use Write tool)
+- ❌ Bash `sed` para modificar código (use Edit tool)
+- ❌ Implementar sem ler contracts.cs primeiro (contracts são a fonte de verdade!)
+
+---
+
+## Workflow
+
+### CHECKPOINT DE ENTRADA: Verificar Pré-requisitos
+
+**⏸️ Antes de iniciar implementação:**
+
+- [ ] `tasks.md` ou `tasks.json` existe e foi aprovado?
+- [ ] Tasks gate aprovado (`morph-spec approve $ARGUMENTS tasks`)?
+- [ ] `spec.md` atualizado com clarificações?
+- [ ] `contracts.cs` corresponde ao schema real?
+- [ ] Build base do projeto compila sem erros?
+
+```bash
+npx morph-spec state get $ARGUMENTS
+npx morph-spec approval-status $ARGUMENTS
+```
+
+**❌ Se alguma checkbox NÃO estiver marcada:**
+→ Voltar para a fase correspondente
+
+---
+
+### Passo 1: Carregar Contexto Completo
+
+Leia TODOS os outputs antes de implementar:
+
+1. `.morph/features/$ARGUMENTS/3-tasks/tasks.md` — Lista de tasks
+2. `.morph/features/$ARGUMENTS/1-design/spec.md` — Especificação completa
+3. `.morph/features/$ARGUMENTS/1-design/contracts.cs` — Interfaces e DTOs
+4. `.morph/features/$ARGUMENTS/1-design/decisions.md` — ADRs
+5. `.morph/features/$ARGUMENTS/1-design/schema-analysis.md` — Schema real (se existir)
+6. `.morph/features/$ARGUMENTS/2-ui/design-system.md` — Design tokens (se existir)
+
+### Passo 2: Iniciar Primeira Task
+
+```bash
+npx morph-spec task next $ARGUMENTS
+npx morph-spec task start $ARGUMENTS T001
+```
+
+Para cada task:
+
+1. **Ler a task description** completa
+2. **Ler contracts.cs** para DTOs/interfaces relevantes
+3. **Implementar** usando Write (novo) ou Edit (existente)
+4. **Verificar** — build, lint, testes
+5. **Marcar como done:**
+```bash
+npx morph-spec task done $ARGUMENTS T001
+```
+
+### Passo 3: Checkpoint a Cada 3 Tasks
+
+**A cada 3 tasks completadas:**
+
+```bash
+# Save checkpoint
+npx morph-spec checkpoint-save $ARGUMENTS
+
+# Run validation
+npx morph-spec validate-feature $ARGUMENTS --phase implement
+```
+
+**Se validação falhar:**
+1. NÃO avançar para próxima task
+2. Corrigir issues reportados
+3. Re-rodar validação
+4. Só então prosseguir
+
+### Passo 4: Test-Driven Development (Recomendado)
+
+Para cada task de implementação:
+
+1. **Escrever teste primeiro** (unit test para service/domain)
+2. **Rodar teste** — deve falhar (RED)
+3. **Implementar** o mínimo para passar
+4. **Rodar teste** — deve passar (GREEN)
+5. **Refatorar** se necessário (REFACTOR)
+
+```bash
+# .NET
+dotnet test --filter "FullyQualifiedName~{TestClass}"
+
+# Node.js
+npm test -- test/path/to/test.js
+```
+
+### Passo 5: Smoke Test com Playwright (se UI)
+
+Após implementar componentes visuais:
+
+```javascript
+// Navegar para a página
+await mcp__playwright__browser_navigate({ url: 'http://localhost:5000/feature-page' });
+
+// Capturar estado da página
+await mcp__playwright__browser_snapshot();
+
+// Verificar erros de console
+await mcp__playwright__browser_console_messages({ level: 'error' });
+
+// Screenshot para recap
+await mcp__playwright__browser_take_screenshot({ type: 'png' });
+```
+
+### Passo 6: Gerar `recap.md`
+
+Após TODAS as tasks completadas:
+
+```bash
+npx morph-spec generate recap $ARGUMENTS
+```
+
+Ou crie manualmente `.morph/features/$ARGUMENTS/4-implement/recap.md`:
+
+```markdown
+# Recap — {Feature Name}
+
+## Summary
+{1-2 parágrafos descrevendo o que foi implementado}
+
+## Tasks Completed
+- [x] T001: {título}
+- [x] T002: {título}
+- ...
+
+## Key Decisions During Implementation
+- {Decisão 1}: {Razão}
+- {Decisão 2}: {Razão}
+
+## Files Created/Modified
+{Lista de arquivos}
+
+## Tests
+- Unit tests: X passing
+- Integration tests: Y passing
+
+## Validation Results
+{Output do morph-spec validate-feature}
+
+## Screenshots
+{Se UI, incluir screenshots}
+```
+
+### Passo 7: Atualizar State
+
+```bash
+npx morph-spec state set $ARGUMENTS phase implement
+npx morph-spec state set $ARGUMENTS status done
+npx morph-spec state mark-output $ARGUMENTS recap
+```
+
+---
+
+## Integração com Superpowers
+
+> Disponível quando o plugin `superpowers` está instalado.
+
+| Skill | Quando Usar | Invocação |
+|-------|-------------|-----------|
+| `test-driven-development` | Para cada task de implementação | `Skill(superpowers:test-driven-development)` |
+| `systematic-debugging` | Quando testes falham ou erros inesperados | `Skill(superpowers:systematic-debugging)` |
+| `requesting-code-review` | Após implementação completa | `Skill(superpowers:requesting-code-review)` |
+| `verification-before-completion` | Antes de marcar feature como done | Use `verification-before-completion` (morph-spec version) |
+
+---
+
+## Outputs Gerados
+
+- Código fonte implementado (vários arquivos)
+- Testes unitários e de integração
+- `.morph/features/$ARGUMENTS/4-implement/recap.md` — Resumo da implementação
+
+## Critérios de Conclusão
+
+- [x] Todas as tasks completadas
+- [x] Build compila sem erros
+- [x] Testes passando
+- [x] Validation pipeline passa
+- [x] `recap.md` gerado
+- [x] State atualizado para `status: done`
+- [x] Checkpoints salvos a cada 3 tasks
+
+---
+
+## Outputs desta Fase
+
+<!-- morph:outputs:implement -->
+| Output | Caminho |
+|--------|---------|
+| `recap` | `.morph/features/{feature}/4-implement/recap.md` |
+<!-- /morph:outputs -->
+
+---
+
+Feature completa! Considere criar um PR e rodar `morph-spec session-summary $ARGUMENTS`.

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

@@ -0,0 +1,132 @@
+# Feature Recap: Photo Processing Pipeline
+
+> Example of a well-structured recap.md. Filled-in reference — not a template.
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Feature ID** | photo-processing |
+| **Completed** | 2025-01-22 |
+| **Total Tasks** | 11 / 11 |
+| **Time Spent** | ~9h |
+| **Agents Used** | dotnet-senior, azure-architect, blazor-builder |
+| **Stack** | blazor-azure |
+
+---
+
+## Tasks Completed
+
+| ID | Title | Category | Duration |
+|----|-------|----------|----------|
+| T001 | Define C# contracts and interfaces | Contract | 25min |
+| T002 | Create ProcessingJob entity and enum | Domain | 30min |
+| T003 | EF Core migration and DbContext setup | Infrastructure | 50min |
+| T004 | Azure Blob Storage service | Infrastructure | 45min |
+| T005 | Implement PhotoProcessingService | Service | 65min |
+| T006 | Implement Hangfire background job | Job | 70min |
+| T007 | Upload and status endpoints | API | 40min |
+| T008 | Blazor upload page component | UI | 60min |
+| T009 | Blazor status polling page | UI | 65min |
+| T010 | Unit tests for PhotoProcessingService | Test | 55min |
+| T011 | Integration tests for upload + status API | Test | 70min |
+
+---
+
+## What Was Delivered
+
+### Functionality
+- Photo upload via Blazor form (10MB limit, .jpg/.png only)
+- Azure Blob Storage integration with `uploads/{jobId}/original.jpg` path structure
+- Hangfire background job with 3-retry exponential backoff (5s/30s/120s)
+- Real-time status polling page (5s interval, stops on terminal state)
+- Download redirect for completed jobs
+
+### Backend (.NET)
+- Endpoints: `POST /api/upload`, `GET /api/status/{id}`, `GET /api/download/{id}`
+- Services: `PhotoProcessingService`, `PhotoProcessingJob`
+- Simulation: `FakeBlobStorageService`, `FakePhotoProcessingJob` for dev mode
+
+### Frontend (Blazor)
+- Pages: `Upload.razor`, `ProcessingStatus.razor`
+- Polling via `PeriodicTimer` — no SignalR dependency
+
+---
+
+## Files Created
+
+```
+src/Domain/Entities/ProcessingJob.cs
+src/Domain/Enums/ProcessingStatus.cs
+src/Application/PhotoProcessing/Interfaces/IPhotoProcessingService.cs
+src/Application/PhotoProcessing/Commands/UploadPhotoCommand.cs
+src/Application/PhotoProcessing/Queries/GetJobStatusQuery.cs
+src/Application/PhotoProcessing/DTOs/JobStatusDto.cs
+src/Application/PhotoProcessing/PhotoProcessingService.cs
+src/Application/PhotoProcessing/PhotoProcessingJob.cs
+src/Application/PhotoProcessing/FakePhotoProcessingJob.cs
+src/Infrastructure/Storage/IBlobStorageService.cs
+src/Infrastructure/Storage/AzureBlobStorageService.cs
+src/Infrastructure/Storage/FakeBlobStorageService.cs
+src/Infrastructure/Persistence/Configurations/ProcessingJobConfiguration.cs
+src/Web/Endpoints/PhotoProcessingEndpoints.cs
+src/Web/Pages/Upload.razor + .cs
+src/Web/Pages/ProcessingStatus.razor + .cs
+tests/Unit/Application/PhotoProcessing/PhotoProcessingServiceTests.cs
+tests/Integration/Api/PhotoProcessingEndpointTests.cs
+tests/Integration/Fixtures/PhotoProcessingApiFixture.cs
+```
+
+## Files Modified
+
+```
+src/Infrastructure/Persistence/AppDbContext.cs
+src/Infrastructure/DependencyInjection.cs
+src/Application/DependencyInjection.cs
+src/Web/Program.cs
+```
+
+---
+
+## Architecture Decisions
+
+| Decision | Rationale |
+|----------|-----------|
+| PeriodicTimer for polling (not SignalR) | Simpler, no hub overhead, sufficient at MVP scale |
+| FakeBlobStorageService as Singleton | Stores in-memory dict; Scoped would lose state between requests |
+| Hangfire RetryCount on entity (not Hangfire built-in) | Domain owns retry state; allows custom error messages per attempt |
+
+See full ADRs in `decisions.md`
+
+---
+
+## Test Coverage
+
+| Type | Files | Notes |
+|------|-------|-------|
+| Unit | `PhotoProcessingServiceTests.cs` | Happy path, invalid type, size limit, 404, all statuses |
+| Integration | `PhotoProcessingEndpointTests.cs` | POST /upload, GET /status, GET /download (completed + pending) |
+
+---
+
+## Issues Encountered
+
+| Issue | Resolution |
+|-------|-----------|
+| `FakeBlobStorageService` registered as `Scoped` — lost uploads between requests | Changed to `Singleton` per simulation-checklist.md |
+| `PeriodicTimer` not stopping on component dispose | Added `CancellationTokenSource` + dispose pattern in `ProcessingStatus.razor.cs` |
+
+---
+
+## Metrics
+
+| Metric | Value |
+|--------|-------|
+| Tasks Completed | 11 / 11 |
+| Checkpoints Passed | 3 (after T003, T006, T009) |
+| Bugs Found | 2 |
+| Bugs Fixed | 2 |
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -0,0 +1,171 @@
+---
+name: phase-setup
+description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech stack, activates relevant agents via detect-agents, and confirms the feature environment. Use at the start of every MORPH-SPEC feature workflow after proposal approval to load standards and initialize the context.
+argument-hint: "[feature-name]"
+user-invocable: false
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# MORPH Setup - FASE 1
+
+> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+
+Inicialize o contexto e prepare o ambiente para uma feature aprovada.
+
+## Pré-requisitos
+
+- [ ] Feature tem `proposal.md` criado (FASE 0 concluída)
+- [ ] Proposal foi aprovado pelo usuário
+- [ ] Agentes foram detectados e registrados no state
+
+## Ferramentas Recomendadas
+
+> **Ref:** `framework/skills/level-0-meta/tool-usage-guide/SKILL.md` para guia completo.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` para referência MCP.
+
+| Ação | Ferramenta | Alternativa |
+|------|------------|-------------|
+| Verificar state | **Bash** `npx morph-spec state get` | — |
+| Detectar agentes + standards | **Bash** `npx morph-spec detect-agents --json` | — |
+| Ler contexto do projeto | **Read** `.morph/context/README.md` | — |
+| Ler config | **Read** `.morph/config.json` | — |
+| Escanear estrutura do projeto | **Glob** `src/**/*.{ts,tsx,cs}` | — |
+| Metadata do repositório | **GitHub MCP** `get_repo()` | **Bash** `gh repo view --json` |
+| Atualizar state | **Bash** `npx morph-spec state set` | — |
+
+**MCPs desta fase:** GitHub (opcional — metadata do repo).
+
+**Anti-padrões:**
+- ❌ Task agent para detectar stack (detect-agents CLI já faz isso)
+- ❌ WebSearch para info local do projeto (use Read/Glob)
+- ❌ Ler agents.json manualmente (detect-agents retorna standards processados)
+
+---
+
+## Workflow
+
+### CHECKPOINT DE ENTRADA: Verificar Pré-requisitos
+
+**⏸️ Antes de prosseguir com setup:**
+
+- [ ] `proposal.md` existe em `.morph/features/$ARGUMENTS/`?
+- [ ] Proposal foi apresentado e aprovado pelo usuário?
+- [ ] Feature foi registrada no state?
+
+**❌ Se alguma checkbox NÃO estiver marcada:**
+→ Voltar para FASE 0 (Proposal)
+
+---
+
+### Passo 1: Verificar State
+
+Confirme que a feature existe no state:
+
+```bash
+npx morph-spec state get $ARGUMENTS
+```
+
+Se não existir, volte para FASE 0 (proposal).
+
+### Passo 2: Carregar Contexto e Standards Automaticamente
+
+**Use detect-agents --json para obter standards context:**
+
+```bash
+npx morph-spec detect-agents --json "{feature description from proposal}"
+```
+
+O output JSON contém `standardsSummary` com todos os standards relevantes para cada agente ativo:
+
+```json
+{
+  "standardsSummary": {
+    "blazor-builder": {
+      "standards": ["blazor-lifecycle", "blazor-state", "coding", ...],
+      "fullContent": "# blazor-lifecycle\n\n...",  // Full standards text
+      "count": 10
+    }
+  }
+}
+```
+
+**Standards resolution order** (automático):
+1. `.morph/context/*.md` (project overrides - highest priority)
+2. `.morph/framework/standards/*.md` (AI Agent Framework, Azure)
+3. `framework/standards/*.md` (Blazor, CSS, .NET)
+4. `.morph/context/inferred.md` (always loaded if exists)
+
+**Contexto geral** (leia manualmente):
+- `.morph/context/README.md` - Overview do projeto
+- `.morph/config.json` - Configurações
+
+### Passo 3: Confirmar Stack
+
+Baseado no proposal e contexto, confirme:
+- Stack tecnológica (Blazor Server, Next.js, etc.)
+- Padrões arquiteturais aplicáveis
+- Componentes reutilizáveis existentes
+
+### Passo 4: Listar Agentes Ativos
+
+Mostre os agentes detectados no proposal:
+
+```bash
+npx morph-spec state get $ARGUMENTS
+```
+
+Parse o JSON e liste os `activeAgents` com seus emojis e responsabilidades (consulte `.morph/framework/agents.json`).
+
+### Passo 5: Atualizar State
+
+Marque a feature como na fase SETUP:
+
+```bash
+npx morph-spec state set $ARGUMENTS phase setup
+npx morph-spec state set $ARGUMENTS status in_progress
+```
+
+## Outputs
+
+**Apresente ao usuário:**
+
+1. **Contexto carregado**:
+   - Nome do projeto
+   - Stack confirmado
+   - Standards aplicáveis
+
+2. **Agentes ativos**:
+   - Lista de agentes com emojis
+   - Responsabilidades de cada um
+
+## Critérios de Avanço
+
+- [x] Contexto do projeto carregado
+- [x] Standards identificados (framework + project)
+- [x] Stack confirmado
+- [x] Agentes listados
+- [x] State atualizado para phase: setup
+
+---
+
+## Integração com Superpowers
+
+> Disponível quando o plugin `superpowers` está instalado.
+
+| Skill | Quando Usar | Invocação |
+|-------|-------------|-----------|
+| `using-git-worktrees` | Se feature requer isolamento do workspace | `Skill(superpowers:using-git-worktrees)` |
+
+---
+
+## Outputs desta Fase
+
+<!-- morph:outputs:proposal -->
+| Output | Caminho |
+|--------|---------|
+| `proposal` | `.morph/features/{feature}/0-proposal/proposal.md` |
+<!-- /morph:outputs -->
+
+---
+
+Continuar automaticamente para próxima fase (UI/UX se detectado, ou Design).

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

@@ -1,3 +1,12 @@
+---
+name: phase-tasks
+description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ordered implementation tasks (T001...TXXX) with dependencies, checkpoints every 3 tasks, and effort estimates, producing tasks.md. Use after design and clarification phases to create a structured implementation plan before coding starts.
+argument-hint: "[feature-name]"
+disable-model-invocation: true
+user-invocable: false
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
 # MORPH Tasks - FASE 4
 
 > INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
@@ -10,11 +19,63 @@ Quebre a especificação em tasks executáveis, defina ordem de execução e est
 - [ ] `spec.md` atualizado com clarificações
 - [ ] Todos os edge cases documentados
 
+## Ferramentas Recomendadas
+
+> **Ref:** `framework/skills/level-0-meta/tool-usage-guide/SKILL.md` para guia completo.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` para referência MCP.
+> **Example:** `references/tasks-example.md` — filled-in tasks.md showing expected granularity and format.
+> **Script:** `scripts/validate-tasks.mjs` — validates tasks.md structure, T### IDs, and required fields.
+
+| Ação | Ferramenta | Alternativa |
+|------|------------|-------------|
+| Ler spec + contracts + decisions | **Read** todos os outputs | — |
+| Analisar complexidade de implementação | **Grep** padrões no código existente | — |
+| Contar padrões similares existentes | **Glob** `**/Services/**/*.cs` | — |
+| Consultar padrões de implementação | **Context7 MCP** `query_docs()` | **WebSearch** |
+| Criar issues no GitHub a partir das tasks | **GitHub MCP** `create_issue()` | **Bash** `gh issue create ...` |
+| Renderizar template de tasks | **Bash** `npx morph-spec template render docs/tasks ...` | — |
+| Atualizar state com total de tasks | **Bash** `npx morph-spec state set ... tasks.total N` | — |
+
+**MCPs desta fase:** Context7 (estimar complexidade), GitHub (criar issues).
+
+**Anti-padrões:**
+- ❌ Task agent para quebrar spec simples (faça diretamente)
+- ✅ Task agent para specs complexos com 50+ requisitos (análise legítima multi-step)
+- ❌ Criar tasks.json sem ler todos os outputs primeiro
+
+---
+
 ## Workflow
 
+### CHECKPOINT DE ENTRADA: Verificar Pré-requisitos
+
+**⏸️ PAUSE - Antes de iniciar o breakdown de tasks:**
+
+- [ ] `spec.md` existe e foi aprovado pelo usuário?
+- [ ] `contracts.cs` existe e corresponde ao schema real?
+- [ ] `schema-analysis.md` foi validado (se aplicável)?
+- [ ] `decisions.md` contém ADRs para todas as escolhas críticas?
+- [ ] Design gate (`morph-spec approve $ARGUMENTS design`) foi aprovado?
+- [ ] Clarificações (FASE 3) foram resolvidas e spec atualizado?
+
+**❌ Se alguma checkbox NÃO estiver marcada:**
+→ Voltar para a fase correspondente e resolver
+
+**✅ Se TODAS as checkboxes estiverem marcadas:**
+→ Prosseguir para análise e breakdown
+
+```bash
+# Verificar estado atual:
+npx morph-spec state get $ARGUMENTS
+# Verificar se design foi aprovado:
+npx morph-spec approval get $ARGUMENTS design
+```
+
+---
+
 ### Passo 1: Analisar Spec
 
-Leia `.morph/project/outputs/{feature}/spec.md` e identifique:
+Leia `.morph/features/$ARGUMENTS/1-design/spec.md` e identifique:
 
 1. **Requisitos funcionais** (FR001, FR002, ...)
 2. **Componentes técnicos** (Entities, Services, Controllers, Pages)
@@ -121,7 +182,7 @@ Para cada task, estime tempo em minutos:
 
 ### Passo 6: Gerar `tasks.json`
 
-Crie `.morph/project/outputs/{feature}/tasks.json` com a estrutura completa de tasks, checkpoints e estimativas.
+Crie `.morph/features/$ARGUMENTS/3-tasks/tasks.md` com a estrutura completa de tasks, checkpoints e estimativas.
 
 ### Passo 7: Incluir Tasks de IaC (se necessário)
 
@@ -130,14 +191,14 @@ Se houver recursos Azure, adicionar tasks de Bicep e migrations.
 ### Passo 8: Atualizar State
 
 ```bash
-npx morph-spec state set {feature-name} phase tasks
-npx morph-spec state set {feature-name} tasks.total {N}
-npx morph-spec state mark-output {feature-name} tasks
+npx morph-spec state set $ARGUMENTS phase tasks
+npx morph-spec state set $ARGUMENTS tasks.total {N}
+npx morph-spec state mark-output $ARGUMENTS tasks
 ```
 
 ## Outputs Gerados
 
-- `.morph/project/outputs/{feature}/tasks.json` - Breakdown completo de tasks
+- `.morph/features/$ARGUMENTS/3-tasks/tasks.md` - Breakdown completo de tasks
 
 ## PAUSA OBRIGATÓRIA
 
@@ -161,4 +222,25 @@ Apresente ao usuário 3 ações sugeridas:
 
 ---
 
-Após aprovação: "Planejamento completo! Execute `/morph-apply {feature}` para iniciar implementação."
+## Integração com Superpowers
+
+> Disponível quando o plugin `superpowers` está instalado.
+
+| Skill | Quando Usar | Invocação |
+|-------|-------------|-----------|
+| `writing-plans` | Após breakdown de tasks, para planejar sequência de implementação | `Skill(superpowers:writing-plans)` |
+| `executing-plans` | Para executar o plano de tasks em sessão separada | `Skill(superpowers:executing-plans)` |
+
+---
+
+## Outputs desta Fase
+
+<!-- morph:outputs:tasks -->
+| Output | Caminho |
+|--------|---------|
+| `tasks` | `.morph/features/{feature}/3-tasks/tasks.md` |
+<!-- /morph:outputs -->
+
+---
+
+Após aprovação: "Planejamento completo! Execute `/morph-apply $ARGUMENTS` para iniciar implementação."