oden-forge 2.0.0

package/.claude/commands/oden/debug.md

@@ -0,0 +1,203 @@
+---
+allowed-tools: Bash, Read, Write, Edit, LS, Glob, Grep, Task
+description: Debugging - analizar errores y encontrar soluciones
+---
+
+# Oden Forge - Debug
+
+Herramientas de debugging para investigar y resolver errores.
+
+## Usage
+
+```
+/oden:debug [subcommand] [context]
+```
+
+## Subcomandos
+
+### `/oden:debug error [mensaje/stack]`
+
+Analiza un error y sugiere soluciones.
+
+**Usa:** `debugger` + `error-detective` agents
+
+**Input:**
+- Mensaje de error
+- Stack trace
+- Contexto del código
+
+**Output:**
+```
+╔══════════════════════════════════════════════════════════════╗
+║                    ERROR ANALYSIS                            ║
+╠══════════════════════════════════════════════════════════════╣
+║                                                              ║
+║  ERROR: TypeError: Cannot read property 'id' of undefined    ║
+║                                                              ║
+║  UBICACIÓN: src/services/orders.ts:145                       ║
+║                                                              ║
+║  CAUSA PROBABLE:                                             ║
+║  El objeto `order` es undefined cuando se intenta acceder    ║
+║  a `order.id`. Esto ocurre cuando:                           ║
+║  1. La query no encontró el order                            ║
+║  2. El ID pasado es inválido                                 ║
+║  3. Hay un problema de timing/async                          ║
+║                                                              ║
+║  SOLUCIÓN SUGERIDA:                                          ║
+║  ```typescript                                               ║
+║  const order = await getOrder(orderId);                      ║
+║  if (!order) {                                               ║
+║    throw new NotFoundError(`Order ${orderId} not found`);    ║
+║  }                                                           ║
+║  // Ahora es seguro acceder a order.id                       ║
+║  ```                                                         ║
+║                                                              ║
+║  ARCHIVOS A REVISAR:                                         ║
+║  - src/services/orders.ts:145                                ║
+║  - src/repositories/orderRepository.ts                       ║
+║                                                              ║
+╚══════════════════════════════════════════════════════════════╝
+```
+
+### `/oden:debug logs [file]`
+
+Analiza archivos de log para encontrar patrones de error.
+
+**Usa:** `error-detective` + `file-analyzer` agents
+
+**Analiza:**
+- Patrones de errores repetidos
+- Correlación temporal
+- Secuencia de eventos antes del error
+
+### `/oden:debug trace [function]`
+
+Traza el flujo de una función a través del código.
+
+**Usa:** `code-analyzer` agent
+
+**Output:**
+```
+TRACE: processOrder()
+
+1. src/api/orders.ts:45 → processOrder(orderId)
+   ↓
+2. src/services/orderService.ts:78 → validateOrder(order)
+   ↓
+3. src/validators/orderValidator.ts:23 → checkItems(items)
+   ↓
+4. src/validators/orderValidator.ts:45 → validateItem(item) ❌ ERROR HERE
+   ↓
+   Error: "Invalid item quantity"
+
+VARIABLES EN SCOPE:
+- orderId: "abc-123"
+- order: { id: "abc-123", items: [...] }
+- item: { id: "xyz", quantity: -1 } ← PROBLEMA: quantity negativo
+```
+
+### `/oden:debug perf [area]`
+
+Analiza problemas de performance.
+
+**Usa:** `performance-engineer` agent
+
+**Areas:**
+- `api` - Latencia de endpoints
+- `db` - Queries lentos
+- `render` - Performance de UI
+- `bundle` - Tamaño de bundle
+
+### `/oden:debug compare [branch]`
+
+Compara comportamiento entre branches para encontrar regresión.
+
+**Usa:** `code-analyzer` agent
+
+**Output:**
+```
+COMPARACIÓN: main vs feature/payments
+
+ARCHIVOS MODIFICADOS:
+- src/services/paymentService.ts (+45 -12)
+- src/utils/calculations.ts (+8 -3)
+
+CAMBIOS DE COMPORTAMIENTO:
+1. paymentService.calculateTotal()
+   - ANTES: Retornaba número
+   - AHORA: Retorna string (posible bug)
+
+2. calculations.roundAmount()
+   - ANTES: 2 decimales
+   - AHORA: 4 decimales (intencional?)
+
+TESTS AFECTADOS:
+- payment.test.ts:67 - Ahora falla
+- calculations.test.ts:34 - Ahora falla
+```
+
+---
+
+## Proceso de Debugging
+
+### 1. Reproducir
+```bash
+/oden:debug error "TypeError: Cannot read property..."
+```
+
+### 2. Localizar
+```bash
+/oden:debug trace functionName
+```
+
+### 3. Entender
+```bash
+/oden:debug logs app.log
+```
+
+### 4. Comparar (si regresión)
+```bash
+/oden:debug compare main
+```
+
+### 5. Resolver
+El agente sugiere el fix específico.
+
+---
+
+## Tips de Debugging
+
+### Para errores de runtime:
+1. Captura el stack trace completo
+2. Identifica la línea exacta
+3. Revisa el valor de variables en scope
+
+### Para errores intermitentes:
+1. Busca patrones en logs
+2. Considera race conditions
+3. Revisa timing de async operations
+
+### Para regresiones:
+1. Identifica el commit que introdujo el bug
+2. Compara comportamiento antes/después
+3. Revisa tests que deberían haber fallado
+
+---
+
+## Integración con Daily Log
+
+Los debugging sessions se documentan en `/oden:daily`:
+
+```markdown
+## 🐛 Issues Encontrados
+
+### Resueltos
+| Issue | Causa | Solución |
+|-------|-------|----------|
+| TypeError en orders.ts:145 | Order undefined | Agregué validación null check |
+
+### Pendientes
+| Issue | Severidad | Investigación |
+|-------|-----------|---------------|
+| Timeout en pagos | Alta | Posible N+1 query |
+```

package/.claude/commands/oden/epic.md

@@ -0,0 +1,224 @@
+---
+allowed-tools: Bash, Read, Write, LS, Task
+description: Convertir PRD a Epic tecnico con work streams, criterios de aceptacion y plan de implementacion
+---
+
+# Epic - Convert PRD to Technical Epic
+
+Convierte un PRD en un Epic tecnico con enfoque de implementacion, work streams paralelos y criterios de aceptacion.
+
+## Usage
+```
+/oden:epic <feature_name>
+```
+
+## Preflight
+
+Silently validate:
+
+1. **Feature name**: If not provided, show: "Usage: /oden:epic <feature_name>"
+
+2. **PRD exists**: Check `.claude/prds/$ARGUMENTS.md`
+   - If not found: "PRD not found. Create it first: /oden:prd $ARGUMENTS"
+
+3. **PRD frontmatter**: Verify has name, description, status, created
+   - If invalid: "Invalid PRD. Check: .claude/prds/$ARGUMENTS.md"
+
+4. **Existing epic**: Check `.claude/epics/$ARGUMENTS/epic.md`
+   - If exists, ask to overwrite
+
+5. **Directory**: Create `.claude/epics/$ARGUMENTS/` if needed
+
+## Context Gathering
+
+Silently scan for context to produce a better epic:
+
+1. **PRD** (required): Read `.claude/prds/$ARGUMENTS.md`
+   - Extract requirements, user stories, constraints, success criteria
+
+2. **Technical context** (if available):
+   - Read `docs/reference/technical-decisions.md` for stack, DB schema, architecture
+   - Read module specs in `docs/reference/modules/` for related specs
+
+3. **Other epics**: Scan `.claude/epics/` for related work
+   - Identify dependencies or shared infrastructure
+
+4. **Codebase structure**: Quick scan of `src/` or main source dirs
+   - Understand existing patterns, shared modules, naming conventions
+   - Identify code to reuse instead of building from scratch
+
+## Instructions
+
+You are a technical lead converting the PRD into an implementation epic for: **$ARGUMENTS**
+
+### Analysis Steps
+
+1. **Map requirements to technical components**
+   - Each functional requirement becomes one or more technical tasks
+   - Group by layer: data, backend/API, frontend/UI, infrastructure
+
+2. **Identify architecture decisions**
+   - New patterns or technologies needed
+   - Integration points with existing system
+   - Data model changes (new tables, columns, relations)
+
+3. **Define work streams**
+   - Independent streams that can run in parallel
+   - Streams that must be sequential
+   - Shared dependencies between streams
+
+4. **Estimate complexity**
+   - Per task: XS (< 2h), S (2-4h), M (4-8h), L (1-2d), XL (2-3d)
+   - Total timeline considering parallelism
+
+### Epic Creation
+
+#### File: `.claude/epics/$ARGUMENTS/epic.md`
+
+```markdown
+---
+name: $ARGUMENTS
+status: backlog
+created: [Real datetime from: date -u +"%Y-%m-%dT%H:%M:%SZ"]
+updated: [Same datetime]
+progress: 0%
+prd: .claude/prds/$ARGUMENTS.md
+github:
+---
+
+# Epic: [Descriptive Title]
+
+## Overview
+[2-3 sentences: what we're building, why, and the technical approach]
+
+## Architecture Decisions
+
+### Data Model
+[New or modified tables/collections, key relationships, indexes]
+
+### API Design
+[New endpoints, request/response contracts, auth requirements]
+
+### Frontend
+[New screens/components, state management, user flows]
+
+### Infrastructure
+[Deployment, caching, background jobs, external services]
+
+## Work Streams
+
+### Stream A: [Name] (e.g., Data Layer)
+**Parallel:** Yes
+**Files:** [file patterns this stream touches]
+
+Tasks:
+1. [Task description] - [Size: XS/S/M/L/XL]
+2. [Task description] - [Size]
+
+### Stream B: [Name] (e.g., API Layer)
+**Parallel:** After Stream A tasks 1-2
+**Files:** [file patterns]
+
+Tasks:
+1. [Task description] - [Size]
+2. [Task description] - [Size]
+
+### Stream C: [Name] (e.g., UI Layer)
+**Parallel:** After Stream B
+**Files:** [file patterns]
+
+Tasks:
+1. [Task description] - [Size]
+2. [Task description] - [Size]
+
+## Task Summary
+
+| # | Task | Stream | Size | Depends On | Parallel |
+|---|------|--------|------|------------|----------|
+| 1 | [desc] | A | M | - | Yes |
+| 2 | [desc] | A | S | 1 | Yes |
+| 3 | [desc] | B | L | 1 | Yes |
+| ... | ... | ... | ... | ... | ... |
+
+**Total tasks:** [count]
+**Estimated effort:** [sum]
+**Critical path:** [longest sequential chain]
+
+## Acceptance Criteria (Technical)
+
+- [ ] All data model changes migrated and tested
+- [ ] API endpoints return correct responses with validation
+- [ ] UI renders correctly on target devices/browsers
+- [ ] Error states handled gracefully
+- [ ] Performance within targets ([specific metrics])
+- [ ] Tests passing ([coverage target]%)
+
+## Risks & Mitigations
+
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+| [risk] | [H/M/L] | [mitigation] |
+
+## Dependencies
+
+- **Internal:** [other epics, shared modules]
+- **External:** [third-party APIs, services, credentials]
+```
+
+## Guidelines
+
+### Task Count
+- Aim for **5-10 tasks** per epic
+- If more than 10 tasks emerge, split into sub-epics
+- Each task should be completable in 1-3 days
+
+### Work Streams
+- Group tasks by the files/layers they touch
+- Streams that touch different files can run in parallel
+- Explicitly mark dependencies between streams
+- Name streams after the layer or concern (Data, API, UI, Tests)
+
+### Sizing
+- Be realistic. Include time for tests and edge cases
+- XS: Trivial change, config, rename (< 2h)
+- S: Single file change, simple logic (2-4h)
+- M: Multiple files, moderate logic, some edge cases (4-8h)
+- L: Cross-cutting change, complex logic, new patterns (1-2d)
+- XL: Architecture change, new subsystem, significant scope (2-3d)
+
+### Leveraging Existing Code
+- Before proposing new abstractions, check if similar patterns exist
+- Reference existing utilities, helpers, or shared modules
+- Prefer extending existing code over creating new silos
+
+## Quality Checks
+
+Before saving, verify:
+- [ ] Every PRD requirement maps to at least one task
+- [ ] No orphan tasks (every task traces back to a requirement)
+- [ ] Dependencies are logical (no circular references)
+- [ ] Parallel streams don't touch the same files
+- [ ] Sizes sum to a reasonable total
+- [ ] Acceptance criteria are testable
+
+## Output
+
+```
+Epic created: .claude/epics/$ARGUMENTS/epic.md
+
+Summary:
+  - [total] tasks across [stream_count] work streams
+  - Estimated effort: [total]
+  - Critical path: [length]
+  - [parallel_count] tasks can run in parallel
+
+Next: /oden:tasks $ARGUMENTS
+```
+
+## Important
+
+- Get REAL datetime: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
+- Never use placeholder dates
+- Keep task count to 10 or fewer
+- Focus on practical implementation, not theory
+- Reference existing code patterns when available

package/.claude/commands/oden/git.md

@@ -0,0 +1,259 @@
+---
+allowed-tools: Bash, Read, Write, LS, Glob, Grep, Task
+description: Git workflow - branches, PRs, y gestión de código
+---
+
+# Oden Forge - Git Workflow
+
+Comandos para gestión de Git siguiendo mejores prácticas.
+
+## Usage
+
+```
+/oden:git [subcommand]
+```
+
+## Subcomandos
+
+### `/oden:git start [feature-name]`
+
+Inicia trabajo en una nueva feature.
+
+**Usa:** `git-flow-manager` agent
+
+**Proceso:**
+1. Asegura que main está actualizado
+2. Crea branch `feature/{name}`
+3. Crea carpeta en `docs/development/current/{name}/`
+4. Inicializa README.md del feature
+
+```bash
+# Equivalente a:
+git checkout main
+git pull origin main
+git checkout -b feature/{name}
+mkdir -p docs/development/current/{name}
+```
+
+### `/oden:git sync`
+
+Sincroniza branch actual con main.
+
+**Proceso:**
+1. Fetch de origin
+2. Rebase sobre main
+3. Resuelve conflictos si los hay
+
+```bash
+git fetch origin
+git rebase origin/main
+```
+
+### `/oden:git pr`
+
+Prepara y crea Pull Request.
+
+**Usa:** `git-flow-manager` + `code-reviewer` agents
+
+**Proceso:**
+1. Ejecuta `/oden:review` automáticamente
+2. Genera descripción de PR basada en:
+   - Commits del branch
+   - DAY_X_COMPLETED.md files
+   - Spec del módulo
+3. Crea PR en GitHub
+
+**Template de PR:**
+```markdown
+## Summary
+{Resumen de cambios basado en commits}
+
+## Changes
+- {Lista de cambios principales}
+
+## Spec Reference
+- `docs/reference/modules/{module}-spec.md`
+
+## Testing
+- [ ] Unit tests added/updated
+- [ ] Integration tests passing
+- [ ] Manual testing completed
+
+## Screenshots
+{Si hay cambios de UI}
+
+## Checklist
+- [ ] Code follows project conventions
+- [ ] Self-review completed
+- [ ] Documentation updated
+```
+
+### `/oden:git status`
+
+Muestra estado detallado del proyecto.
+
+**Output:**
+```
+╔══════════════════════════════════════════════════════════════╗
+║                      GIT STATUS                              ║
+╠══════════════════════════════════════════════════════════════╣
+║                                                              ║
+║  BRANCH: feature/payments                                    ║
+║  BASE: main (3 commits behind)                               ║
+║                                                              ║
+║  COMMITS EN BRANCH: 8                                        ║
+║  ├─ abc1234 feat: Add payment form                           ║
+║  ├─ def5678 feat: Integrate Stripe                           ║
+║  ├─ ghi9012 fix: Handle declined cards                       ║
+║  └─ ... (5 more)                                             ║
+║                                                              ║
+║  ARCHIVOS MODIFICADOS: 12                                    ║
+║  ├─ src/components/PaymentForm.tsx                           ║
+║  ├─ src/services/stripeService.ts                            ║
+║  └─ ... (10 more)                                            ║
+║                                                              ║
+║  ESTADO:                                                     ║
+║  ├─ Staged: 2 files                                          ║
+║  ├─ Modified: 3 files                                        ║
+║  └─ Untracked: 1 file                                        ║
+║                                                              ║
+║  DAILY LOGS: 3 (DAY_1 → DAY_3)                              ║
+║                                                              ║
+╚══════════════════════════════════════════════════════════════╝
+```
+
+### `/oden:git log`
+
+Muestra historial con contexto de proyecto.
+
+**Output:**
+```
+HISTORIAL DE FEATURE: payments
+
+Semana 1:
+├─ DAY_1 (2024-01-15)
+│  ├─ abc1234 feat: Add payment form
+│  └─ def5678 feat: Integrate Stripe
+│
+├─ DAY_2 (2024-01-16)
+│  ├─ ghi9012 fix: Handle declined cards
+│  └─ jkl3456 test: Add payment tests
+│
+└─ DAY_3 (2024-01-17)
+   └─ mno7890 refactor: Extract payment utils
+
+Total: 5 commits, 12 files changed
+Progress: 60% of spec completed
+```
+
+### `/oden:git finish`
+
+Finaliza feature y limpia.
+
+**Proceso:**
+1. Verifica PR merged
+2. Mueve docs a `completed/`
+3. Elimina branch local
+4. Actualiza main
+
+```bash
+git checkout main
+git pull origin main
+git branch -d feature/{name}
+mv docs/development/current/{name} docs/development/completed/
+```
+
+---
+
+## Convenciones de Commits
+
+### Formato
+```
+{type}: {description}
+
+{body opcional}
+```
+
+### Types
+- `feat`: Nueva funcionalidad
+- `fix`: Bug fix
+- `refactor`: Refactoring sin cambio de funcionalidad
+- `test`: Tests
+- `docs`: Documentación
+- `style`: Formato, sin cambio de código
+- `chore`: Tareas de mantenimiento
+
+### Ejemplos
+```
+feat: Add payment processing with Stripe
+fix: Handle edge case when order is empty
+refactor: Extract validation logic to separate module
+test: Add unit tests for payment service
+docs: Update API documentation for payments
+```
+
+---
+
+## Branch Naming
+
+### Features
+```
+feature/{module}-{description}
+```
+Ejemplos:
+- `feature/auth-social-login`
+- `feature/orders-bulk-actions`
+- `feature/payments-stripe`
+
+### Fixes
+```
+fix/{issue-number}-{description}
+```
+Ejemplos:
+- `fix/123-login-redirect`
+- `fix/456-payment-timeout`
+
+### Hotfixes
+```
+hotfix/{description}
+```
+Para fixes urgentes en producción.
+
+---
+
+## Integración con Daily Log
+
+Los commits del día se documentan en `/oden:daily`:
+
+```markdown
+### Commits del Día
+```
+abc1234 feat: Add payment form
+def5678 feat: Integrate Stripe
+ghi9012 fix: Handle declined cards
+```
+```
+
+---
+
+## Flujo Típico
+
+```bash
+# 1. Iniciar feature
+/oden:git start payments
+
+# 2. Durante desarrollo (cada día)
+git add .
+git commit -m "feat: Add payment form"
+/oden:daily
+
+# 3. Sincronizar periódicamente
+/oden:git sync
+
+# 4. Antes de PR
+/oden:review
+/oden:git pr
+
+# 5. Después de merge
+/oden:git finish
+```