@polymorphism-tech/morph-spec 4.10.0 → 4.10.2

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

@@ -3,236 +3,236 @@ name: morph:phase-setup
 description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech stack, activates relevant agents by reading agents.json, 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
-cliVersion: "4.10.0"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+cliVersion: "4.10.2"
 ---
 
-# MORPH Setup - FASE 1
+# MORPH Setup — Phase 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.
+Initialize the context and prepare the environment for an approved feature.
 
-## Pré-requisitos
+## Prerequisites
 
-- [ ] Feature tem `proposal.md` criado (FASE 0 concluída)
-- [ ] Proposal foi aprovado pelo usuário
-- [ ] Agentes foram detectados e registrados no state
+- [ ] Feature has `proposal.md` created (Phase 0 complete)
+- [ ] Proposal was approved by the user
+- [ ] Agents were detected and registered in state
 
-## Ferramentas Recomendadas
+## Recommended Tools
 
-> **Ref:** `framework/skills/level-0-meta/morph-tool-usage-guide/SKILL.md` para guia completo.
-> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` para referência MCP.
+> **Ref:** `framework/skills/level-0-meta/morph-tool-usage-guide/SKILL.md` for full guide.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` for MCP reference.
 
-| Ação | Ferramenta | Alternativa |
-|------|------------|-------------|
-| Verificar state | **Bash** `npx morph-spec state get` | — |
-| Detectar agentes + standards | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent` | — |
-| Ler contexto do projeto | **Read** `.morph/context/README.md` | — |
-| Ler config | **Read** `.morph/config/config.json` | — |
-| Detectar arquitetura VSA | **Read** `.morph/config/config.json` → verificar `config.architecture.style` | — |
-| 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` | — |
+| Action | Tool | Alternative |
+|--------|------|-------------|
+| Verify state | **Bash** `npx morph-spec state get` | — |
+| Detect agents + standards | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent` | — |
+| Read project context | **Read** `.morph/context/README.md` | — |
+| Read config | **Read** `.morph/config/config.json` | — |
+| Detect VSA architecture | **Read** `.morph/config/config.json` → check `config.architecture.style` | — |
+| Scan project structure | **Glob** `src/**/*.{ts,tsx,cs}` | — |
+| Repository metadata | **GitHub MCP** `get_repo()` | **Bash** `gh repo view --json` |
+| Update state | **Bash** `npx morph-spec state set` | — |
 
-**MCPs desta fase:** GitHub (opcional — metadata do repo).
+**MCPs for this phase:** GitHub (optional — repo metadata).
 
-**Anti-padrões:**
-- ❌ Chamar `detect-agents` CLI (não existe — leia `.morph/framework/agents.json` diretamente)
-- ❌ Task agent para o keyword matching inline de stack detection (rápido o suficiente direto)
-- ❌ WebSearch para info local do projeto (use Read/Glob)
+**Anti-patterns:**
+- Do not call a `detect-agents` CLI command (it doesn't exist — read `.morph/framework/agents.json` directly)
+- Do not use a Task agent for inline keyword matching (fast enough to do directly)
+- Do not use WebSearch for local project info (use Read/Glob)
 
 ---
 
 ## Workflow
 
-### CHECKPOINT DE ENTRADA: Verificar Pré-requisitos
+### ENTRY CHECKPOINT: Verify Prerequisites
 
-**⏸️ Antes de prosseguir com setup:**
+Before proceeding with setup:
 
-- [ ] `proposal.md` existe em `.morph/features/$ARGUMENTS/`?
-- [ ] Proposal foi apresentado e aprovado pelo usuário?
-- [ ] Feature foi registrada no state?
+- [ ] Does `proposal.md` exist in `.morph/features/$ARGUMENTS/0-proposal/`?
+- [ ] Was the proposal presented and approved by the user?
+- [ ] Is the feature registered in state?
 
-**❌ Se alguma checkbox NÃO estiver marcada:**
-→ Voltar para FASE 0 (Proposal)
+If any checkbox is NOT checked → go back to Phase 0 (Proposal).
 
 ---
 
-### Passo 1: Verificar State
+### Step 1: Load Project Context
 
-Confirme que a feature existe no state:
+Read these files first — they inform all subsequent decisions:
 
 ```bash
 npx morph-spec state get $ARGUMENTS
 ```
 
-Se não existir, volte para FASE 0 (proposal).
+If the feature doesn't exist in state, go back to Phase 0.
 
-### Passo 2: Detectar Agentes e Carregar Standards
+Then read:
+- `.morph/context/README.md` — project overview, tech stack, architecture
+- `.morph/config/config.json` — project configuration
 
-#### Passo 2.0: Detectar Estilo de Arquitetura e Ativar Arquiteto
+### Step 2: Detect Agents and Load Standards
 
-**Leia `.morph/config/config.json` e verifique `config.architecture.style`:**
+#### Step 2.0: Detect Architecture Style and Activate Architect
 
-| Valor | Ação |
-|-------|------|
+Read `.morph/config/config.json` and check `config.architecture.style`:
+
+| Value | Action |
+|-------|--------|
 | `"vertical-slice"` | `npx morph-spec state add-agent $ARGUMENTS vsa-architect` |
-| ausente / qualquer outro | `npx morph-spec state add-agent $ARGUMENTS domain-architect` |
+| absent / any other value | `npx morph-spec state add-agent $ARGUMENTS domain-architect` |
 
-**Prossiga com keyword detection normal para os demais agentes** (ef-modeler, api-designer, etc.).
-O arquiteto já foi adicionado acima — **ignore-o no keyword matching** para evitar duplicação.
+Proceed with normal keyword detection for all other agents. The architect was already added above — skip it during keyword matching to avoid duplication.
 
-#### Passo 2.1: Keyword Detection
+#### Step 2.1: Keyword Detection
 
-**Leia agents.json diretamente e faça o match de keywords** (exceto `domain-architect` e `vsa-architect` que já foram tratados no Passo 2.0):
+Read agents.json and match keywords (except `domain-architect` and `vsa-architect` which were handled in Step 2.0):
 
-1. Leia `.morph/framework/agents.json`
-2. Extraia título e descrição da feature de `0-proposal/proposal.md`
-3. Para cada agente no JSON (exceto arquitetos), verifique se alguma keyword do campo `keywords[]` aparece no texto da proposta
-4. Adicione os agentes correspondentes ao state:
+1. Read `.morph/framework/agents.json` (or `framework/agents.json` in the framework project itself)
+2. Extract the feature title and description from `0-proposal/proposal.md`
+3. For each agent in the JSON (except architects), check if any keyword from the `keywords[]` field appears in the proposal text
+4. Include all agents with `always_active: true` automatically
+5. Add matched agents to state:
 
 ```bash
 npx morph-spec state add-agent $ARGUMENTS {agent-id}
-# Exemplo:
-npx morph-spec state add-agent $ARGUMENTS dotnet-senior
-npx morph-spec state add-agent $ARGUMENTS ef-modeler
 ```
 
-**Para carregar standards dos agentes detectados:**
-- Para cada agente ativo, leia os standards referenciados pelo campo `standards[]` em `agents.json`
-- Os arquivos de standard ficam em `.morph/framework/standards/{path}`
-
-**Standards resolution order** (manual):
-1. `.morph/context/*.md` — project overrides (maior prioridade)
-2. `.morph/framework/standards/` — standards instalados pelo morph-spec
-3. `framework/standards/` — standards do pacote npm (fallback)
+**To load standards for detected agents:**
+- For each active agent, read the standards referenced by the `standards[]` field in `agents.json`
+- Standard files are located at `.morph/framework/standards/{path}`
 
-**Contexto geral** (leia sempre):
-- `.morph/context/README.md` — Overview do projeto
-- `.morph/config/config.json` — Configurações
+**Standards resolution order:**
+1. `.morph/context/*.md` — project overrides (highest priority)
+2. `.morph/framework/standards/` — standards installed by morph-spec
+3. `framework/standards/` — npm package standards (fallback)
 
-### Passo 2.5: Validar Conexoes MCP
+### Step 2.5: Validate MCP Connections
 
-Verifique se os MCPs configurados estao funcionando antes de prosseguir.
+Check that configured MCPs are working before proceeding.
 
-**1. Coletar MCPs recomendados:**
-- Leia `framework/phases.json` → para cada fase no workflow da feature, colete os `recommendedMCPs[]`
-- Leia `framework/skills/level-0-meta/mcp-registry.json` → obtenha os `healthCheck` de cada MCP
+**1. Collect recommended MCPs:**
+- Read `framework/phases.json` → for each phase in the feature's workflow, collect `recommendedMCPs[]`
+- Read `framework/skills/level-0-meta/mcp-registry.json` → get `healthCheck` for each MCP
 
-**2. Identificar MCPs configurados:**
-- Leia `.claude/settings.local.json` → identifique quais MCPs estao em `mcpServers`
+**2. Identify configured MCPs:**
+- Read `.claude/settings.local.json` → identify which MCPs are in `mcpServers`
 
-**3. Para cada MCP que esta CONFIGURADO E RECOMENDADO:**
-1. Procure nas suas ferramentas disponiveis por uma que contenha `healthCheck.toolPattern` no nome
-2. Se a ferramenta existir → execute o `healthCheck.testCall` com `healthCheck.testParams`
-3. Avalie o resultado:
+**3. For each MCP that is CONFIGURED AND RECOMMENDED:**
+1. Search your available tools for one containing `healthCheck.toolPattern` in the name
+2. If the tool exists → execute the `healthCheck.testCall` with `healthCheck.testParams`
+3. Evaluate the result:
 
-| Resultado | Acao |
-|-----------|------|
-| **Sucesso** | `✓ {MCP} — conexao verificada` |
-| **Ferramenta nao encontrada** | `○ {MCP} — precisa restart para ativar` |
-| **Erro** | → **AskUserQuestion** com 3 opcoes (abaixo) |
+| Result | Action |
+|--------|--------|
+| **Success** | `✓ {MCP} — connection verified` |
+| **Tool not found** | `○ {MCP} — needs restart to activate` |
+| **Error** | → Use `AskUserQuestion` with 3 options (below) |
 
-**Em caso de erro — pergunte ao usuario:**
+**On error — ask the user:**
 
-Use `AskUserQuestion` com header `"{MCP}"` e opcoes:
-- **Continuar sem {MCP}** — Mostre o campo `fallback` do registry e prossiga
-- **Reconfigurar credenciais** — Colete novas credenciais e atualize `.claude/settings.local.json`
-- **Parar setup** — Aborte e reporte o que precisa ser corrigido
+Use `AskUserQuestion` with header `"{MCP}"` and options:
+- **Continue without {MCP}** — show the `fallback` field from the registry and proceed
+- **Reconfigure credentials** — collect new credentials and update `.claude/settings.local.json`
+- **Stop setup** — abort and report what needs to be fixed
 
-**4. Para MCPs RECOMENDADOS mas NAO CONFIGURADOS:**
-- Print `△ {MCP} — nao configurado (fallback: {registry.fallback})`
-- Sugestao: `Tip: configure com /morph:init refresh ou npx morph-spec mcp setup`
+**4. For MCPs RECOMMENDED but NOT CONFIGURED:**
+- Print `△ {MCP} — not configured (fallback: {registry.fallback})`
+- Suggestion: `Tip: configure with /morph:init refresh or npx morph-spec mcp setup`
 
-**Resumo:** Mostre uma tabela com status de cada MCP antes de prosseguir:
+**Summary:** Show a status table for each MCP before proceeding:
 ```
 MCP Readiness:
-  ✓ context7 — conexao verificada
-  ○ playwright — precisa restart
-  △ supabase — nao configurado (fallback: Grep + Read para schema)
+  ✓ context7 — connection verified
+  ○ playwright — needs restart
+  △ supabase — not configured (fallback: Grep + Read for schema)
 ```
 
 ---
 
-### Passo 3: Confirmar Stack
+### Step 3: Confirm Stack
 
-Baseado no proposal e contexto, confirme:
-- Stack tecnológica (Blazor Server, Next.js, etc.)
-- Padrões arquiteturais aplicáveis
-- Componentes reutilizáveis existentes
+Based on the proposal and context, confirm:
+- Tech stack (Blazor Server, Next.js, .NET API, Node.js CLI, etc.)
+- Applicable architectural patterns
+- Existing reusable components
 
-### Passo 4: Listar Agentes Ativos e Preview de Dispatch
+### Step 4: List Active Agents and Dispatch Preview
 
-Mostre os agentes detectados no proposal:
+Show the agents detected from the 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`).
+Parse the JSON and list `activeAgents` with their emojis/icons and responsibilities (look up each agent in `.morph/framework/agents.json` for the `icon` field).
 
-**Se houver 2+ agentes especialistas ativos**, mostre o plano de dispatch para as próximas fases:
+**If there are 2+ specialist agents active**, show the dispatch plan for the next phase:
 
 ```bash
 npx morph-spec dispatch-agents $ARGUMENTS design
 ```
 
-Isso informa quais agentes serão disparados em paralelo na fase de design e quais tasks eles executarão.
+This shows which agents will be dispatched in parallel during the design phase and which tasks they'll execute.
 
-> **Mapeamento importante:** `agents[].id` do dispatch config = `subagent_type` no `Agent` tool.
-> Exemplo: `id: "nextjs-expert"` → `Agent(subagent_type=nextjs-expert, prompt=agent.taskPrompt)`.
-> Cada `id` corresponde ao campo `name:` no frontmatter do arquivo em `.claude/agents/`.
+> **Important mapping:** `agents[].id` from the dispatch config = `subagent_type` in the `Agent` tool.
+> Example: `id: "nextjs-expert"` → `Agent(subagent_type=nextjs-expert, prompt=agent.taskPrompt)`.
+> Each `id` corresponds to the `name:` field in the frontmatter of the file in `.claude/agents/`.
 
-### Passo 5: Atualizar State
+### Step 5: Update State and Determine Next Phase
 
-Marque a feature como na fase SETUP:
+Update the feature state:
 
 ```bash
 npx morph-spec state set $ARGUMENTS status in_progress
 ```
 
-## Outputs
+**Determine the next phase** based on active agents:
 
-**Apresente ao usuário:**
+| Condition | Next Phase |
+|-----------|------------|
+| `ui-designer` is in activeAgents | **uiux** (UI/UX phase) |
+| `ui-designer` is NOT in activeAgents | **design** (skip uiux) |
 
-1. **Contexto carregado**:
-   - Nome do projeto
-   - Stack confirmado
-   - Standards aplicáveis
+Announce the next phase clearly to the user.
 
-2. **Agentes ativos**:
-   - Lista de agentes com emojis
-   - Responsabilidades de cada um
+## Outputs
 
-## Critérios de Avanço
+Present to the user:
 
-- [x] Contexto do projeto carregado
-- [x] Standards identificados (framework + project)
-- [x] Stack confirmado
-- [x] Agentes listados
-- [x] State atualizado para phase: setup
+1. **Context loaded**:
+   - Project name
+   - Confirmed stack
+   - Applicable standards
 
----
+2. **Active agents**:
+   - Agent list with emojis/icons and tier
+   - Responsibilities of each agent
 
-## Integração com Superpowers
+3. **Next phase**:
+   - Which phase comes next (uiux or design)
+   - Why (ui-designer presence or absence)
 
-> Disponível quando o plugin `superpowers` está instalado.
+## Advancement Criteria
 
-| Skill | Quando Usar | Invocação |
-|-------|-------------|-----------|
-| `using-git-worktrees` | Se feature requer isolamento do workspace | `Skill(superpowers:using-git-worktrees)` |
+- [x] Project context loaded
+- [x] Standards identified (framework + project)
+- [x] Stack confirmed
+- [x] Agents listed with icons
+- [x] State updated to in_progress
+- [x] Next phase determined
 
 ---
 
-## Outputs desta Fase
+## Superpowers Integration
 
-<!-- morph:outputs:proposal -->
-| Output | Caminho |
-|--------|---------|
-| `proposal` | `.morph/features/{feature}/0-proposal/proposal.md` |
-<!-- /morph:outputs -->
+> Available when the `superpowers` plugin is installed.
+
+| Skill | When to Use | Invocation |
+|-------|-------------|-----------|
+| `using-git-worktrees` | If the feature requires workspace isolation | `Skill(superpowers:using-git-worktrees)` |
 
 ---
 
-Continuar automaticamente para próxima fase (UI/UX se detectado, ou Design).
+Continue automatically to the next phase (UI/UX if ui-designer detected, otherwise Design).

package/framework/skills/level-1-workflows/morph-phase-tasks/.morph/logs/activity.json

@@ -0,0 +1,14 @@
+{
+  "sessionId": "",
+  "feature": "",
+  "phase": "",
+  "hooks": [
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:38:44"
+    }
+  ],
+  "skills": []
+}