Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/alexbruno/dev-skills --skill decision-recordsAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Decision Records (ADRs)
Capture why important technical decisions were made—along with alternatives considered and trade-offs accepted—in concise, immutable Markdown records.
When to Create an ADR
Create an ADR when a change involves:
- A hard-to-reverse architectural or data-model choice.
- A cross-cutting trade-off affecting multiple modules, services, or teams.
- Adding or replacing a core dependency, protocol, storage engine, or integration pattern.
Skip ADRs for routine implementation details, local refactorings, or easily reversible choices—those belong in workflow/PLAN.md or code comments.
Storage & Naming
- Store records in
docs/decisions/(ordocs/adr/if the repository already uses that convention). - Name files sequentially with a lowercase hyphenated slug:
docs/decisions/0001-short-decision-title.md
- Start from the template in ADR.md.
Rules
- Link with `workflow/`: Reference the ADR from
workflow/PLAN.md(andworkflow/SPEC.mdif applicable) so design context stays connected. - Keep it concise: Focus on context, decision, alternatives rejected, and consequences—avoid turning an ADR into a tutorial or full specification.
- Immutable history: Once accepted, do not rewrite an old ADR's intent; if a decision changes later, create a new ADR that marks the previous one as
Superseded by <ADR-XXXX>.