Skip to main content

architect-adr

Prompt for Architect Alphonso to perform analysis and draft a Proposed ADR

Source facts

Repository
sddevelopment-be/quickstart_agent-augmented-development
Last source activity
January 31, 2026 at 06:30
Detected SKILL.md language
English
Stars
13
Forks
3

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
ARCHITECT ADR
description
Prompt for Architect Alphonso to perform analysis and draft a Proposed ADR
version
1.0.0
type
prompt-template
agent
architect-alphonso
category
architecture
tags
["architecture","adr","decision-record","trade-offs","design"]
# ARCHITECT ADR Prompt for Architect Alphonso to perform analysis and draft a Proposed ADR ## Instructions Clear context. Bootstrap as Architect Alphonso. When ready: Execute an architectural analysis and draft a Proposed ADR. ## Inputs: - Decision Title: \<TITLE> - Problem Context (paragraph): \<CONTEXT> - Forces / Constraints (bullets): \<FORCES> - Options (bullets, short labels): \<OPTIONS> - Preferred Option: \<PREFERRED> - Impact Areas (e.g., performance, portability, maintainability): \<IMPACTS> - Related Artifacts (paths): \<RELATED> - Existing ADR References (list): \<ADR_REFS> - Risk Appetite (low|medium|high): \<RISK_APPETITE> - Time Horizon (short|medium|long): \<HORIZON> - Non-Functional Requirements (bullets): \<NFRS> ## Task: 1. Validate uniqueness of \<TITLE> vs existing ADRs. 2. Decompose context into problem statement + drivers + constraints. 3. Analyze each \<OPTION> against \<IMPACTS> and \<NFRS> (matrix-style, qualitative scores). 4. Provide rationale for selecting \<PREFERRED> (trade-off narrative). 5. Draft ADR in template format (status: Proposed) with sections: Context, Decision, Rationale, Envisioned Consequences (+ positive/negative), Considered Alternatives. 6. Add risk assessment (tie to \<RISK_APPETITE>) and horizon alignment. 7. Suggest acceptance criteria + success metrics. 8. Output file: `docs/architecture/adrs/ADR-XXX-\<slug>.md` (choose next number). 9. Provide diff plan for cross-link updates (README index). ## Output: - ADR markdown content - Option Impact Matrix block - Success Metrics list ## Constraints: - Keep Decision section ≤ 120 words. - Each alternative: one sentence reason for rejection. - Avoid speculative implementation detail; defer to Technical Design doc if needed. Ask clarifying questions if \<CONTEXT> or \<PREFERRED> ambiguous. ## Workflow 1. Provide diff plan for cross-link updates (README index). ## Inputs - **TITLE** (required) - Decision Title - **CONTEXT** (required) - paragraph - **FORCES** (required) - bullets - **OPTIONS** (required) - bullets, short labels - **PREFERRED** (required) - Preferred Option - **IMPACTS** (required) - e.g., performance, portability, maintainability - **RELATED** (required) - paths - **ADR_REFS** (required) - list - **RISK_APPETITE** (required) - low|medium|high - **HORIZON** (required) - short|medium|long - **NFRS** (required) - bullets ## Outputs - Success Metrics list
View on GitHub