Files
Kill_LIFE/docs/workflows/README.md
Clément SAILLANT d7ffbf14cf feat: Add workflows and templates for design reviews, release processes, and compliance checks
- Introduced new documentation for design reviews (DR0/DR1) and release rituals.
- Created templates for Architecture Decision Records (ADR), Design Reviews, Playtest Reports, and Validation Plans.
- Established workflows for consulting, creative processes, systems engineering, R&D spikes, and compliance/QA.
- Implemented GitHub Actions workflows for firmware and hardware CI with required checks strategy.
- Added setup script for repository configuration, including label creation and branch protection.
- Developed installation script for Kill_LIFE with system updates and environment setup.
2026-02-19 01:35:10 +01:00

36 lines
1.5 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Workflows professionnels (opérationnels)
Ces workflows sont conçus pour ressembler aux pratiques **cabinet de conseil**, **bureau d’études**, **design produit**, **studio créatif**, **R&D**, **industrialisation / compliance** — tout en restant compatibles avec le pipeline agentique du repo :
- labels `type:*` pour classer lintention métier,
- labels `ai:*` pour déclencher lautomatisation (Issue → PR),
- **scope guard** et **label enforcement** pour sécuriser les actions,
- **evidence pack** pour tracer les décisions et résultats.
## Menu
- 🧑‍💼 [Cabinet de conseil](consulting.md)
- 🏗 [Bureau d’études / Ingénierie système](systems_engineering.md)
- 🎨 [Design produit / UX](design.md)
- 🎭 [Créatif / narration / contenu](creative.md)
- 🧪 [R&D / spikes time-boxés](rnd_spikes.md)
- 🛡 [Compliance / QA / Release](compliance_release.md)
## Règle simple (anti-chaos)
1) **Crée une issue** avec un template (`.github/ISSUE_TEMPLATE/`).
2) **Triage** : ajoute `prio:*`, `risk:*`, `scope:*`, et garde seulement un `type:*`.
3) **Déclenche lautomatisation** en ajoutant le bon label `ai:*` :
- `ai:spec` → formaliser exigences (RFC2119 + critères dacceptation)
- `ai:plan` → architecture + options + ADR
- `ai:tasks` → backlog exécutable
- `ai:impl` → impl + tests minimaux
- `ai:qa` → durcissement tests/edge
- `ai:docs` → docs + runbooks
⚠️ Si tu suspects une injection / comportement bizarre : ajoute `ai:hold`.
## Evidence pack
Voir : `docs/evidence/evidence_pack.md`.