@polymorphism-tech/morph-spec 4.10.0 → 4.10.1

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

@@ -3,234 +3,238 @@ name: morph:phase-uiux
 description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md, components.md, and flows.md using Playwright/Context7 MCPs. Use after setup for features with frontend UI components, pages, dashboards, forms, wizards, or visual interactions requiring design documentation.
 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.1"
 ---
 
-# MORPH UI/UX Design - FASE 1.5
+# MORPH UI/UX Design - Phase 1.5
 
 > INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
 
-Fase condicional para features com front-end. Coleta requisitos de UI/UX, gera wireframes, specs de componentes e fluxos de usuário.
+Conditional phase for features with front-end. Collects UI/UX requirements, generates wireframes, component specs, and user flows.
 
-## Pré-requisitos
+## Prerequisites
 
-- [ ] FASE 1 (Setup) concluída
-- [ ] Feature tem keywords de UI detectadas (blazor, ui, component, page, dashboard, wizard, form, chart)
-- [ ] `uiux-designer` agent ativado
+- [ ] Phase 1 (Setup) completed
+- [ ] Feature has detected UI keywords (blazor, ui, component, page, dashboard, wizard, form, chart)
+- [ ] `uiux-designer` agent activated
 
-## 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 complete guide.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` for MCP reference.
 
-| Ação | Ferramenta | Alternativa |
-|------|------------|-------------|
-| Verificar design system existente | **Read** `.morph/context/design-system.md` | — |
-| Ler screenshots do usuário | **Read** (arquivo de imagem) | — |
-| Buscar variáveis CSS existentes | **Grep** `--root:` em `*.css,*.scss` | — |
-| Encontrar componentes existentes | **Glob** `**/Components/**/*.razor` ou `**/components/**/*.tsx` | — |
-| Documentação de componentes UI | **Context7 MCP** `query_docs({ libraryId, query })` | **WebSearch** + **WebFetch** |
-| Preview de página existente | **Playwright MCP** `browser_navigate()` + `browser_take_screenshot()` | **WebFetch** URL |
-| Inspecionar estrutura da página | **Playwright MCP** `browser_snapshot()` | **WebFetch** + parse manual |
-| Testar layout responsivo | **Playwright MCP** `browser_resize()` + `browser_take_screenshot()` | Manual testing |
-| Referências de design externas | **WebSearch** + **WebFetch** | — |
-| Renderizar templates UI | **Bash** `npx morph-spec template render docs/ui-mockups ...` | — |
-| Gerar design system de CSS existente | **Bash** `npx morph-spec generate design-system --scan` | — |
-| Atualizar state | **Bash** `npx morph-spec state mark-output ...` | — |
+| Action | Tool | Alternative |
+|--------|------|-------------|
+| Check existing design system | **Read** `.morph/context/design-system.md` | — |
+| Read user screenshots | **Read** (image file) | — |
+| Search for existing CSS variables | **Grep** `--root:` in `*.css,*.scss` | — |
+| Find existing components | **Glob** `**/Components/**/*.razor` or `**/components/**/*.tsx` | — |
+| UI component documentation | **Context7 MCP** `query_docs({ libraryId, query })` | **WebSearch** + **WebFetch** |
+| Preview existing page | **Playwright MCP** `browser_navigate()` + `browser_take_screenshot()` | **WebFetch** URL |
+| Inspect page structure | **Playwright MCP** `browser_snapshot()` | **WebFetch** + manual parse |
+| Test responsive layout | **Playwright MCP** `browser_resize()` + `browser_take_screenshot()` | Manual testing |
+| External design references | **WebSearch** + **WebFetch** | — |
+| Render UI templates | **Bash** `npx morph-spec template render docs/ui-mockups ...` | — |
+| Generate design system from existing CSS | **Bash** `npx morph-spec generate design-system --scan` | — |
+| Update state | **Bash** `npx morph-spec state mark-output ...` | — |
 
-**MCPs desta fase:** Playwright (preview, inspeção, responsividade), Context7 (docs de componentes).
+**MCPs for this phase:** Playwright (preview, inspection, responsiveness), Context7 (component docs).
 
-**Anti-padrões:**
-- ❌ WebSearch para docs MudBlazor (use Context7 MCP — mais preciso)
-- ❌ Task agent para ler um screenshot (use Read direto na imagem)
-- ❌ Adivinhar props de componentes (use Context7 para API real)
+**Anti-patterns:**
+- WebSearch for MudBlazor docs (use Context7 MCP — more precise)
+- Task agent to read a screenshot (use Read directly on image)
+- Guess component props (use Context7 for actual API)
 
 ---
 
 ## Workflow
 
-### Passo 0: Garantir fase uiux
+### Step 0: Ensure uiux phase
 
 ```bash
 npx morph-spec state get $ARGUMENTS
 ```
 
-Verifique o campo `"phase"` no output:
+Check the `"phase"` field in the output:
 
-**Se `"phase": "uiux"`** → ✅ fase correta, prossiga.
+**If `"phase": "uiux"`** → correct phase, proceed.
 
-**Se `"phase": "setup"`** → execute:
+**If `"phase": "setup"`** → execute:
 1. `npx morph-spec phase advance $ARGUMENTS` (→ uiux)
 
-**Qualquer outro valor** → ⛔ não prossiga — estado inconsistente, reporte ao usuário.
+**Any other value** → do not proceed — inconsistent state, report to user.
 
-> **Regra:** Nunca escreva em `2-ui/` enquanto a fase não for `uiux`. O hook bloqueará a escrita.
+> **Rule:** Never write to `2-ui/` until the phase is `uiux`. The hook will block writes.
 
 ---
 
-### Passo 0.5: Verificar Design System Existe
+### Step 0.5: Check Design System Exists
 
-**CRITICAL:** Antes de iniciar a FASE UI/UX, verifique se um design system existe:
+**CRITICAL:** Before starting UI/UX phase, check if a design system exists:
 
 ```
 Read: .morph/context/design-system.md
 ```
 
-Se o arquivo não existir (design system não encontrado):
+If the file doesn't exist (design system not found):
 
-1. **Opção A - Scaffold automático:**
-   - O sistema criará automaticamente um design system ao avançar para implementação
-   - Você pode gerar manualmente agora: `npx morph-spec generate design-system`
+1. **Option A - Automatic scaffold:**
+   - The system will automatically create a design system when advancing to implementation
+   - You can generate manually now: `npx morph-spec generate design-system`
 
-2. **Opção B - Criar manualmente:**
-   - Crie `.morph/context/design-system.md` (project-level, compartilhado)
-   - Ou `.morph/features/$ARGUMENTS/2-ui/design-system.md` (feature-specific)
+2. **Option B - Create manually:**
+   - Create `.morph/context/design-system.md` (project-level, shared)
+   - Or `.morph/features/$ARGUMENTS/2-ui/design-system.md` (feature-specific)
 
-3. **Opção C - Scan existing CSS:**
-   - Se o projeto já tem CSS com variáveis: `npx morph-spec generate design-system --scan`
+3. **Option C - Scan existing CSS:**
+   - If the project already has CSS with variables: `npx morph-spec generate design-system --scan`
 
-**⚠️ IMPORTANTE:**
-- Design system é **obrigatório** para features UI
-- Gate automático bloqueará implementação (FASE 5) se design system não existir
-- Melhor criar agora para garantir consistência visual
+**IMPORTANT:**
+- Design system is **mandatory** for UI features
+- Automatic gate will block implementation (Phase 5) if design system doesn't exist
+- Better to create now to ensure visual consistency
 
-### Passo 1: Detectar Se Fase É Necessária
+### Step 1: Detect If Phase Is Needed
 
-Verifique se agentes ativos incluem `uiux-designer`:
+Check if active agents include `uiux-designer`:
 
 ```bash
 npx morph-spec state get $ARGUMENTS
 ```
 
-Se `uiux-designer` NÃO estiver nos `activeAgents`, pule esta fase e continue para FASE 2 (Design).
+If `uiux-designer` is NOT in `activeAgents`, skip this phase and continue to Phase 2 (Design).
 
-### Passo 1.5: Design Thinking — Direção Estética
+### Step 1.5: Design Thinking — Aesthetic Direction
 
 > **Ref:** `framework/standards/frontend/design-system/aesthetic-direction.md`
 
-**ANTES de coletar requisitos técnicos**, definir a direção visual com 4 perguntas:
+**BEFORE collecting technical requirements**, define visual direction with 4 questions:
 
-1. **Purpose**: Que problema resolve? Quem usa? Qual o contexto profissional?
-2. **Tone**: Qual direção? (Minimal Refined / Editorial / Soft Professional / Industrial / Modern Luxury)
-3. **Differentiation**: Qual o 1 elemento memorável desta interface?
-4. **Constraints**: Framework, performance budget, brand guidelines existentes
+1. **Purpose**: What problem does it solve? Who uses it? What is the professional context?
+2. **Tone**: What direction? (Minimal Refined / Editorial / Soft Professional / Industrial / Modern Luxury)
+3. **Differentiation**: What is the 1 memorable element of this interface?
+4. **Constraints**: Framework, performance budget, existing brand guidelines
 
-**CRITICAL:** Commitar à direção ANTES das specs técnicas. Documentar em `ui-design-system.md`
-na seção `## Aesthetic Direction` (template disponível no standard acima).
+**CRITICAL:** Commit to direction BEFORE technical specs. Document in `ui-design-system.md`
+in section `## Aesthetic Direction` (template available in the standard above).
 
-**Anti-padrões a evitar:**
-- ❌ Gradiente roxo em fundo branco (AI cliché)
-- ❌ Inter/Roboto como fonte de display
-- ❌ Grid 3-colunas de cards sem diferencial visual
-- ❌ Paleta de 5 cores de peso igual (sem dominant + accent)
+**Anti-patterns to avoid:**
+- Purple gradient on white background (AI cliche)
+- Inter/Roboto as display font
+- 3-column card grid without visual differentiation
+- 5-color palette with equal weight (without dominant + accent)
 
-### Passo 2: Coletar Input do Usuário
+### Step 2: Collect User Input
 
-**SEMPRE perguntar ao usuário PRIMEIRO:**
+**ALWAYS ask the user FIRST:**
 
-1. **Layout e estilo**:
-   - Você tem alguma ideia de layout em mente?
-   - Tem alguma referência visual? (sites, apps, screenshots)
-   - Como imagina o fluxo do usuário?
+1. **Layout and style**:
+   - Do you have any layout ideas in mind?
+   - Do you have visual references? (sites, apps, screenshots)
+   - How do you envision the user flow?
 
-2. **Componentes e interações**:
-   - Quais os principais componentes desta tela/página?
-   - Quais estados precisam ser considerados? (loading, error, empty, success)
+2. **Components and interactions**:
+   - What are the main components of this screen/page?
+   - What states need to be considered? (loading, error, empty, success)
 
-3. **Imagens de referência**:
-   - Tem imagens de exemplo que eu possa analisar?
-   - Se SIM: use Read tool para ler screenshots e extrair padrões
+3. **Reference images**:
+   - Do you have example images I can analyze?
+   - If YES: use Read tool to read screenshots and extract patterns
 
-### Passo 3: Decidir Biblioteca UI
+### Step 3: Choose UI Library
 
-Escolha entre **Fluent UI Blazor** (recomendado para AI-first) ou **MudBlazor** (componentes complexos):
+Detect the stack from `.morph/config/config.json` and recommend the appropriate library:
 
-**Critérios:**
-- Fluent UI: Para dashboards, forms simples, AI components, Microsoft design language
-- MudBlazor: Para data grids avançadas, charts complexos, material design
+**Blazor stack:**
+- **Fluent UI Blazor** — dashboards, simple forms, AI components, Microsoft design language
+- **MudBlazor** — advanced data grids, complex charts, material design
 
-**Documente a decisão em `decisions.md`.**
+**Next.js stack:**
+- **shadcn/ui + Radix** (recommended) — composable primitives, full control, Tailwind-native
+- **MUI** — feature-rich, enterprise-grade, material design
 
-### Passo 4: Gerar Deliverables
+**Document the decision as an ADR in `decisions.md`** with: context, options considered, decision, and rationale.
 
-Crie os seguintes arquivos em `.morph/features/$ARGUMENTS/`:
+### Step 4: Generate Deliverables
 
-> **Use templates:** Utilize `npx morph-spec template render` para gerar os arquivos a partir dos templates em `.morph/framework/templates/docs/`. Templates disponíveis: `ui-design-system`, `ui-mockups`, `ui-components`, `ui-flows`.
+Create the following files in `.morph/features/$ARGUMENTS/`:
+
+> **Use templates:** Use `npx morph-spec template render` to generate files from templates in `.morph/framework/templates/docs/`. Available templates: `ui-design-system`, `ui-mockups`, `ui-components`, `ui-flows`.
 
 #### 4.1. `ui-design-system.md`
 
-**Se design system project-level existe (`.morph/context/design-system.md`):**
-- Referencie-o nos specs: "Uses project design system at .morph/context/design-system.md"
-- Crie `ui-design-system.md` apenas se houver cores/componentes **específicos** da feature
+**If project-level design system exists (`.morph/context/design-system.md`):**
+- Reference it in specs: "Uses project design system at .morph/context/design-system.md"
+- Create `ui-design-system.md` only if there are feature-specific colors/components
 
-**Se não existe:**
-- Crie design system feature-level completo com:
-  - **Seção `## Aesthetic Direction`** (usar template de `aesthetic-direction.md`):
-    direção, font pair, color philosophy, motion intent, composition approach
-  - Paleta de cores (primary, secondary, accent, semantic)
-  - Tipografia (heading scales, body text, code)
-  - Spacing e layout (grid, margins, paddings)
-  - Componentes base (buttons, inputs, cards)
+**If it doesn't exist:**
+- Create complete feature-level design system with:
+  - **Section `## Aesthetic Direction`** (use template from `aesthetic-direction.md`):
+    direction, font pair, color philosophy, motion intent, composition approach
+  - Color palette (primary, secondary, accent, semantic)
+  - Typography (heading scales, body text, code)
+  - Spacing and layout (grid, margins, paddings)
+  - Base components (buttons, inputs, cards)
 
 #### 4.2. `ui-mockups.md`
 
-Wireframes ASCII + descrições:
-- Layout geral de cada tela/página
-- Posicionamento de componentes
-- Responsividade (desktop, tablet, mobile)
-- Estados (loading, error, empty, success)
+ASCII wireframes + descriptions:
+- General layout of each screen/page
+- Component positioning
+- Responsiveness (desktop, tablet, mobile)
+- States (loading, error, empty, success)
 
 #### 4.3. `ui-components.md`
 
-Specs técnicas de componentes Fluent UI/MudBlazor:
-- Componente a usar (FluentButton, MudDataGrid, etc.)
-- Props e configurações
-- Eventos e bindings
-- Validações e estados
+Technical specs for Fluent UI/MudBlazor components:
+- Component to use (FluentButton, MudDataGrid, etc.)
+- Props and configurations
+- Events and bindings
+- Validations and states
 
 #### 4.4. `ui-flows.md`
 
-Fluxos de usuário completos:
+Complete user flows:
 - User stories
-- Diagramas de fluxo (texto/ASCII)
-- Edge cases (o que acontece se...?)
-- Validações e feedback
+- Flow diagrams (text/ASCII)
+- Edge cases (what happens if...?)
+- Validations and feedback
 
-### CHECKPOINT: Validar Deliverables UI
+### CHECKPOINT: Validate UI Deliverables
 
-**⏸️ PAUSE - Antes de prosseguir para acessibilidade:**
+**PAUSE - Before proceeding to accessibility:**
 
-- [ ] Direção estética definida e documentada em `ui-design-system.md`?
-- [ ] Font pair especificado (não apenas Inter/Roboto para display)?
-- [ ] Color philosophy: dominant + accent + rationale documentados?
-- [ ] Design system definido (project-level ou feature-level)?
-- [ ] Wireframes cobrem todos os estados (loading, error, empty, success)?
-- [ ] Componentes especificados com props reais da biblioteca UI escolhida?
-- [ ] Fluxos de usuário completos com edge cases?
-- [ ] Biblioteca UI escolhida documentada como ADR em `decisions.md`?
+- [ ] Aesthetic direction defined and documented in `ui-design-system.md`?
+- [ ] Font pair specified (not just Inter/Roboto for display)?
+- [ ] Color philosophy: dominant + accent + rationale documented?
+- [ ] Design system defined (project-level or feature-level)?
+- [ ] Wireframes cover all states (loading, error, empty, success)?
+- [ ] Components specified with actual props from chosen UI library?
+- [ ] Complete user flows with edge cases?
+- [ ] Chosen UI library documented as ADR in `decisions.md`?
 
-**❌ Se alguma checkbox NÃO estiver marcada:**
-→ Voltar e completar o deliverable faltante
+**If any checkbox is NOT checked:**
+→ Go back and complete the missing deliverable
 
-**✅ Se TODAS as checkboxes estiverem marcadas:**
-→ Prosseguir para validação de acessibilidade
+**If ALL checkboxes are checked:**
+→ Proceed to accessibility validation
 
 ---
 
-### Passo 5: Validar Acessibilidade e Responsividade
+### Step 5: Validate Accessibility and Responsiveness
 
-Documente nos arquivos UI:
+Document in UI files:
 - **WCAG 2.1 Level AA** compliance
-  - Contraste de cores adequado
-  - Labels acessíveis para screen readers
-  - Navegação por teclado
+  - Adequate color contrast
+  - Accessible labels for screen readers
+  - Keyboard navigation
 - **Responsive breakpoints**
   - Desktop (>1200px)
   - Tablet (768px - 1199px)
   - Mobile (<768px)
 
-### Passo 6: Atualizar State
+### Step 6: Update State
 
 ```bash
 npx morph-spec state mark-output $ARGUMENTS ui-design-system
@@ -239,77 +243,76 @@ npx morph-spec state mark-output $ARGUMENTS ui-components
 npx morph-spec state mark-output $ARGUMENTS ui-flows
 ```
 
-> **Nota sobre formatos:** Os comandos `mark-output` aceitam TANTO kebab-case (`ui-design-system`)
-> QUANTO camelCase (`uiDesignSystem`). Ambos os formatos funcionam igualmente! Use o que for mais
-> confortável para você. Exemplos:
-> - `npx morph-spec state mark-output my-feature uiDesignSystem` ✅
-> - `npx morph-spec state mark-output my-feature ui-design-system` ✅
+> **Format note:** The `mark-output` commands accept BOTH kebab-case (`ui-design-system`)
+> AND camelCase (`uiDesignSystem`). Both formats work equally! Use whichever is more
+> comfortable for you. Examples:
+> - `npx morph-spec state mark-output my-feature uiDesignSystem`
+> - `npx morph-spec state mark-output my-feature ui-design-system`
 
-## Outputs Gerados
+## Generated Outputs
 
 - `.morph/features/$ARGUMENTS/2-ui/design-system.md`
 - `.morph/features/$ARGUMENTS/2-ui/mockups.md`
 - `.morph/features/$ARGUMENTS/2-ui/components.md`
 - `.morph/features/$ARGUMENTS/2-ui/flows.md`
-- `.morph/features/$ARGUMENTS/1-design/decisions.md` (atualizado com ADR UI library)
+- `.morph/features/$ARGUMENTS/1-design/decisions.md` (updated with UI library ADR)
 
-### Passo 7: Validar Design com Frontend Review
+### Step 7: Validate Design with Frontend Review
 
-Após gerar todos os 4 outputs de UI e atualizar o state (Passo 6):
+After generating all 4 UI outputs and updating state (Step 6):
 
 ```bash
 /frontend-review $ARGUMENTS
 ```
 
-O skill valida: contraste WCAG dos tokens, existência de todos os outputs, acessibilidade
-estática no design, e gera screenshots dos mockups se dev server disponível.
+The skill validates: WCAG token contrast, existence of all outputs, static design accessibility, and generates mockup screenshots if dev server is available.
 
-**🚫 Se o frontend-review bloquear**, corrija os issues antes de apresentar ao usuário.
+**If frontend-review blocks**, fix issues before presenting to user.
 
 ---
 
-## PAUSA OBRIGATÓRIA
+## MANDATORY PAUSE
 
-Use `AskUserQuestion` para capturar aprovação explícita antes de avançar:
+Use `AskUserQuestion` to capture explicit approval before advancing:
 
 ```json
 {
   "questions": [{
-    "header": "Aprovação",
-    "question": "UI/UX gerado. Aprovar para avançar para design técnico?",
+    "header": "Approval",
+    "question": "UI/UX generated. Approve to advance to technical design?",
     "multiSelect": false,
     "options": [
-      { "label": "Aprovar UI/UX", "description": "Avançar para fase de design técnico" },
-      { "label": "Tenho feedback", "description": "Digite o que deseja ajustar no campo abaixo (Other)" }
+      { "label": "Approve UI/UX", "description": "Advance to technical design phase" },
+      { "label": "I have feedback", "description": "Type what you want to adjust in the field below (Other)" }
     ]
   }]
 }
 ```
 
-- **"Aprovar UI/UX"** →
+- **"Approve UI/UX"** →
   ```bash
   npx morph-spec approve $ARGUMENTS uiux
   npx morph-spec phase advance $ARGUMENTS
   ```
-- **"Tenho feedback" ou "Other"** → aplique o feedback recebido e repita esta PAUSA
+- **"I have feedback" or "Other"** → apply the received feedback and repeat this PAUSE
 
-## Critérios de Avanço
+## Advancement Criteria
 
-- [x] Input do usuário coletado (layout, referências)
-- [x] Biblioteca UI escolhida e justificada (ADR)
-- [x] 4 deliverables criados (design-system, mockups, components, flows)
-- [x] Acessibilidade WCAG 2.1 documentada
-- [x] Responsividade especificada
-- [x] State atualizado
-- [x] Usuário aprovou UI/UX
+- [x] User input collected (layout, references)
+- [x] UI library chosen and justified (ADR)
+- [x] 4 deliverables created (design-system, mockups, components, flows)
+- [x] WCAG 2.1 accessibility documented
+- [x] Responsiveness specified
+- [x] State updated
+- [x] User approved UI/UX
 
 ---
 
-## Outputs desta Fase
+## Phase Outputs
 
 <!-- morph:outputs:uiux -->
-| Output | Caminho |
-|--------|---------|
+| Output | Path |
+|--------|------|
 | `uiDesignSystem` | `.morph/features/{feature}/2-ui/design-system.md` |
 | `uiMockups` | `.morph/features/{feature}/2-ui/mockups.md` |
 | `uiComponents` | `.morph/features/{feature}/2-ui/components.md` |
@@ -318,4 +321,4 @@ Use `AskUserQuestion` para capturar aprovação explícita antes de avançar:
 
 ---
 
-Continuar automaticamente para FASE 2 (Design) após aprovação.
+Continue automatically to Phase 2 (Design) after approval.

package/framework/skills/level-1-workflows/morph-scope-escalation/SKILL.md

@@ -3,6 +3,7 @@ name: morph:scope-escalation
 description: Guided workflow for mid-implementation scope escalation — analyzes complexity discovery, recommends action, and executes phase regression or task expansion
 user-invocable: true
 argument-hint: "[feature-name]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
 # Scope Escalation Workflow
@@ -18,11 +19,37 @@ Use this skill when a task during implementation reveals significantly more comp
 
 ### Step 1: COLLECT Evidence
 
-Ask the user (using `AskUserQuestion`):
+Use `AskUserQuestion` to gather the details:
+
+```json
+{
+  "questions": [
+    {
+      "header": "Task ID",
+      "question": "Which task triggered the complexity discovery?",
+      "multiSelect": false,
+      "options": [
+        { "label": "T001", "description": "First task" },
+        { "label": "T002", "description": "Second task" },
+        { "label": "Other", "description": "Type the task ID" }
+      ]
+    },
+    {
+      "header": "Discovery",
+      "question": "What complexity did you discover?",
+      "multiSelect": true,
+      "options": [
+        { "label": "Hidden dependencies", "description": "More systems involved than spec assumed" },
+        { "label": "Wrong assumptions", "description": "Spec assumed simpler architecture" },
+        { "label": "Missing abstractions", "description": "Need new patterns/interfaces not in contracts" },
+        { "label": "Other", "description": "Describe the discovery" }
+      ]
+    }
+  ]
+}
+```
 
-1. **Which task triggered the discovery?** (task ID from tasks.md)
-2. **What did you discover?** (specific complexity: hidden dependencies, wrong assumptions, missing abstractions)
-3. **Show evidence** — read the relevant code files to understand the actual complexity
+> Populate the Task ID options dynamically from the feature's `tasks.md`. After receiving answers, **read the relevant code files** to verify the evidence before classifying.
 
 ### Step 2: ANALYZE Impact
 
@@ -54,11 +81,33 @@ Explain WHY you recommend this classification based on the evidence.
 
 Pause and wait for user confirmation using `AskUserQuestion`:
 
-- "Do you agree with the [impact] classification?"
-- "Should we proceed with [action]?"
-- Allow override: "Or would you prefer a different target phase?"
+```json
+{
+  "questions": [
+    {
+      "header": "Severity",
+      "question": "Impact classified as {LOW|MEDIUM|HIGH}. Do you agree?",
+      "multiSelect": false,
+      "options": [
+        { "label": "Agree", "description": "Classification is correct" },
+        { "label": "Override", "description": "I think the impact is different" }
+      ]
+    },
+    {
+      "header": "Action",
+      "question": "Recommended action: {action}. Proceed?",
+      "multiSelect": false,
+      "options": [
+        { "label": "Proceed", "description": "{action description}" },
+        { "label": "Different target", "description": "I want to regress to a different phase" },
+        { "label": "Cancel", "description": "Do not escalate — continue as-is" }
+      ]
+    }
+  ]
+}
+```
 
-**DO NOT proceed without explicit user approval.**
+**DO NOT proceed without explicit user approval.** If user chooses "Cancel", stop the workflow entirely.
 
 ### Step 5: EXECUTE
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "4.10.0",
+  "version": "4.10.1",
   "description": "MORPH-SPEC: AI-First development framework with validation pipeline and multi-stack support",
   "keywords": [
     "claude-code",
@@ -54,7 +54,7 @@
     "chalk": "^5.3.0",
     "commander": "^12.0.0",
     "fs-extra": "^11.2.0",
-    "glob": "^10.3.0",
+    "glob": "^13.0.6",
     "handlebars": "^4.7.8",
     "inquirer": "^9.2.0",
     "minimatch": "^9.0.5",
@@ -75,7 +75,7 @@
     "access": "public"
   },
   "devDependencies": {
-    "c8": "^10.1.3",
+    "c8": "^11.0.0",
     "docdash": "^2.0.2",
     "jsdoc": "^4.0.5"
   }

package/src/commands/project/doctor.js

@@ -5,6 +5,7 @@ import fs from 'fs-extra';
 import chalk from 'chalk';
 import { logger } from '../../utils/logger.js';
 import { pathExists, readJson } from '../../utils/file-copier.js';
+import { checkClaudeMdImport } from '../../utils/claude-md-injector.js';
 import {
   checkCLIOutdated,
   checkProjectOutdated,
@@ -504,10 +505,14 @@ export async function doctorCommand(options = {}) {
     hasWarnings = true;
   }
 
-  // Check CLAUDE.md
+  // Check CLAUDE.md has morph-spec @import
   const claudeMd = join(targetPath, 'CLAUDE.md');
-  if (await pathExists(claudeMd)) {
+  const claudeMdStatus = await checkClaudeMdImport(claudeMd);
+  if (claudeMdStatus === 'ok') {
     checks.push({ name: 'CLAUDE.md', status: 'ok' });
+  } else if (claudeMdStatus === 'missing-import') {
+    checks.push({ name: 'CLAUDE.md', status: 'warn', msg: 'missing @.claude/CLAUDE.md import — run morph-spec update' });
+    hasWarnings = true;
   } else {
     checks.push({ name: 'CLAUDE.md', status: 'missing' });
     hasErrors = true;