home/roleplay/architecture-impact

Architecture Impact

GPTClaudeGemini··756 copies·updated 2026-07-14
architecture-impact.prompt
# Lens: Architecture Impact

> Reusable analysis lens. Apply to any change description (story, RFC, PR diff) to surface architectural ripples.

## Purpose
Identify which layers, services, packages, and contracts the change touches, and flag anything that needs an Architecture Decision Record (ADR) or cross-team review.

## Length budget
**≤30 lines.** Bullets, not paragraphs. Omit subsections that don't apply (don't write "Cross-team: none identified" — just leave it out). Each open question goes in **this lens only** if it's an architecture decision; cross-reference from other lenses.

## When to use
- New feature spanning >1 layer (UI / domain / data / integration).
- Anything that changes a public API contract, message schema, or shared library.
- Stories that look "small" but reference shared infrastructure (auth, sync, queue, gateway).

## Inputs expected
- Assembled story context (`story.md`) **or** any change description.
- Discovered project context (CLAUDE.md, README.md, folder structure) so layer naming is accurate.

## Output template

when to use it

Community prompt sourced from the open-source GitHub repo shuchitajain/story-agent (MIT). A "Architecture Impact" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

roleplaycommunitygeneral

source

shuchitajain/story-agent · MIT