RFC / Decision Record

Capture an architecture decision with context, options, and consequences.

Prompt

Copy the prompt, then replace the placeholders with your own context.

Write an architecture decision record for this choice. Sections: 1. Status (proposed) 2. Context and forces 3. Options considered 4. Decision and rationale 5. Consequences (positive, negative, risks) 6. Review date Keep it one to two pages. Link to code or tickets where relevant.

Related prompts

More prompts with similar tags or categories.

Business

Any model

Incident Status Update

Draft internal and external status messages during an incident.

128 copies

Draft incident communications from the facts I provide. Produce: 1. Internal Slack update (technical, timeline-focused) 2. External status page update (user impact, workaround, next update time) 3. What not to say yet (unknowns) Calm, factual tone. No ETA unless confident.

incident

communication

by prompts!

View

Business

Any model

User Story Splitting

Break an epic into small, independently shippable user stories.

206 copies

Split this epic into user stories small enough for a 1–3 day PR each. Each story needs: - Title - Acceptance criteria - Dependencies noted - MVP vs follow-up label Vertical slices over horizontal layers. First story should demo something user-visible.

agile

planning

by prompts!

View

Research

Claude

Literature Summary for Decision

Summarize approaches from docs and threads to inform an architecture decision.

143 copies

Summarize research to inform a decision on [topic]. Include: - Common approaches and when each fits - Tradeoffs (complexity, cost, operability) - What our codebase already assumes - Recommendation with reversible vs one-way door flagged Link to official docs where possible. Mark uncertain claims.

research

architecture

by prompts!

View