@the-bearded-bear/claude-craft 3.0.0

package/Project/i18n/fr/commands/generate-tech-spec.md

@@ -0,0 +1,285 @@
+---
+name: generate-tech-spec
+description: Generate a Technical Specification from PRD and architecture analysis
+arguments:
+  - name: prd
+    description: Path to PRD (default project-management/prd.md)
+    required: false
+  - name: output
+    description: Output path (default project-management/tech-spec.md)
+    required: false
+---
+
+# /project:generate-tech-spec
+
+## Mission
+
+Generate a comprehensive Technical Specification document by analyzing the PRD, existing codebase, and architectural requirements. This document serves as the technical blueprint for implementation.
+
+## Prerequisites
+
+- PRD exists at `project-management/prd.md` or specified path
+- Project directory with codebase (for existing projects)
+- Technology stack identified
+
+## Workflow
+
+### Phase 1: PRD Analysis
+
+```
+╔══════════════════════════════════════════════════════════╗
+║           TECH SPEC GENERATION - ANALYSIS                 ║
+╠══════════════════════════════════════════════════════════╣
+║ Loading PRD and analyzing requirements...                 ║
+╚══════════════════════════════════════════════════════════╝
+```
+
+**Extract from PRD:**
+- Functional requirements (features to build)
+- Non-functional requirements (performance, security, scalability)
+- Personas and user journeys
+- Constraints and assumptions
+- Integration requirements
+
+### Phase 2: Codebase Analysis
+
+If existing codebase:
+
+```
+╔══════════════════════════════════════════════════════════╗
+║               CODEBASE ANALYSIS                           ║
+╠══════════════════════════════════════════════════════════╣
+║ Detected Stack:                                           ║
+║ ├── Backend: Symfony 7.x (PHP 8.3)                        ║
+║ ├── Frontend: React 18.x (TypeScript)                     ║
+║ ├── Database: PostgreSQL 16                               ║
+║ ├── Cache: Redis 7.x                                      ║
+║ └── Infrastructure: Docker + Kubernetes                   ║
+║                                                           ║
+║ Existing Patterns:                                        ║
+║ ├── Architecture: Clean Architecture (Hexagonal)          ║
+║ ├── API Style: REST with JSON:API                         ║
+║ ├── Auth: JWT with refresh tokens                         ║
+║ └── Testing: PHPUnit + Jest + Playwright                  ║
+╚══════════════════════════════════════════════════════════╝
+```
+
+For new projects, ask:
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ QUESTIONS - Technology Stack                             │
+├─────────────────────────────────────────────────────────┤
+│ 1. Preferred backend framework? (Symfony/Laravel/Node)   │
+│ 2. Frontend framework? (React/Vue/Angular/None)          │
+│ 3. Database preference? (PostgreSQL/MySQL/MongoDB)       │
+│ 4. Deployment target? (Docker/K8s/Serverless/VPS)        │
+│ 5. Any existing integrations to consider?                │
+└─────────────────────────────────────────────────────────┘
+```
+
+### Phase 3: Architecture Design
+
+**Ask clarifying questions:**
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ QUESTIONS - Architecture Decisions                       │
+├─────────────────────────────────────────────────────────┤
+│ 1. Monolith or Microservices?                            │
+│ 2. API style preference? (REST/GraphQL/gRPC)             │
+│ 3. Expected scale? (users, requests/sec)                 │
+│ 4. Real-time features needed? (WebSockets/SSE)           │
+│ 5. File storage requirements? (S3/local/CDN)             │
+│ 6. Background job processing needs?                      │
+│ 7. Third-party integrations? (payments, email, etc.)     │
+└─────────────────────────────────────────────────────────┘
+```
+
+### Phase 4: Data Model Design
+
+Based on PRD entities, design the data model:
+
+```mermaid
+erDiagram
+    USER ||--o{ ORDER : places
+    USER {
+        uuid id PK
+        string email UK
+        string name
+        enum role
+    }
+    ORDER ||--|{ ORDER_ITEM : contains
+```
+
+**Validate with user:**
+- Entity relationships correct?
+- Missing entities?
+- Indexing strategy appropriate?
+
+### Phase 5: API Design
+
+Generate API endpoints based on requirements:
+
+```
+╔══════════════════════════════════════════════════════════╗
+║               PROPOSED API ENDPOINTS                      ║
+╠══════════════════════════════════════════════════════════╣
+║ Authentication:                                           ║
+║   POST /api/v1/auth/login                                 ║
+║   POST /api/v1/auth/register                              ║
+║   POST /api/v1/auth/refresh                               ║
+║                                                           ║
+║ Users (from Persona: Admin):                              ║
+║   GET    /api/v1/users                                    ║
+║   GET    /api/v1/users/{id}                               ║
+║   PUT    /api/v1/users/{id}                               ║
+║   DELETE /api/v1/users/{id}                               ║
+║                                                           ║
+║ [Based on FR-001] Orders:                                 ║
+║   GET    /api/v1/orders                                   ║
+║   POST   /api/v1/orders                                   ║
+║   GET    /api/v1/orders/{id}                              ║
+╚══════════════════════════════════════════════════════════╝
+```
+
+### Phase 6: Security & Performance
+
+**Security considerations based on NFRs:**
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ SECURITY CHECKLIST                                       │
+├─────────────────────────────────────────────────────────┤
+│ ✅ Authentication: JWT with HttpOnly cookies              │
+│ ✅ Authorization: RBAC with policies                      │
+│ ✅ Data encryption: AES-256 at rest, TLS 1.3 in transit  │
+│ ✅ Input validation: DTO validation + sanitization        │
+│ ✅ Rate limiting: 100 req/min per user                    │
+│ ✅ OWASP Top 10: Mitigations defined                      │
+│ ⚠️  GDPR compliance: Needs data retention policy          │
+└─────────────────────────────────────────────────────────┘
+```
+
+### Phase 7: Generate Tech Spec
+
+Compile all analysis into the Tech Spec document:
+
+1. **Load Template**: `./templates/tech-spec.md`
+2. **Generate Diagrams**: C4, ERD, sequence diagrams
+3. **Document APIs**: Endpoints, payloads, errors
+4. **Define ADRs**: Architecture Decision Records
+5. **Plan Testing**: Strategy and coverage targets
+6. **Design Deployment**: CI/CD and environments
+
+### Phase 8: Review & ADR Creation
+
+```
+╔══════════════════════════════════════════════════════════╗
+║                  TECH SPEC GENERATED                      ║
+╠══════════════════════════════════════════════════════════╣
+║ Output: project-management/tech-spec.md                   ║
+║                                                           ║
+║ Sections completed:                                       ║
+║ ✅ Architecture Overview (C4 diagrams)                    ║
+║ ✅ Technology Stack                                       ║
+║ ✅ Data Model (ERD + schemas)                             ║
+║ ✅ API Design (24 endpoints)                              ║
+║ ✅ Security Considerations                                ║
+║ ✅ Performance & Scalability                              ║
+║ ✅ Testing Strategy                                       ║
+║ ✅ Deployment & CI/CD                                     ║
+║ ✅ Monitoring & Observability                             ║
+║                                                           ║
+║ ADRs Created:                                             ║
+║ • ADR-001: Database choice (PostgreSQL)                   ║
+║ • ADR-002: API style (REST)                               ║
+║ • ADR-003: Authentication (JWT)                           ║
+╚══════════════════════════════════════════════════════════╝
+```
+
+**Offer iterations:**
+- "Want me to detail the caching strategy?"
+- "Should I expand the API documentation?"
+- "Need more detail on the deployment pipeline?"
+
+## Output Structure
+
+```
+project-management/
+├── tech-spec.md              # Generated Tech Spec
+├── architecture/
+│   ├── c4-context.md         # C4 Context diagram
+│   ├── c4-container.md       # C4 Container diagram
+│   └── erd.md                # Entity Relationship Diagram
+└── docs/
+    └── adr/
+        ├── ADR-001-database.md
+        ├── ADR-002-api-style.md
+        └── ADR-003-auth.md
+```
+
+## Integration with Workflow
+
+After Tech Spec generation:
+
+```
+╔══════════════════════════════════════════════════════════╗
+║                     NEXT STEPS                            ║
+╠══════════════════════════════════════════════════════════╣
+║ Tech Spec is ready! Recommended next actions:             ║
+║                                                           ║
+║ 1. /project:generate-backlog   → Create sprint backlog    ║
+║ 2. /workflow:implement         → Start implementation     ║
+║ 3. /project:decompose-tasks    → Break down first sprint  ║
+╚══════════════════════════════════════════════════════════╝
+```
+
+## Example Session
+
+```
+User: /project:generate-tech-spec
+
+Claude: Starting Tech Spec generation...
+
+📄 Loading PRD from project-management/prd.md
+Found 12 functional requirements, 8 non-functional requirements
+
+📂 Analyzing existing codebase...
+Detected: Symfony 7.x + React 18 + PostgreSQL
+
+Let me confirm some architecture decisions:
+
+❓ Architecture
+1. Current API is REST. Keep REST or migrate to GraphQL?
+> User: Keep REST, it works well for us
+
+2. Expected concurrent users at peak?
+> User: Around 500-1000 users
+
+3. Any specific third-party integrations?
+> User: Stripe for payments, SendGrid for emails
+
+[... interactive Q&A continues ...]
+
+✅ Tech Spec Generated!
+Output: project-management/tech-spec.md
+
+Created:
+- C4 diagrams (context + container)
+- ERD with 8 entities
+- 24 API endpoints documented
+- 3 ADRs (database, API style, auth)
+- Testing strategy (80% coverage target)
+- CI/CD pipeline design
+
+Ready to generate the backlog?
+```
+
+## Related Commands
+
+- `/project:generate-prd` - Generate Product Requirements Document
+- `/project:generate-backlog` - Create SCRUM backlog
+- `/common:architecture-decision` - Create individual ADRs
+- `/workflow:design` - Full solutioning phase workflow
+- `/workflow:implement` - Start implementation phase

package/Project/i18n/fr/commands/list-epics.md

@@ -0,0 +1,95 @@
+---
+description: Lister les EPICs
+argument-hint: [arguments]
+---
+
+# Lister les EPICs
+
+Afficher la liste de tous les EPICs avec leur statut et progression.
+
+## Arguments
+
+$ARGUMENTS (optionnel, format: [statut] [priorité])
+- **Statut** (optionnel): todo, in-progress, blocked, done, all (défaut: all)
+- **Priorité** (optionnel): high, medium, low
+
+## Processus
+
+### Étape 1: Lire les EPICs
+
+1. Scanner le répertoire `project-management/backlog/epics/`
+2. Lire chaque fichier EPIC-XXX-*.md
+3. Extraire les métadonnées de chaque EPIC
+
+### Étape 2: Filtrer (si arguments)
+
+Appliquer les filtres demandés:
+- Par statut
+- Par priorité
+
+### Étape 3: Calculer les statistiques
+
+Pour chaque EPIC:
+- Compter les US totales
+- Compter les US par statut
+- Calculer le pourcentage de progression
+
+### Étape 4: Afficher
+
+Générer un tableau formaté avec les résultats.
+
+## Format de Sortie
+
+```
+📋 EPICs du Projet
+
+| ID | Nom | Statut | Priorité | US | Progression |
+|----|-----|--------|----------|-----|-------------|
+| EPIC-001 | Authentification | 🟡 In Progress | High | 5 | ████░░░░░░ 40% |
+| EPIC-002 | Catalogue | 🔴 To Do | Medium | 8 | ░░░░░░░░░░ 0% |
+| EPIC-003 | Panier | 🔴 To Do | High | 6 | ░░░░░░░░░░ 0% |
+
+───────────────────────────────────────────────────
+Résumé: 3 EPICs | 🔴 2 To Do | 🟡 1 In Progress | 🟢 0 Done
+```
+
+## Format Compact (si beaucoup d'EPICs)
+
+```
+📋 EPICs (12 total)
+
+🔴 To Do (5):
+   EPIC-002, EPIC-003, EPIC-004, EPIC-007, EPIC-010
+
+🟡 In Progress (4):
+   EPIC-001 (40%), EPIC-005 (60%), EPIC-008 (25%), EPIC-011 (80%)
+
+⏸️ Blocked (1):
+   EPIC-006 - Bloqué par dépendance externe
+
+🟢 Done (2):
+   EPIC-009 ✓, EPIC-012 ✓
+```
+
+## Exemples
+
+```
+# Lister tous les EPICs
+/project:list-epics
+
+# Lister les EPICs en cours
+/project:list-epics in-progress
+
+# Lister les EPICs priorité haute
+/project:list-epics all high
+
+# Lister les EPICs bloqués
+/project:list-epics blocked
+```
+
+## Détails d'un EPIC
+
+Pour voir les détails d'un EPIC spécifique, suggérer:
+```
+Voir les détails: cat project-management/backlog/epics/EPIC-001-*.md
+```

package/Project/i18n/fr/commands/list-stories.md

@@ -0,0 +1,120 @@
+---
+description: Lister les User Stories
+argument-hint: [arguments]
+---
+
+# Lister les User Stories
+
+Afficher la liste des User Stories avec filtrage par EPIC, Sprint ou Statut.
+
+## Arguments
+
+$ARGUMENTS (optionnel, format: [filtre] [valeur])
+- **epic EPIC-XXX**: Filtrer par EPIC
+- **sprint N**: Filtrer par sprint
+- **status STATUS**: Filtrer par statut (todo, in-progress, blocked, done)
+- **backlog**: Afficher uniquement les US non assignées à un sprint
+
+## Processus
+
+### Étape 1: Lire les User Stories
+
+1. Scanner le répertoire `project-management/backlog/user-stories/`
+2. Lire chaque fichier US-XXX-*.md
+3. Extraire les métadonnées de chaque US
+
+### Étape 2: Filtrer
+
+Appliquer les filtres selon $ARGUMENTS:
+- Par EPIC parent
+- Par sprint assigné
+- Par statut
+- Non assignées (backlog)
+
+### Étape 3: Calculer les statistiques
+
+Pour chaque US:
+- Compter les tasks totales
+- Compter les tasks par statut
+- Calculer le pourcentage de progression
+
+### Étape 4: Afficher
+
+Générer un tableau formaté groupé par EPIC ou Sprint selon le contexte.
+
+## Format de Sortie - Par EPIC
+
+```
+📖 User Stories - EPIC-001: Authentification
+
+| ID | Nom | Sprint | Statut | Points | Tasks | Progression |
+|----|-----|--------|--------|--------|-------|-------------|
+| US-001 | Login utilisateur | Sprint 1 | 🟡 In Progress | 5 | 4/6 | ██████░░░░ 67% |
+| US-002 | Inscription | Sprint 1 | 🔴 To Do | 3 | 0/5 | ░░░░░░░░░░ 0% |
+| US-003 | Mot de passe oublié | Backlog | 🔴 To Do | 3 | - | - |
+
+───────────────────────────────────────────────────
+Total: 3 US | 11 points | 🔴 2 | 🟡 1 | 🟢 0
+```
+
+## Format de Sortie - Par Sprint
+
+```
+📖 User Stories - Sprint 1
+
+| ID | EPIC | Nom | Statut | Points | Tasks | Progression |
+|----|------|-----|--------|--------|-------|-------------|
+| US-001 | EPIC-001 | Login utilisateur | 🟡 In Progress | 5 | 4/6 | ██████░░░░ 67% |
+| US-002 | EPIC-001 | Inscription | 🔴 To Do | 3 | 0/5 | ░░░░░░░░░░ 0% |
+| US-005 | EPIC-002 | Liste produits | 🟢 Done | 5 | 6/6 | ██████████ 100% |
+
+───────────────────────────────────────────────────
+Sprint 1: 3 US | 13 points | Done: 5 pts (38%)
+```
+
+## Format de Sortie - Backlog
+
+```
+📖 Backlog (US non assignées)
+
+| ID | EPIC | Nom | Priorité | Points | Statut |
+|----|------|-----|----------|--------|--------|
+| US-003 | EPIC-001 | Mot de passe oublié | High | 3 | 🔴 To Do |
+| US-006 | EPIC-002 | Détail produit | Medium | 5 | 🔴 To Do |
+| US-007 | EPIC-002 | Recherche | Low | 8 | 🔴 To Do |
+
+───────────────────────────────────────────────────
+Backlog: 3 US | 16 points à planifier
+```
+
+## Exemples
+
+```
+# Lister toutes les US
+/project:list-stories
+
+# Lister les US d'un EPIC
+/project:list-stories epic EPIC-001
+
+# Lister les US du sprint courant
+/project:list-stories sprint 1
+
+# Lister les US en cours
+/project:list-stories status in-progress
+
+# Lister les US bloquées
+/project:list-stories status blocked
+
+# Lister le backlog (non assignées)
+/project:list-stories backlog
+```
+
+## Actions suggérées
+
+Selon le contexte, suggérer:
+```
+Actions:
+  /project:move-story US-XXX sprint-2     # Assigner à un sprint
+  /project:move-story US-XXX in-progress  # Changer le statut
+  /project:add-task US-XXX "[BE] ..." 4h  # Ajouter une tâche
+```

package/Project/i18n/fr/commands/list-tasks.md

@@ -0,0 +1,132 @@
+---
+description: Lister les Tasks
+argument-hint: [arguments]
+---
+
+# Lister les Tasks
+
+Afficher la liste des tâches avec filtrage par User Story, Sprint, Type ou Statut.
+
+## Arguments
+
+$ARGUMENTS (optionnel, format: [filtre] [valeur])
+- **us US-XXX**: Filtrer par User Story
+- **sprint N**: Filtrer par sprint
+- **type TYPE**: Filtrer par type (DB, BE, FE-WEB, FE-MOB, TEST, DOC, OPS, REV)
+- **status STATUS**: Filtrer par statut (todo, in-progress, blocked, done)
+
+## Processus
+
+### Étape 1: Lire les Tasks
+
+1. Scanner les répertoires de tasks:
+   - `project-management/sprints/sprint-XXX/tasks/`
+   - `project-management/backlog/tasks/` (si existe)
+2. Lire chaque fichier TASK-XXX.md
+3. Extraire les métadonnées
+
+### Étape 2: Filtrer
+
+Appliquer les filtres selon $ARGUMENTS.
+
+### Étape 3: Calculer
+
+- Heures estimées totales
+- Heures complétées
+- Répartition par type
+- Répartition par statut
+
+### Étape 4: Afficher
+
+Générer un tableau formaté.
+
+## Format de Sortie - Par User Story
+
+```
+🔧 Tasks - US-001: Login utilisateur
+
+| ID | Type | Description | Statut | Est. | Passé |
+|----|------|-------------|--------|------|-------|
+| TASK-001 | [DB] | Entity User | 🟢 Done | 2h | 2h |
+| TASK-002 | [BE] | Repository User | 🟢 Done | 3h | 3.5h |
+| TASK-003 | [BE] | API endpoint login | 🟡 In Progress | 4h | 2h |
+| TASK-004 | [FE-WEB] | Controller Auth | 🔴 To Do | 3h | - |
+| TASK-005 | [FE-MOB] | Screen Login | ⏸️ Blocked | 6h | - |
+| TASK-006 | [TEST] | Tests AuthService | 🔴 To Do | 3h | - |
+
+───────────────────────────────────────────────────
+US-001: 6 tasks | 21h estimées | 7.5h complétées (36%)
+🔴 2 | 🟡 1 | ⏸️ 1 | 🟢 2
+```
+
+## Format de Sortie - Par Sprint
+
+```
+🔧 Tasks - Sprint 1
+
+Par statut:
+🔴 To Do (8 tasks, 24h)
+🟡 In Progress (3 tasks, 10h)
+⏸️ Blocked (2 tasks, 8h)
+🟢 Done (12 tasks, 35h)
+
+Par type:
+[DB]     ████████░░ 5 tasks
+[BE]     ██████████ 8 tasks
+[FE-WEB] ██████░░░░ 4 tasks
+[FE-MOB] ████░░░░░░ 3 tasks
+[TEST]   ██████░░░░ 4 tasks
+[DOC]    ██░░░░░░░░ 1 task
+
+───────────────────────────────────────────────────
+Sprint 1: 25 tasks | 77h estimées | 35h complétées (45%)
+```
+
+## Format de Sortie - Bloquées
+
+```
+⏸️ Tasks Bloquées
+
+| ID | US | Type | Description | Bloqueur |
+|----|-----|------|-------------|----------|
+| TASK-005 | US-001 | [FE-MOB] | Screen Login | En attente API auth |
+| TASK-012 | US-003 | [BE] | Service Email | Config SMTP manquante |
+
+───────────────────────────────────────────────────
+2 tasks bloquées | 14h en attente
+
+Actions:
+  Résoudre TASK-005: Compléter TASK-003 d'abord
+  Résoudre TASK-012: Configurer SMTP dans .env
+```
+
+## Exemples
+
+```
+# Lister toutes les tasks
+/project:list-tasks
+
+# Lister les tasks d'une US
+/project:list-tasks us US-001
+
+# Lister les tasks du sprint 1
+/project:list-tasks sprint 1
+
+# Lister les tasks backend
+/project:list-tasks type BE
+
+# Lister les tasks en cours
+/project:list-tasks status in-progress
+
+# Lister les tasks bloquées
+/project:list-tasks status blocked
+```
+
+## Codes Couleur Statuts
+
+| Icône | Statut | Signification |
+|-------|--------|---------------|
+| 🔴 | To Do | Non commencée |
+| 🟡 | In Progress | En cours |
+| ⏸️ | Blocked | Bloquée |
+| 🟢 | Done | Terminée |