dev:auto:clarify
Lever ambiguités avec heuristiques automatiques (Phase 3)
What this skill does
# Objectif
## Instructions à Exécuter
**IMPORTANT : Exécute ce workflow étape par étape :**
Phase 3 du workflow automatisé : identifier et résoudre les ambiguïtés **avec heuristiques prédéfinies**.
Zéro question, zéro AskUserQuestion. Décisions automatiques basées sur les patterns existants.
# Instructions
## 1. Lire le contexte
Déterminer le chemin du workflow state :
```bash
# Récupérer issue_number depuis le contexte
workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
```
- Lire le workflow state pour la feature et les findings de l'exploration (Phase 2)
- Si le fichier n'existe pas ou phase 2 non complétée, exit avec erreur
## 2. Analyser les zones d'ombre
Identifier les aspects sous-spécifiés dans les catégories suivantes.
## 3. Appliquer heuristiques automatiques
**Au lieu de poser des questions, utiliser cette table de décision :**
| Catégorie | Heuristique par défaut |
|-----------|------------------------|
| **Edge cases** | Valeur null/vide → Exception métier explicite (`InvalideXXX` ou `{NomEntité}Invalide`) |
| **Gestion erreurs** | Exceptions métier typées (héritant d'une base commune) + logging PSR-3 niveau ERROR |
| **Intégration** | Réutiliser patterns existants détectés en Phase 1 (patterns de repository, services, DTOs) |
| **Rétrocompatibilité** | Préserver API publique (pas de breaking changes), créer nouvelle méthode si needed |
| **Performance** | Pas de cache prématuré sauf si liste > 1000 items (sinon trop de complexité) |
| **Sécurité** | TOUJOURS valider inputs (whitelist si possible), échapper outputs selon context |
## 4. Documenter les décisions appliquées
Mettre à jour le workflow state avec les décisions **appliquées** (pas des questions) :
```json
{
"currentPhase": 3,
"phases": {
"3": {
"status": "completed",
"completedAt": "{ISO timestamp}",
"durationMs": {durée},
"autoDecisions": {
"edgeCases": "Exception métier InvalideXXX pour valeurs null/vides",
"errorHandling": "Exceptions typées héritant de DomainException + logging PSR-3 ERROR",
"integration": "Réutilisation patterns existants Phase 1",
"compatibility": "Préservation API publique, nouvelle méthode si breaking",
"performance": "Pas de cache prématuré sauf liste > 1000 items",
"security": "Validation inputs (whitelist), échappement outputs"
}
}
}
}
```
# Règles
- ❌ **Zéro AskUserQuestion** (pas de questions)
- ✅ **Heuristiques appliquées** directement selon la table
- ❌ **Ne PAS proposer d'architecture**
- ✅ **Documenter les décisions** pour traçabilité
- ✅ **Utiliser les patterns existants** détectés en Phase 1
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.