القائمة
Write Architecture Decision Records when making significant technical choices. Use when selecting tools, patterns, frameworks, or making structural changes that future developers need to understand.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write AGENTS.md files that serve as operating contracts for AI agents. Use when creating or updating AGENTS.md for a project. Trigger terms: AGENTS.md, agent instructions, agent contract, agent configuration, coding agent setup.
Quality rules for changelog entries. Use when validating, writing, or reviewing changelog content to ensure user-facing value communication.
Task completion sequence including verification, git, signaling, and handoff. Use when finishing a task or reporting status.
Architecture diagrams for documentation. Covers ASCII, Mermaid, C4, and D2. Applies C4 methodology by default. Trigger terms: diagram, flowchart, architecture diagram, sequence diagram, C4, mermaid, ascii diagram.
Classify documentation by audience and content type. Use when planning, auditing, or placing project documentation.
Audit project documentation for quality, completeness, and freshness. Use when assessing documentation health, planning cleanup, or measuring improvement.
| name | adr-authoring |
| description | Write Architecture Decision Records when making significant technical choices. Use when selecting tools, patterns, frameworks, or making structural changes that future developers need to understand. |
Record decisions so future-you (and future-teammates) know WHY, not just WHAT.
Do NOT write ADRs for: trivial choices, temporary experiments, or decisions that are easily reversed.
# ADR-NNNN: [Decision Title]
**Status:** proposed | accepted | deprecated | superseded by ADR-XXXX
**Date:** YYYY-MM-DD
**Deciders:** [who was involved]
## Context
What is the issue? What forces are at play? Why does this decision need to be made now?
## Decision
What did we decide? State it clearly in one sentence, then elaborate.
## Consequences
### Positive
- [What becomes easier or better]
### Negative
- [What becomes harder or what we give up]
### Neutral
- [Side effects that aren't clearly good or bad]
## Alternatives Considered
### [Alternative 1]
- Pros: ...
- Cons: ...
- Why rejected: ...
## References
- [Research artifact that informed this] (link to docs/research/ if applicable)
- [Related ADRs]
docs/adrs/NNNN-short-title.mddocs/adrs/README.md or link from project READMEIf a research artifact (warlock output, BPAPPA survey) informed this decision, link it:
## References
- [Research: JWT vs Session Auth](../research/bpappa-auth-patterns.md) — informed this decision
The research artifact should back-link: Consumed by: ADR-0003