generate-add
Create, update, and review a source-backed Architecture Design Document (ADD) from reviewed use cases, applicable Business Decision Records, repository evidence, constraints, quality attributes, C4 vi
SKILL.mdskills/generate-add/SKILL.md
GitHubGenerate ADD
Workflow
- Read
AGENTS.md, the project profile, reviewed use cases, applicable BDRs, existing architecture, relevant code, deployment sources, diagrams, and decisions. - Resolve the next
ADD-NNNor the referenced ADD. Never reuse or renumber identifiers. - Copy assets/add-template.md and apply references/add-quality.md.
- Define scope, drivers, constraints, system context, responsibilities, data flows, interfaces, deployment, operations, risks, and migration/rollback.
- Link C4 views rather than embedding several abstraction levels in one diagram. Request
$generate-c4only for views that answer a concrete stakeholder question. - Identify independently changeable choices as ADR candidates. Link proposed ADRs; treat only accepted ADRs as constraints.
- Run the privacy, security, clinical/legal safety, and human-oversight assessment. Stop on an unresolved compliance conflict.
- Save under
architecture/design/ADD-NNN-<slug>.mdunless an established layout exists.
Rules
- Do not invent owners, technologies, protocols, service levels, classifications, approvals, or data flows.
- Distinguish current, transition, target, and conceptual states.
- Include failure modes and operational ownership, not only the happy path.
- Keep real personal/health data, credentials, secrets, and sensitive endpoints out of the document.
- Keep status
DraftorIn Reviewuntil authoritative approval is cited.
Completion
Report the document path, linked use cases, required C4 views, ADR candidates, compliance blockers, open questions, and implementation-readiness result.