sedd 0.1.1 → 0.1.3

package/commands/sedd.clarify.md

@@ -40,11 +40,11 @@ User runs `/sedd.clarify`
 - AI listens and records everything in clarify.md
 - User controls the flow with inline commands:
 
-| Command | Aliases | Action |
-|---------|---------|--------|
-| `continue` | `mais`, `more`, `+` | Keep discussing, AI records notes |
-| `pergunta` | `question`, `q`, `?` | AI asks next clarification question |
-| `tasks` | `done`, `gerar`, `finish` | Generate tasks.md and finish |
+| Comando | O que faz |
+|---------|-----------|
+| `continue` | Continuar explicando, AI anota |
+| `pergunte` | AI faz próxima pergunta de clarificação |
+| `tasks` | Gerar tasks.md e finalizar |
 
 ⚠️ **ALWAYS CREATES TASKS**
 - Every clarify creates a NEW migration
@@ -53,26 +53,31 @@ User runs `/sedd.clarify`
 
 ## Workflow
 
-### Step 1: Load Context
+### Step 1: Capture Expected Outcome (FIRST - MANDATORY)
 
-Read from feature root:
-- spec.md
-- interfaces.ts
-- Previous migrations (if any)
-
-### Step 2: Capture Expected Outcome (NEW)
+**ANTES DE QUALQUER COISA**, pergunte ao usuário:
 
-Before creating migration, ask user:
 ```
-What do you expect to achieve with this clarification?
-(This will be used to verify task alignment)
+🎯 Qual é sua EXPECTATIVA para esta clarificação?
+
+O que você espera ter funcionando ao final desta migration?
+(Isso será usado para validar se as tasks cobrem seu objetivo)
 ```
 
-Save in `clarify.md` under `## Expected Outcome` section.
+Save in `clarify.md` under `## Expected Outcome` section (NO TOPO).
+
+**NÃO PROSSIGA** sem a expectativa do usuário.
+
+### Step 2: Load Context
+
+Read from feature root:
+- spec.md (especialmente a seção Expectation original)
+- interfaces.ts
+- Previous migrations (if any)
 
 ### Step 3: Create New Migration Folder
 
-Generate new migration folder FIRST:
+Generate new migration folder:
 
 ```
 Migration ID: 001 (or next: 002, 003...)
@@ -120,17 +125,14 @@ Present the clarification session with available commands:
 Spec loaded: spec.md
 Interfaces: interfaces.ts
 
-Você pode:
-• Explicar livremente o que precisa
-• Adicionar notas e decisões
-• Responder perguntas
+Você pode explicar livremente o que precisa.
+Eu vou anotar tudo e fazer perguntas quando necessário.
+
+Digite um comando para controlar o fluxo:
 
-Comandos disponíveis:
-┌───────────┬────────────────────────────────────┐
-│ continue  │ Continuar explicando (mais, +)     │
-│ pergunta  │ AI faz próxima pergunta (q, ?)     │
-│ tasks     │ Gerar tasks e finalizar (done)     │
-└───────────┴────────────────────────────────────┘
+  continue  → Continuar explicando
+  pergunte  → AI faz próxima pergunta
+  tasks     → Gerar tasks e finalizar
 
 Como você quer começar?
 ```
@@ -184,13 +186,13 @@ System will support multiple tenants with isolated configurations.
 ```
 ✓ Anotado: Multi-tenant com configurações isoladas
 
-Continue explicando ou use um comando:
-• continue / mais → mais detalhes
-• pergunta / ? → AI faz uma pergunta
-• tasks / done → gerar tasks
+Digite um comando:
+  continue  → Continuar explicando
+  pergunte  → AI faz próxima pergunta
+  tasks     → Gerar tasks e finalizar
 ```
 
-#### 5.2 User Says "continue" / "mais" / "more" / "+"
+#### 5.2 User Says "continue"
 
 Keep in discussion mode:
 
@@ -198,7 +200,7 @@ Keep in discussion mode:
 Ok, continue explicando...
 ```
 
-#### 5.3 User Says "pergunta" / "question" / "q" / "?"
+#### 5.3 User Says "pergunte"
 
 AI analyzes gaps and asks ONE clarification question:
 
@@ -223,7 +225,7 @@ Sua resposta (ou continue explicando):
 
 After user answers, update clarify.md and decisions.md immediately.
 
-#### 5.4 User Says "tasks" / "done" / "gerar" / "finish"
+#### 5.4 User Says "tasks"
 
 Proceed to Step 6 (Generate Tasks).
 
@@ -255,47 +257,163 @@ T001-001, T001-002 → T001-003 → T001-004
                    → T001-005
 ```
 
-### Step 7: Expectation Alignment Check (NEW)
+### Step 6.5: Generate Acceptance Criteria (NEW)
+
+Após gerar tasks, criar critérios de aceite baseados na expectativa:
+
+#### 6.5.1 Transformar Expectativa em Critérios
+
+Regras de geração:
 
-After generating tasks, verify alignment with expected outcome:
+| Padrão na Expectativa | Critério Gerado |
+|----------------------|-----------------|
+| "can {verb}" | User can perform {verb} |
+| "persist" ou "save" | Data survives refresh/session |
+| "{noun} in {location}" | {noun} appears in {location} |
+| "across {context}" | Works in multiple {context} |
+| "immediately" | Response time < 100ms |
 
+**Exemplo:**
+
+Expectativa: "User can toggle dark mode in settings and persist across sessions"
+
+Critérios gerados:
 ```markdown
-## Expectation Alignment Check
+- [ ] **AC-001:** User can toggle dark mode
+  - Verificar: Clicar no toggle, tema muda
 
-**Your expectation:**
-> [User's expected outcome from clarify.md]
+- [ ] **AC-002:** Toggle está em settings
+  - Verificar: Navegar para settings, toggle visível
 
-**Generated tasks cover:**
-- Task T001-001: Creates ThemeContext ✅
-- Task T001-002: Updates database schema ✅
-- Task T001-003: Creates toggle component ✅
-- Task T001-004: Adds to settings page ✅
-- Task T001-005: API endpoint ✅
+- [ ] **AC-003:** Theme persists after refresh
+  - Verificar: Setar dark mode, refresh, tema permanece
 
-**Alignment:** ✅ Aligned
+- [ ] **AC-004:** Theme persists across sessions
+  - Verificar: Fechar browser, reabrir, tema permanece
 ```
 
-#### When Misaligned:
+#### 6.5.2 Criar acceptance.md
+
+Escrever em `{migration_folder}/acceptance.md` usando template.
+
+#### 6.5.3 Linkar em tasks.md
 
-If tasks don't cover the expectation:
+Adicionar ao final de tasks.md:
+```markdown
+---
 
+## Acceptance Criteria
+
+Ver `acceptance.md` para checklist de verificação.
 ```
-⚠️ Tasks geradas não cobrem completamente sua expectativa.
 
-**Missing from expectation:**
-- [item not covered by tasks]
+### Step 7: Expectation Alignment Check + Score
+
+Após gerar tasks E acceptance criteria, calcular score de alinhamento:
 
-Deseja prosseguir mesmo assim? [Y/n]
+#### 7.1 Extrair Keywords da Expectativa
+
+```
+PASSO 1: Tokenizar expectativa
+  - Dividir em palavras
+  - Remover stop words (the, a, an, is, are, can, will, to, for, in, on, and, or, user, etc.)
+  - Extrair termos significativos
+
+PASSO 2: Pesar tokens
+  - Verbos (ações): peso 3
+  - Substantivos (entidades): peso 2
+  - Modificadores: peso 1
+
+Exemplo: "User can toggle dark mode in settings and persist across sessions"
+Tokens: {toggle: 3, dark: 1, mode: 2, settings: 2, persist: 3, sessions: 1}
+Total: 12
 ```
 
-**If user says "no"** - Return to discussion mode:
+#### 7.2 Verificar Cobertura nas Tasks
+
+Para cada token, buscar nas descrições das tasks geradas.
+
+#### 7.3 Calcular Score
+
 ```
-Ok, vamos continuar a clarificação.
+matched_weight = soma dos pesos dos tokens encontrados
+score = (matched_weight / total_weight) * 100
+```
+
+#### 7.4 Exibir Resultado
+
+**Se coverage >= 80%:**
+```
+📊 Coverage: ~{score}% 🟢
+
+**Sua expectativa:**
+> {expectation}
+
+**Tokens encontrados nas tasks:**
+  ✅ toggle (T001-003) - peso 3
+  ✅ dark mode (T001-003, T001-004) - peso 3
+  ✅ settings (T001-004) - peso 2
+  ✅ persist (T001-003) - peso 3
+  ❌ sessions - peso 1
+
+Score: 11/12 = 92%
+
+✅ Boa cobertura! Tasks prontas.
+```
+
+**Se coverage 60-79%:**
+```
+📊 Coverage: ~{score}% 🟡
+
+**Sua expectativa:**
+> {expectation}
+
+**Cobertos:**
+  ✅ toggle (T001-003)
+  ✅ dark mode (T001-003)
+
+**Faltando:**
+  ❌ persist - nenhuma task menciona
+  ❌ sessions - não encontrado
+
+⚠️ Cobertura parcial. Deseja adicionar tasks para cobrir os gaps? [Y/n]
+```
+
+**Se coverage < 60%:**
+```
+📊 Coverage: ~{score}% 🔴
+
+**Sua expectativa:**
+> {expectation}
+
+**Cobertos:**
+  ✅ toggle (T001-003)
+
+**Faltando:**
+  ❌ dark mode
+  ❌ settings
+  ❌ persist
+  ❌ sessions
+
+⚠️ Cobertura baixa! Recomendo adicionar mais tasks.
+
+**Opções:**
+1. Adicionar tasks para conceitos faltando
+2. Prosseguir assim mesmo
+3. Refinar expectativa
+
+O que deseja fazer?
+```
+
+#### 7.5 Se Usuário Escolhe Adicionar Tasks
+
+Voltar ao modo discussão:
+```
+Vamos adicionar tasks para os conceitos faltando.
+
+Faltando: "persist", "sessions"
 
-Use os comandos:
-• continue - explicar mais detalhes
-• pergunta - AI faz pergunta de refinamento
-• tasks - tentar gerar tasks novamente
+Como você imagina a persistência funcionando?
 ```
 
 ### Step 8: Update _meta.json
@@ -378,10 +496,10 @@ Parent references allow tracking the evolution:
 - **FLEXIBLE DISCUSSION** - User controls the flow with inline commands
 - **UPDATE FILES IMMEDIATELY** - After each user input
 - **RECOGNIZE INLINE COMMANDS:**
-  - `continue`, `mais`, `more`, `+` → Keep discussing
-  - `pergunta`, `question`, `q`, `?` → AI asks next question
-  - `tasks`, `done`, `gerar`, `finish` → Generate tasks and end
-- ALWAYS generate tasks.md when user says "tasks/done"
+  - `continue` → Continuar explicando
+  - `pergunte` → AI faz próxima pergunta
+  - `tasks` → Gerar tasks e finalizar
+- ALWAYS generate tasks.md when user says "tasks"
 - Task IDs include migration ID (T001-XXX)
 - Each clarify = new migration folder
 - Auto-split files > 400 lines
@@ -401,12 +519,12 @@ Parent references allow tracking the evolution:
 │  User explains → AI records in clarify.md + decisions.md    │
 │       ↓                                                     │
 │  "continue" → AI: "Ok, continue..."                         │
-│  "pergunta" → AI asks ONE question                          │
+│  "pergunte" → AI asks ONE question                          │
 │  "tasks"    → Exit loop, generate tasks                     │
 └─────────────────────────────────────────────────────────────┘
                               ↓
 ┌─────────────────────────────────────────────────────────────┐
-│  User says "tasks" / "done"                                 │
+│  User says "tasks"                                          │
 │  → AI generates tasks.md from all notes + decisions         │
 │  → AI updates _meta.json                                    │
 │  → AI asks about commit                                     │

package/commands/sedd.implement.md

@@ -98,14 +98,20 @@ For each task in order:
    | T001-001 | 001 | in-progress | 10:30 | - |
    ```
 
-2. **Show task context**
+2. **Show task context with expectations**
    ```
    📌 Task T001-001 [Foundation]
    Create ThemeContext in src/contexts/ThemeContext.tsx
 
    From Decision D001-001: Theme persisted in user account
+
+   ━━━ Expectations ━━━
+   🎯 Feature: User can customize theme preferences
+   📍 Migration 001: Toggle dark mode with persistence
    ```
 
+   **Nota:** Se feature expectation e migration expectation forem iguais, mostrar apenas uma.
+
 3. **Execute the task**
 
 4. **Update ALL task files** (CRITICAL - keep them in sync):
@@ -131,6 +137,80 @@ For each task in order:
 
 5. **Verify sync** - All three files must show same completed count
 
+### Step 5.5: Expectation Checkpoint (NEW)
+
+A cada 3 tasks completadas, pausar e verificar alinhamento com expectativa.
+
+#### 5.5.1 Trigger
+
+Checkpoint dispara quando:
+- `completed_in_session % 3 == 0` (a cada 3 tasks)
+- AND `remaining_tasks > 0` (não está no final)
+- AND NÃO está usando `--all` flag
+
+#### 5.5.2 Prompt do Checkpoint
+
+```
+⏸️ Checkpoint - {completed}/{total} tasks completas
+
+**Sua expectativa:**
+> {expectation_from_meta}
+
+**Completadas até agora:**
+- [x] T001-001: Created ThemeContext
+- [x] T001-002: Updated database schema
+- [x] T001-003: Created toggle component
+
+**Restantes:**
+- [ ] T001-004: Add to settings page
+- [ ] T001-005: API endpoint
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Isso ainda está alinhado com sua expectativa? [Y/n/ajustar]
+```
+
+#### 5.5.3 Respostas do Usuário
+
+**Se "Y" ou Enter (default):**
+```
+✓ Continuando implementação...
+```
+
+**Se "n":**
+```
+⏹️ Implementação pausada.
+
+**Opções:**
+1. /sedd.clarify - Criar nova migration para ajustes
+2. Continuar mesmo assim
+3. Marcar tasks restantes como blocked
+
+O que deseja fazer?
+```
+
+**Se "ajustar":**
+```
+O que mudou na sua expectativa?
+(Isso será registrado mas não altera as tasks existentes)
+```
+
+Registrar em `progress.md`:
+```markdown
+## Expectation Notes
+
+### Checkpoint em T001-003 (2026-01-11 14:30)
+**Original:** User can toggle dark mode in settings
+**Nota do usuário:** Também quero detecção de preferência do sistema
+**Ação:** Continuar com tasks atuais, criar migration 002 depois
+```
+
+#### 5.5.4 Configuração
+
+Intervalo pode ser ajustado:
+- Default: A cada 3 tasks
+- Override: `/sedd.implement --checkpoint=5` (a cada 5)
+- Desabilitar: `/sedd.implement --no-checkpoint`
+
 ### Step 6: Migration Boundaries
 
 When completing a migration's tasks:
@@ -146,47 +226,139 @@ All 5 tasks finished:
 - T001-005 ✓
 ```
 
-### Step 7: Expectation Verification (NEW)
+### Step 7: Final Validation with Acceptance Criteria (ENHANCED)
 
-After completing all tasks in a migration, verify against the original expectation:
+Quando todas as tasks de uma migration forem completadas, validar usando acceptance criteria.
 
+#### 7.1 Carregar Acceptance Criteria
+
+Se `{migration}/acceptance.md` existe, carregar os critérios.
+
+#### 7.2 Prompt de Verificação
+
+```
+🏁 Migration 001 Completa!
+
+**Todas {N} tasks finalizadas.**
+
+**Sua expectativa era:**
+> {expectation}
+
+**Acceptance Criteria:**
+- [ ] AC-001: User can access dark mode toggle
+- [ ] AC-002: Toggle changes theme immediately
+- [ ] AC-003: Theme persists after refresh
+- [ ] AC-004: Theme persists across sessions
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Por favor verifique cada critério. Quais foram atendidos?
+(Digite: all, none, ou IDs específicos como "1,2,4")
+```
+
+#### 7.3 Processar Resposta
+
+**Se "all":**
+```
+✅ Todos os critérios atendidos!
+
+Atualizando acceptance.md...
+Migration 001 marcada como completa com sucesso total.
+```
+
+Atualizar `acceptance.md`:
 ```markdown
-## Expectation Verification
+## Sign-off
+
+| Critério | Status | Verificado Por | Data |
+|----------|--------|----------------|------|
+| AC-001 | passed | user | 2026-01-11 |
+| AC-002 | passed | user | 2026-01-11 |
+| AC-003 | passed | user | 2026-01-11 |
+| AC-004 | passed | user | 2026-01-11 |
+```
+
+**Se parcial (ex: "1,2"):**
+```
+⚠️ Alguns critérios não atendidos
+
+**Atendidos:**
+- [x] AC-001: User can access dark mode toggle
+- [x] AC-002: Toggle changes theme immediately
 
-**Original expectation:**
-> User can toggle dark mode in settings and have it persist across sessions
+**Não Atendidos:**
+- [ ] AC-003: Theme persists after refresh
+- [ ] AC-004: Theme persists across sessions
 
-**Delivered:**
-- Implemented 5 tasks
-- Created ThemeContext for state management
-- Added database persistence
-- Created toggle component in settings
-- API endpoint for saving preference
+**Opções:**
+1. Criar migration de follow-up para critérios faltando
+2. Marcar como completo com notas (entrega parcial)
+3. Manter migration aberta para debug
 
-**Alignment:** ✅ Expectation met
+O que deseja fazer?
 ```
 
-#### When Not Met:
+#### 7.4 Follow-up Migration
 
-If expectation was not fully met:
+Se usuário escolhe opção 1:
+```
+Criando migration de follow-up...
+
+Expectativa sugerida para nova migration:
+> "Theme should persist after page refresh and across browser sessions"
+
+Deseja rodar /sedd.clarify agora? [Y/n]
+```
 
+#### 7.5 Atualizar _meta.json
+
+Registrar resultado da validação:
+```json
+{
+  "migrations": {
+    "001": {
+      "status": "completed",
+      "expectationMet": "partial",
+      "criteriaResults": {
+        "passed": ["AC-001", "AC-002"],
+        "failed": ["AC-003", "AC-004"],
+        "deferredTo": "002"
+      },
+      "completedAt": "2026-01-11T15:30:00Z"
+    }
+  }
+}
 ```
-⚠️ Expectation may not be fully met
 
-**Original expectation:**
-> User can toggle dark mode in settings and have it persist across sessions
+#### 7.6 Atualizar acceptance.md
 
-**What may be missing:**
-- [potential gap]
+```markdown
+## Sign-off
+
+| Critério | Status | Verificado Por | Data |
+|----------|--------|----------------|------|
+| AC-001 | passed | user | 2026-01-11 |
+| AC-002 | passed | user | 2026-01-11 |
+| AC-003 | deferred | - | - |
+| AC-004 | deferred | - | - |
+
+## Notas
+AC-003, AC-004 diferidos para migration 002.
+```
+
+#### 7.7 Se Não Existir acceptance.md
+
+Fazer verificação simplificada:
+```
+🏁 Migration 001 Completa!
 
-**Options:**
-1. Create new migration to address gaps
-2. Mark as complete anyway (partial delivery)
+**Sua expectativa era:**
+> {expectation}
 
-What would you like to do?
+Sua expectativa foi atendida? [Y/n/parcial]
 ```
 
-If user chooses option 1, suggest running `/sedd.clarify` for a follow-up migration.
+Se "parcial", perguntar o que faltou e sugerir nova migration.
 
 ### Step 8: Ask About Commit
 

package/commands/sedd.specify.md

@@ -40,7 +40,24 @@ Default `sedd.config.json`:
 
 Extract feature description from user input or ask interactively.
 
-### Step 2: Architecture Analysis (MANDATORY)
+### Step 2: Capture Expectation (FIRST - MANDATORY)
+
+**ANTES DE QUALQUER COISA**, pergunte ao usuário:
+
+```
+🎯 Qual é sua EXPECTATIVA para esta feature?
+
+O que você espera ver funcionando quando estiver pronto?
+(Isso será usado para validar se as tasks cobrem seu objetivo)
+```
+
+Save expectation in:
+- `spec.md` under `## Expectation` section (NO TOPO)
+- `_meta.json` in `expectation` field
+
+**NÃO PROSSIGA** sem a expectativa do usuário.
+
+### Step 3: Architecture Analysis (MANDATORY)
 
 Before creating spec, MUST search for related implementations:
 
@@ -53,25 +70,13 @@ Find similar:
 
 Document findings in spec.md.
 
-### Step 3: Capture Expectation (NEW)
-
-Ask user for their expectation:
-```
-What do you expect as the final outcome of this feature?
-(This will be used to verify alignment when implementation is complete)
-```
-
-Save expectation in:
-- `spec.md` under `## Expectation` section
-- `_meta.json` in `expectation` field
-
 ### Step 4: Create Feature Structure
 
 ```
 {{specsDir}}/{{FEATURE_ID}}-{{SHORT_NAME}}/
 ├── _meta.json              # Metadata (with expectation)
 ├── CHANGELOG.md            # Changelog
-├── spec.md                 # Base specification (with Expectation section)
+├── spec.md                 # Base specification (with Expectation section NO TOPO)
 ├── interfaces.ts           # TypeScript interfaces
 └── ui-mockups/             # If UI feature
     └── component-name.md
@@ -80,10 +85,10 @@ Save expectation in:
 ### Step 5: Generate spec.md
 
 Use template with:
+- **Expectation section NO TOPO** (capturada no Step 2)
 - Feature name, ID, timestamp
 - User stories based on description
 - Mark requirements as NEEDS_CLARIFICATION where unclear
-- Include Expectation section
 
 ### Step 6: Generate interfaces.ts (MANDATORY)
 

package/hooks/README.md

@@ -62,19 +62,22 @@ The hook detects keywords and **FORCES** skills into context:
 ### Output Example
 
 ```xml
-<forced-skills>
-[SKILL ACTIVATED: langchain-expert]
-You MUST use the langchain-expert skill for this request.
-Follow LangGraph 1.0+ patterns, check Context7 MCP for latest docs.
-</forced-skills>
-
 <sedd-context>
-**Branch: 023-agent-executor** | Migration: 004 | Progress: 187/187 tasks
+**Branch: 023-agent-executor** | Migration: 004 | Progress: 5/10 tasks
+
+🎯 **EXPECTATIVA:** User can toggle dark mode and have it persist across sessions
 
-Use `/sedd.implement` to execute tasks.
+Pending tasks:
+- T004-001: Create ThemeContext
+- T004-002: Add toggle component
+... and 3 more
 </sedd-context>
 ```
 
+### Expectation Reminder
+
+O hook **sempre mostra a EXPECTATIVA** do `_meta.json` para lembrar a AI do objetivo final. Isso garante que todas as ações estejam alinhadas com o que o usuário espera.
+
 ---
 
 ## post-tool-use.js

package/hooks/check-roadmap.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 /**
  * SEDD Hook - UserPromptSubmit
- * Simple task count display for feature branches
+ * Task count display and expectation tracking for feature branches
  */
 
 const fs = require('fs');
@@ -24,7 +24,13 @@ const IGNORE_PATTERNS = [
   /^prossiga\s*$/i,
 ];
 
-/** @param {string} cwd */
+const STOP_WORDS = new Set([
+  'the', 'a', 'an', 'is', 'are', 'can', 'will', 'should', 'must',
+  'to', 'for', 'in', 'on', 'at', 'by', 'with', 'and', 'or', 'but',
+  'user', 'users', 'system', 'be', 'have', 'has', 'it', 'its', 'of',
+  'that', 'this', 'from', 'as', 'when', 'if', 'then', 'so', 'do',
+]);
+
 const loadConfig = (cwd) => {
   const configPath = path.join(cwd, 'sedd.config.json');
   if (!fs.existsSync(configPath)) return DEFAULT_CONFIG;
@@ -37,7 +43,6 @@ const loadConfig = (cwd) => {
   }
 };
 
-/** @param {string} cwd */
 const getCurrentBranch = (cwd) => {
   try {
     return execSync('git rev-parse --abbrev-ref HEAD', { cwd, encoding: 'utf8' }).trim();
@@ -46,16 +51,10 @@ const getCurrentBranch = (cwd) => {
   }
 };
 
-/** @param {string} branch */
 const isFeatureBranch = (branch) => /^\d{3}-/.test(branch);
 
-/** @param {string} prompt */
 const shouldIgnorePrompt = (prompt) => IGNORE_PATTERNS.some((p) => p.test(prompt));
 
-/**
- * @param {string} content
- * @param {string|null} migrationId
- */
 const parseTasksFromContent = (content, migrationId) => {
   const pending = [];
   let completed = 0;
@@ -79,10 +78,6 @@ const parseTasksFromContent = (content, migrationId) => {
   return { pending, completed };
 };
 
-/**
- * @param {string} featureDir
- * @param {object} metaData
- */
 const parseTasksFromMigrations = (featureDir, metaData) => {
   const currentMigration = metaData.currentMigration;
 
@@ -128,7 +123,6 @@ const parseTasksFromMigrations = (featureDir, metaData) => {
   return { pending: allPending, completed: totalCompleted };
 };
 
-/** @param {string} featureDir */
 const parseTasksFromLegacy = (featureDir) => {
   const tasksFile = path.join(featureDir, 'tasks.md');
   if (!fs.existsSync(tasksFile)) return { pending: [], completed: 0 };
@@ -137,11 +131,6 @@ const parseTasksFromLegacy = (featureDir) => {
   return parseTasksFromContent(content, null);
 };
 
-/**
- * @param {string} cwd
- * @param {string} specsDir
- * @param {string} branch
- */
 const findFeatureDir = (cwd, specsDir, branch) => {
   const primaryDir = path.join(cwd, specsDir, branch);
   if (fs.existsSync(primaryDir)) return primaryDir;
@@ -152,18 +141,61 @@ const findFeatureDir = (cwd, specsDir, branch) => {
   return null;
 };
 
-/**
- * @param {string} branch
- * @param {string|null} currentMigration
- * @param {number} completed
- * @param {Array} pending
- */
-const buildSeddContext = (branch, currentMigration, completed, pending) => {
-  if (pending.length === 0) return null;
+const calculateAlignmentScore = (expectation, tasks) => {
+  if (!expectation || tasks.length === 0) return 0;
+
+  const tokens = expectation
+    .toLowerCase()
+    .replace(/[^\w\s]/g, '')
+    .split(/\s+/)
+    .filter((t) => t.length > 2 && !STOP_WORDS.has(t));
+
+  if (tokens.length === 0) return 100;
+
+  const taskText = tasks.map((t) => t.text.toLowerCase()).join(' ');
+  const matches = tokens.filter((token) => taskText.includes(token));
+
+  return Math.round((matches.length / tokens.length) * 100);
+};
+
+const getScoreEmoji = (score) => {
+  if (score >= 80) return '🟢';
+  if (score >= 60) return '🟡';
+  return '🔴';
+};
+
+const buildSeddContext = (branch, currentMigration, completed, pending, featureExpectation, migrationExpectation) => {
+  if (pending.length === 0 && !featureExpectation && !migrationExpectation) return null;
 
   const total = completed + pending.length;
   const migrationInfo = currentMigration ? ` | Migration: ${currentMigration}` : '';
 
+  let expectationBlock = '';
+  const activeExpectation = migrationExpectation || featureExpectation;
+
+  if (featureExpectation && migrationExpectation && featureExpectation !== migrationExpectation) {
+    expectationBlock = `
+🎯 **FEATURE:** ${featureExpectation}
+📍 **MIGRATION ${currentMigration}:** ${migrationExpectation}
+`;
+  } else if (activeExpectation) {
+    const prefix = migrationExpectation ? `📍 M${currentMigration}` : '🎯';
+    expectationBlock = `\n${prefix} **EXPECTATIVA:** ${activeExpectation}\n`;
+  }
+
+  let scoreBlock = '';
+  if (activeExpectation && pending.length > 0) {
+    const score = calculateAlignmentScore(activeExpectation, pending);
+    const emoji = getScoreEmoji(score);
+    scoreBlock = ` ${emoji} ~${score}%`;
+  }
+
+  if (pending.length === 0) {
+    return `<sedd-context>
+**Branch: ${branch}**${migrationInfo}${expectationBlock}
+</sedd-context>`;
+  }
+
   const tasksList = pending.slice(0, 5).map((t) => {
     const truncated = t.text.length > 60 ? `${t.text.substring(0, 60)}...` : t.text;
     return `- ${t.id}: ${truncated}`;
@@ -172,8 +204,8 @@ const buildSeddContext = (branch, currentMigration, completed, pending) => {
   const moreText = pending.length > 5 ? `\n... and ${pending.length - 5} more` : '';
 
   return `<sedd-context>
-**Branch: ${branch}**${migrationInfo} | Progress: ${completed}/${total} tasks
-
+**Branch: ${branch}**${migrationInfo} | Progress: ${completed}/${total} tasks${scoreBlock}
+${expectationBlock}
 Pending tasks:
 ${tasksList}${moreText}
 </sedd-context>`;
@@ -205,10 +237,18 @@ const main = () => {
       let pending = [];
       let completed = 0;
       let currentMigration = null;
+      let featureExpectation = null;
+      let migrationExpectation = null;
 
       if (fs.existsSync(metaFile)) {
         const metaData = JSON.parse(fs.readFileSync(metaFile, 'utf8'));
         currentMigration = metaData.currentMigration;
+        featureExpectation = metaData.expectation || null;
+
+        if (currentMigration && metaData.migrations?.[currentMigration]?.expectation) {
+          migrationExpectation = metaData.migrations[currentMigration].expectation;
+        }
+
         const result = parseTasksFromMigrations(featureDir, metaData);
         pending = result.pending;
         completed = result.completed;
@@ -218,12 +258,12 @@ const main = () => {
         completed = result.completed;
       }
 
-      const context = buildSeddContext(branch, currentMigration, completed, pending);
+      const context = buildSeddContext(branch, currentMigration, completed, pending, featureExpectation, migrationExpectation);
       if (context) {
         console.log(JSON.stringify({ systemMessage: '\n' + context + '\n' }));
       }
     } catch {
-      // Silent exit on parse errors
+      return;
     }
   });
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sedd",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "SEDD - Spec & Expectation Driven Development. A phase-based specification workflow for AI-assisted development.",
   "type": "module",
   "main": "dist/index.js",
@@ -14,7 +14,8 @@
     "templates",
     "commands",
     "scripts",
-    "hooks"
+    "hooks",
+    "README.md"
   ],
   "scripts": {
     "build": "tsc",

package/templates/acceptance-template.md

@@ -0,0 +1,64 @@
+# Acceptance Criteria - Migration {{MIGRATION_ID}}
+
+> Generated from expectation
+> Timestamp: {{TIMESTAMP}}
+> Branch: {{BRANCH}}
+
+## Expectativa
+
+> {{EXPECTATION}}
+
+---
+
+## Checklist de Aceite
+
+### Critérios Funcionais
+
+- [ ] **AC-001:** {{criterion_1}}
+  - Verificar: {{verification_steps}}
+
+- [ ] **AC-002:** {{criterion_2}}
+  - Verificar: {{verification_steps}}
+
+### Critérios de UX
+
+- [ ] **AC-UX-001:** {{ux_criterion}}
+  - Verificar: {{verification_steps}}
+
+### Critérios Técnicos
+
+- [ ] **AC-TECH-001:** {{technical_criterion}}
+  - Verificar: {{verification_steps}}
+
+---
+
+## Comandos de Verificação
+
+```bash
+# Comandos sugeridos para testar
+npm test
+npm run build
+```
+
+---
+
+## Sign-off
+
+| Critério | Status | Verificado Por | Data |
+|----------|--------|----------------|------|
+| AC-001 | pending | - | - |
+| AC-002 | pending | - | - |
+
+---
+
+## Notas
+
+_Adicione notas de verificação aqui_
+
+---
+
+## Relacionados
+
+- **Tasks:** Ver `tasks.md` nesta migration
+- **Clarificações:** Ver `clarify.md` nesta migration
+- **Fonte:** Expectativa capturada em /sedd.clarify