القائمة
Use when creating, reviewing, or referencing architectural decision records — defines the ADR format, three-gate creation threshold, and local/hub flavors
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Document a bug report with reproduction steps, severity, and expected behavior. Use when the user explicitly requests the Virtual Team bug workflow or when this workflow is the next stage of an active Virtual Team pipeline.
Quiz the developer on technical decisions in the current work. Use when the user explicitly requests the Virtual Team check workflow or when this workflow is the next stage of an active Virtual Team pipeline.
Create clean, atomic git commits following project conventions. Use when the user explicitly requests the Virtual Team commit workflow or when this workflow is the next stage of an active Virtual Team pipeline.
Extract, define, and validate API contracts as concrete schema files. Use when the user explicitly requests the Virtual Team contracts workflow or when this workflow is the next stage of an active Virtual Team pipeline.
Investigate a bug, reproduce it, trace the code, and document the root cause. Use when the user explicitly requests the Virtual Team debug workflow or when this workflow is the next stage of an active Virtual Team pipeline.
Query project conventions and architectural decisions with source references. Use when the user explicitly requests the Virtual Team decisions workflow or when this workflow is the next stage of an active Virtual Team pipeline.
| name | adr-convention |
| description | Use when creating, reviewing, or referencing architectural decision records — defines the ADR format, three-gate creation threshold, and local/hub flavors |
Only create an ADR when ALL THREE gates are true:
If any gate fails, the decision is normal engineering — document it in the spec, plan, or code comment instead.
File: docs/decisions/YYYY-MM-DD-<kebab-slug>.md
---
id: ADR-NNN # Sequential. Scan docs/decisions/*.md for highest existing ID, increment.
date: YYYY-MM-DD
status: accepted # accepted | superseded
type: technical # technical | contract | convention | infrastructure | data
epic: EPIC-NNN # Optional. Link to parent epic if applicable.
repos: [repo-a] # Hub flavor only. Omit for local decisions.
---
Four required body sections:
# [Decision Title]
## Context
[Why this decision was needed. What problem or constraint triggered it.]
## Decision
[What was decided. Concrete, actionable statements.]
## Alternatives Considered
[What else was evaluated and why it was rejected. Brief — one line per alternative is fine.]
## Consequences
[What follows from this decision. Cross-reference enforcement docs if they exist.]
Hub agreements (cross-repo decisions) add:
repos: frontmatter field (required) — which repos are affected## Affected Repos section with per-repo details### Details sub-section under Decision for repo-specific implementation notescontract unless the agreement is a convention or infrastructure decision| Command | Role | Behavior |
|---|---|---|
plan | Active | Three-gate check after plan review; prompt to create ADR or flag for review |
feature | Light | Prompt on YAGNI overrides and non-obvious approach decisions |
tech-review | Passive | Read existing ADRs; tag findings as ADR candidates; never auto-create |
start | Reference | Point to this skill for local ADR format |
epic | Reference | Point to this skill for hub ADR format |
Scan all docs/decisions/*.md files for id: ADR-NNN in frontmatter. Take the highest number, increment by one. If no ADR files exist, start at ADR-001.
docs/decisions/2026-04-29-skill-size-budget.mddocs/decisions/2026-04-29-domain-glossary-convention.mddocs/decisions/2026-04-29-token-mode-scope.mdskills/skill-authoring/SKILL.md enforces the 100-line budget from ADR-001