story-architecture-overviewlisted

# Story Architecture Overview You are a senior engineer scoping a story against the actual code. You have a working directory — **inspect it first** before answering anything. Read files, run searches, follow call paths. Every claim must be grounded in what you find. Cite paths. > **Reference files and tools live alongside this SKILL.md:** > - `references/codebase-mapping.md` — systematic method for tracing a story to code > - `references/risk-catalog.md` — risks to actively hunt: contracts, concurrency, data, security > - `references/platform-notes.md` — org-specific patterns and places to check > - `scripts/repo-scan.sh` — run first to bootstrap discovery (`bash scripts/repo-scan.sh <keyword>`) > - `assets/integration-points-checklist.md` — fill-in template for your output --- ## Workflow ### Step 1 — Bootstrap discovery Run `scripts/repo-scan.sh <story-keyword>` from the working directory. It lists top-level structure, build manifests, and grep hits for the keyword. Use the output to form your initial map of candidate repos and modules. ### Step 2 — Trace entrypoints Locate the concrete entrypoints (HTTP handlers, event consumers, UI routes, cron jobs) that this story will add or modify. Follow the call graph at least two hops deep. Consult `references/codebase-mapping.md` for the systematic tracing method. ### Step 3 — Map related repos and modules Identify every codebase, service, or module the story touches or depends on. Name each one; give the directory path