القائمة
Use when documenting architectural decisions for an NHS digital service using the ADR format, or when reviewing technology choices for GDS assessment evidence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when deploying an NHS Python/FastAPI service to Azure using Terraform, or configuring App Service, Key Vault, or Application Insights.
Use when generating a clinical safety hazard log, clinical risk matrix, or DCB0129 Clinical Safety Case Report for an NHS digital health service.
Use when scaffolding or building an NHS service with the FastAPI + React + Azure stack. Contains project structure, scaffold steps, and deployment commands.
Use when assessing a feature or PR against the GDS Service Standard 14 points, or producing NHS Alpha service assessment evidence.
Use when drafting a Data Protection Impact Assessment (DPIA) for an NHS service that processes health data under UK GDPR.
Use when generating synthetic NHS test data including NHS numbers, patient names, SNOMED codes, and seed scripts for development and demos.
| name | nhs-adr-writer |
| description | Use when documenting architectural decisions for an NHS digital service using the ADR format, or when reviewing technology choices for GDS assessment evidence. |
This skill generates Architectural Decision Records (ADRs) for NHS digital services. ADRs provide the evidence trail required by GDS Service Standard point 11 ("Choose the right tools and technology") and point 12 ("Make new source code open").
Use the MADR (Markdown Any Decision Records) format. Store ADRs as new files in docs/adr/ with sequential numbering. Do not edit this skill file — it is a reference, not a template to fill in.
docs/adr/
├── README.md # Index of all ADRs
├── 0001-backend-framework.md
├── 0002-frontend-framework.md
├── 0003-hosting-platform.md
├── 0004-infrastructure-as-code.md
├── 0005-authentication-strategy.md
└── ...
# ADR-NNNN: [Decision Title]
**Status**: Proposed | Accepted | Deprecated | Superseded by ADR-NNNN
**Date**: YYYY-MM-DD
**Deciders**: [Who was involved in the decision]
## Context
[What is the issue that we're seeing that is motivating this decision or change?
Include NHS-specific constraints that influenced the decision.]
## Decision
[What is the change that we're proposing and/or doing?]
## Consequences
### Positive
- [What becomes easier or possible as a result of this change?]
### Negative
- [What becomes more difficult as a result of this change?]
### Risks
- [What risks does this decision introduce?]
## Alternatives Considered
### [Alternative 1]
- **Pros**: [advantages]
- **Cons**: [disadvantages]
- **Why rejected**: [reason]
### [Alternative 2]
- **Pros**: [advantages]
- **Cons**: [disadvantages]
- **Why rejected**: [reason]
## NHS Constraints
[Document any NHS-specific constraints that influenced this decision, such as:]
- Data sovereignty (UK hosting)
- NHS Digital standards compliance
- Clinical safety implications (DCB0129)
- Data protection (UK GDPR Art. 9 special category)
- NHS Design System requirements
- Integration with NHS systems (PDS, Spine, MESH)
## References
- [Links to relevant documentation, RFCs, NHS standards]
Every NHS Alpha built during the workshop should document at minimum:
var.app_name for isolationdocs/adr/README.md)# Architectural Decision Records
This directory contains the Architectural Decision Records (ADRs) for this service.
| ADR | Title | Status | Date |
|---|---|---|---|
| [0001](0001-backend-framework.md) | Backend Framework — Python/FastAPI | Accepted | YYYY-MM-DD |
| [0002](0002-frontend-framework.md) | Frontend Framework — React/nhsuk-react-components | Accepted | YYYY-MM-DD |
| [0003](0003-hosting-platform.md) | Hosting — Azure App Service UK South | Accepted | YYYY-MM-DD |
| [0004](0004-infrastructure-as-code.md) | Infrastructure as Code — Terraform | Accepted | YYYY-MM-DD |
| [0005](0005-authentication-strategy.md) | Authentication — Managed Identity | Accepted | YYYY-MM-DD |
## What is an ADR?
An Architectural Decision Record captures a significant design decision along with
its context and consequences. See [GDS Service Standard point 11](https://www.gov.uk/service-manual/service-standard/point-11-choose-the-right-tools-and-technology).