sddevelopment-be 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:
- Validate uniqueness of <TITLE> vs existing ADRs.
- Decompose context into problem statement + drivers + constraints.
- Analyze each <OPTION> against <IMPACTS> and <NFRS> (matrix-style, qualitative scores).
- Provide rationale for selecting <PREFERRED> (trade-off narrative).
- Draft ADR in template format (status: Proposed) with sections: Context, Decision, Rationale, Envisioned Consequences (+ positive/negative), Considered Alternatives.
- Add risk assessment (tie to <RISK_APPETITE>) and horizon alignment.
- Suggest acceptance criteria + success metrics.
- Output file:
docs/architecture/adrs/ADR-XXX-\<slug>.md(choose next number). - 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
- 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