adi_dev_workflow 1.1.1 → 1.3.0

package/frameworks/skills/sdd-task-plan-expert-workspace/iteration-1/eval-1-happy-path/without_skill/outputs/transcript.md

@@ -1,30 +1,30 @@
-# Transcript of Tool Calls
-
-## Call 1: ToolSearch
-- **Query:** `select:Read,Write,Glob`
-- **Purpose:** Load the Read, Write, and Glob tools for file operations.
-
-## Call 2: Read
-- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\docs\feature-user\v1\spec_tech.md`
-- **Purpose:** Read the approved SPEC_TECH document to understand all technical requirements for the user feature.
-- **Result:** File was large (914 lines). First 41 lines loaded in preview, full content saved to persistent output.
-
-## Call 3: Read (continued)
-- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\docs\feature-user\v1\spec_tech.md`
-- **Offset:** 42
-- **Purpose:** Read the remainder of the SPEC_TECH starting from line 42 (architecture section onwards).
-- **Result:** Read complete document including all 16 sections: architecture, data structures, user stories, business rules, technical flows, proto contracts, persistence, security (identity package), error handling, configuration, logging, test strategy, and file listing.
-
-## Call 4: Glob
-- **Pattern:** `internal/**/*.go`
-- **Path:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review`
-- **Purpose:** Understand the current codebase structure and existing files to properly plan which files need to be created vs modified.
-- **Result:** Found 17 existing Go files across handler, infra (config, database, di, grpc, logger), repository, and service packages.
-
-## Call 5: Write
-- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\.claude\skills\sdd-task-plan-expert-workspace\iteration-1\eval-1-happy-path\without_skill\outputs\response.md`
-- **Purpose:** Save the generated Task Plan document with 17 tasks organized in 7 phases.
-
-## Call 6: Write
-- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\.claude\skills\sdd-task-plan-expert-workspace\iteration-1\eval-1-happy-path\without_skill\outputs\transcript.md`
-- **Purpose:** Save this transcript of tool calls.
+# Transcript of Tool Calls
+
+## Call 1: ToolSearch
+- **Query:** `select:Read,Write,Glob`
+- **Purpose:** Load the Read, Write, and Glob tools for file operations.
+
+## Call 2: Read
+- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\docs\feature-user\v1\spec_tech.md`
+- **Purpose:** Read the approved SPEC_TECH document to understand all technical requirements for the user feature.
+- **Result:** File was large (914 lines). First 41 lines loaded in preview, full content saved to persistent output.
+
+## Call 3: Read (continued)
+- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\docs\feature-user\v1\spec_tech.md`
+- **Offset:** 42
+- **Purpose:** Read the remainder of the SPEC_TECH starting from line 42 (architecture section onwards).
+- **Result:** Read complete document including all 16 sections: architecture, data structures, user stories, business rules, technical flows, proto contracts, persistence, security (identity package), error handling, configuration, logging, test strategy, and file listing.
+
+## Call 4: Glob
+- **Pattern:** `internal/**/*.go`
+- **Path:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review`
+- **Purpose:** Understand the current codebase structure and existing files to properly plan which files need to be created vs modified.
+- **Result:** Found 17 existing Go files across handler, infra (config, database, di, grpc, logger), repository, and service packages.
+
+## Call 5: Write
+- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\.claude\skills\sdd-task-plan-expert-workspace\iteration-1\eval-1-happy-path\without_skill\outputs\response.md`
+- **Purpose:** Save the generated Task Plan document with 17 tasks organized in 7 phases.
+
+## Call 6: Write
+- **File:** `H:\repos\flutter_experience\04_2026\cb_vakinhaburger_2025\vakinha-api-review\.claude\skills\sdd-task-plan-expert-workspace\iteration-1\eval-1-happy-path\without_skill\outputs\transcript.md`
+- **Purpose:** Save this transcript of tool calls.

package/frameworks/skills/sdd-task-plan-expert-workspace/iteration-1/eval-1-happy-path/without_skill/timing.json

@@ -1,5 +1,5 @@
-{
-  "total_tokens": 40363,
-  "duration_ms": 141273,
-  "total_duration_seconds": 141.3
-}
+{
+  "total_tokens": 40363,
+  "duration_ms": 141273,
+  "total_duration_seconds": 141.3
+}

package/frameworks/skills/sdd-task-plan-expert-workspace/iteration-1/eval-2-spec-simples/eval_metadata.json

@@ -1,12 +1,12 @@
-{
-  "eval_id": 2,
-  "eval_name": "spec-tech-simples-alteracao-pontual",
-  "prompt": "Preciso de um TASK PLAN para esta feature simples. O SPEC_TECH aprovado esta abaixo:\n\n---\n# SPEC_TECH — Adicionar Telefone ao Usuario v1\n\n## 1. Identificacao\n| Campo | Valor |\n|-------|-------|\n| **Feature/Projeto** | Adicionar Telefone ao Modulo de Usuario |\n| **Versao** | v1 |\n| **Data** | 2026-03-07 |\n| **PRD** | docs/feature-telefone-usuario/v1/prd.md |\n\n## 2. Resumo Tecnico\nAdicionar campo `telefone` (opcional) a tabela `usuarios` e expor via gRPC nos endpoints CreateUser e UpdateUser.\n\n## 3. Definicoes Tecnicas\n\n### 3.1 Banco de Dados\n- Nova migracao: `ALTER TABLE usuarios ADD COLUMN telefone TEXT;`\n\n### 3.2 SQLC\n- Atualizar queries CreateUser e UpdateUser para incluir coluna `telefone`\n\n### 3.3 Repository\n- Adicionar campo `Phone` ao modelo User\n- Mapear `telefone` (banco) para `Phone` (Go)\n\n### 3.4 Service\n- Aceitar campo opcional phone em CreateUser e UpdateUser\n- Validacao: se informado, deve ter entre 10 e 15 caracteres\n\n### 3.5 Handler gRPC\n- Adicionar campo `phone` nas mensagens proto CreateUserRequest, UpdateUserRequest e User\n\n### 3.6 Proto\n- Atualizar user.proto com campo `string phone = X;`\n\n## 4. User Stories Relacionadas\n- US-10: Como usuario, quero informar meu telefone para receber notificacoes por SMS\n---",
-  "assertions": [
-    {"id": "b1", "text": "Gera um numero proporcional de tasks (entre 3 e 6) — nao over-engineers com tasks demais para uma alteracao simples", "type": "llm_judge"},
-    {"id": "b2", "text": "Respeita a ordem de dependencias das camadas (migracao > SQLC > repository > service > handler > proto)", "type": "llm_judge"},
-    {"id": "b3", "text": "Mapeia a US-10 na tabela de rastreabilidade do task_plan", "type": "llm_judge"},
-    {"id": "b4", "text": "Cada task segue o template completo (secoes 1-8) ou marca secoes N/A com justificativa", "type": "llm_judge"},
-    {"id": "b5", "text": "Salva task_plan.md como documento de REFERENCIA (sem corpo detalhado de tasks dentro dele)", "type": "llm_judge"}
-  ]
-}
+{
+  "eval_id": 2,
+  "eval_name": "spec-tech-simples-alteracao-pontual",
+  "prompt": "Preciso de um TASK PLAN para esta feature simples. O SPEC_TECH aprovado esta abaixo:\n\n---\n# SPEC_TECH — Adicionar Telefone ao Usuario v1\n\n## 1. Identificacao\n| Campo | Valor |\n|-------|-------|\n| **Feature/Projeto** | Adicionar Telefone ao Modulo de Usuario |\n| **Versao** | v1 |\n| **Data** | 2026-03-07 |\n| **PRD** | docs/feature-telefone-usuario/v1/prd.md |\n\n## 2. Resumo Tecnico\nAdicionar campo `telefone` (opcional) a tabela `usuarios` e expor via gRPC nos endpoints CreateUser e UpdateUser.\n\n## 3. Definicoes Tecnicas\n\n### 3.1 Banco de Dados\n- Nova migracao: `ALTER TABLE usuarios ADD COLUMN telefone TEXT;`\n\n### 3.2 SQLC\n- Atualizar queries CreateUser e UpdateUser para incluir coluna `telefone`\n\n### 3.3 Repository\n- Adicionar campo `Phone` ao modelo User\n- Mapear `telefone` (banco) para `Phone` (Go)\n\n### 3.4 Service\n- Aceitar campo opcional phone em CreateUser e UpdateUser\n- Validacao: se informado, deve ter entre 10 e 15 caracteres\n\n### 3.5 Handler gRPC\n- Adicionar campo `phone` nas mensagens proto CreateUserRequest, UpdateUserRequest e User\n\n### 3.6 Proto\n- Atualizar user.proto com campo `string phone = X;`\n\n## 4. User Stories Relacionadas\n- US-10: Como usuario, quero informar meu telefone para receber notificacoes por SMS\n---",
+  "assertions": [
+    {"id": "b1", "text": "Gera um numero proporcional de tasks (entre 3 e 6) — nao over-engineers com tasks demais para uma alteracao simples", "type": "llm_judge"},
+    {"id": "b2", "text": "Respeita a ordem de dependencias das camadas (migracao > SQLC > repository > service > handler > proto)", "type": "llm_judge"},
+    {"id": "b3", "text": "Mapeia a US-10 na tabela de rastreabilidade do task_plan", "type": "llm_judge"},
+    {"id": "b4", "text": "Cada task segue o template completo (secoes 1-8) ou marca secoes N/A com justificativa", "type": "llm_judge"},
+    {"id": "b5", "text": "Salva task_plan.md como documento de REFERENCIA (sem corpo detalhado de tasks dentro dele)", "type": "llm_judge"}
+  ]
+}

package/frameworks/skills/sdd-task-plan-expert-workspace/iteration-1/eval-2-spec-simples/with_skill/grading.json

@@ -1,32 +1,32 @@
-{
-  "eval_id": 2,
-  "eval_name": "spec-tech-simples-alteracao-pontual",
-  "configuration": "with_skill",
-  "expectations": [
-    {
-      "text": "Gera um numero proporcional de tasks (entre 3 e 6) — nao over-engineers com tasks demais para uma alteracao simples",
-      "passed": true,
-      "evidence": "Gerou exatamente 6 tasks (T1-T6), dentro da faixa esperada de 3-6. Proporcional a complexidade da feature."
-    },
-    {
-      "text": "Respeita a ordem de dependencias das camadas (migracao > SQLC > repository > service > handler > proto)",
-      "passed": true,
-      "evidence": "Dependencias: T1(migracao)->T2(SQLC)->T3(repo)->T4(service)->T6(handler), T5(proto)->T6(handler). Proto em paralelo com migracao. Ordem correta."
-    },
-    {
-      "text": "Mapeia a US-10 na tabela de rastreabilidade do task_plan",
-      "passed": true,
-      "evidence": "Secao 5 do task_plan contem tabela de rastreabilidade mapeando US-10 para todas as 6 tasks com definicoes tecnicas correspondentes."
-    },
-    {
-      "text": "Cada task segue o template completo (secoes 1-8) ou marca secoes N/A com justificativa",
-      "passed": true,
-      "evidence": "Todas as 6 tasks (T1-T6) seguem o template com secoes 1-8 preenchidas. Secoes N/A possuem justificativa (ex: T1 secao 6.1: 'N/A -- migracao SQL nao possui testes unitarios isolados')."
-    },
-    {
-      "text": "Salva task_plan.md como documento de REFERENCIA (sem corpo detalhado de tasks dentro dele)",
-      "passed": true,
-      "evidence": "O task_plan contem apenas identificacao, macro-fases, tabela de tasks com IDs/links, rastreabilidade, dependencias e criterios. Tasks detalhadas estao separadas (T1-T6). Embora tudo esteja em um arquivo de output por ser eval, a estrutura esta correta."
-    }
-  ]
-}
+{
+  "eval_id": 2,
+  "eval_name": "spec-tech-simples-alteracao-pontual",
+  "configuration": "with_skill",
+  "expectations": [
+    {
+      "text": "Gera um numero proporcional de tasks (entre 3 e 6) — nao over-engineers com tasks demais para uma alteracao simples",
+      "passed": true,
+      "evidence": "Gerou exatamente 6 tasks (T1-T6), dentro da faixa esperada de 3-6. Proporcional a complexidade da feature."
+    },
+    {
+      "text": "Respeita a ordem de dependencias das camadas (migracao > SQLC > repository > service > handler > proto)",
+      "passed": true,
+      "evidence": "Dependencias: T1(migracao)->T2(SQLC)->T3(repo)->T4(service)->T6(handler), T5(proto)->T6(handler). Proto em paralelo com migracao. Ordem correta."
+    },
+    {
+      "text": "Mapeia a US-10 na tabela de rastreabilidade do task_plan",
+      "passed": true,
+      "evidence": "Secao 5 do task_plan contem tabela de rastreabilidade mapeando US-10 para todas as 6 tasks com definicoes tecnicas correspondentes."
+    },
+    {
+      "text": "Cada task segue o template completo (secoes 1-8) ou marca secoes N/A com justificativa",
+      "passed": true,
+      "evidence": "Todas as 6 tasks (T1-T6) seguem o template com secoes 1-8 preenchidas. Secoes N/A possuem justificativa (ex: T1 secao 6.1: 'N/A -- migracao SQL nao possui testes unitarios isolados')."
+    },
+    {
+      "text": "Salva task_plan.md como documento de REFERENCIA (sem corpo detalhado de tasks dentro dele)",
+      "passed": true,
+      "evidence": "O task_plan contem apenas identificacao, macro-fases, tabela de tasks com IDs/links, rastreabilidade, dependencias e criterios. Tasks detalhadas estao separadas (T1-T6). Embora tudo esteja em um arquivo de output por ser eval, a estrutura esta correta."
+    }
+  ]
+}