メニュー
Produce a one-page architecture brief covering drivers, decisions, risks, and alternatives. Use when a stakeholder needs the whole picture in five minutes - kickoffs, funding asks, vendor reviews.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build production integrations with Anthropic Claude (Claude 4.5 Sonnet, Claude Opus 4, Claude Haiku 4) via the Messages API — system prompts, multi-turn conversations, tool use (function calling), prompt caching, extended thinking, vision, batched requests, and streaming. Use when wiring Claude into backends, agentic workflows, or evaluating it against other foundation models. Requires ANTHROPIC_API_KEY.
Deploy Cloudflare Workers, Pages, and Workers-with-static-assets safely using Wrangler 4.x with versioned uploads, gradual deployments, preview/production environments, secret bindings, observability, and one-command rollback. Use when shipping edge workloads, API routes, or full-stack apps to Cloudflare. Requires CLOUDFLARE_API_TOKEN with scoped permissions or an authenticated Wrangler session.
Deploy static sites, framework apps (Next.js, Astro, Remix, SvelteKit, Nuxt), Edge Functions, and serverless Functions to Netlify with deploy previews, branch deploys, atomic production promotion, scoped env vars, and instant rollback. Use when releasing on Netlify via CLI, API, or Git-triggered builds. Requires NETLIFY_AUTH_TOKEN (PAT) and NETLIFY_SITE_ID.
Transcribe audio with OpenAI speech-to-text models (gpt-4o-transcribe, gpt-4o-mini-transcribe, whisper-1) using prompt-guided terminology, segment-level timestamps, optional diarization via post-processing, and reliable artifact delivery. Use when converting interviews, calls, podcasts, or meeting recordings into reviewable text. Requires OPENAI_API_KEY.
Deploy Web Services, Private Services, Background Workers, Cron Jobs, Static Sites, PostgreSQL, and Key-Value (Redis-compatible) on Render via Blueprints (`render.yaml`) or the Render API with preview environments, zero-downtime rolling deploys, health checks, env-group secret scoping, and one-click rollback. Use when releasing services, applying schema migrations, or syncing infra-as-code on Render. Requires RENDER_API_KEY (owner- or workspace-scoped).
Operate Sentry end-to-end — error monitoring, performance tracing, session replay, profiling, release health, source-map upload, ownership routing, alert tuning, issue triage, and CI integration via sentry-cli — across web, mobile, and backend stacks. Use when instrumenting an app, wiring releases into deploy pipelines, or running incident-grade triage. Requires SENTRY_AUTH_TOKEN (org-scoped, `project:releases project:write`), project DSN, and (for source maps) `org` + `project` slugs.
| name | architecture-brief |
| description | Produce a one-page architecture brief covering drivers, decisions, risks, and alternatives. Use when a stakeholder needs the whole picture in five minutes - kickoffs, funding asks, vendor reviews. |
The brief is a single page that lets a busy reader grasp the system, the bets, and the risks in five minutes - and decide whether to dig deeper. It sits above ADRs and RFCs and links to them. Think IETF abstract crossed with arc42 sections 1, 4, 9, and 11.
| Concern | Recommended |
|---|---|
| Length | One printed page (~400-500 words + 1 diagram) |
| Format | Markdown in repo (docs/architecture/brief.md) |
| Diagram | C4 Level 1 (System Context) - embedded |
| Decisions | Linked, never inlined (ADR/RFC IDs) |
| Risks | Top 3-5 only, with owner |
| Alternatives | Trade-off table, max 3 options |
| Refresh | Reviewed every release; expires after 6 months |
Do not use this skill for engineering deep-dives (use rfc-template) or for slide presentations (use stakeholder-presentation).
flowchart TB
H[Header: name, owner, date, status] --> D[Drivers - 3 bullets]
D --> C[Context Diagram - C4 L1]
C --> K[Key Decisions - linked ADRs]
K --> A[Alternatives - 3-row trade-off table]
A --> R[Top Risks - 3-5 with owner]
R --> N[Next steps + decision asked]
# Architecture Brief - <System Name>
**Owner:** @handle **Status:** Draft | Active | Superseded
**Version:** 2026.04 **Next review:** 2026-07-31
## Drivers
- Business: <one line, with metric>
- User: <one line, with metric>
- Constraint: <regulatory, budget, deadline>
## Context
<embedded C4 L1 diagram>
## Key decisions
| ID | Decision | Link |
|----|----------|------|
| ADR-014 | Postgres over DynamoDB for orders | /docs/adr/014.md |
| ADR-017 | Temporal for sagas | /docs/adr/017.md |
| RFC-0021 | Front door on Cloudflare | /rfcs/0021.md |
## Quality attributes (top 3)
| Attribute | Target | How measured |
|---|---|---|
| Availability | 99.95% monthly | SLO burn rate |
| p95 checkout latency | < 400 ms | RUM + synthetic |
| Recovery (RPO/RTO) | 5 min / 30 min | Quarterly DR test |
## Alternatives considered
| Option | Pros | Cons | Verdict |
|---|---|---|---|
| Monolith | Simple ops | Coupling, scaling | Rejected |
| Microservices (chosen) | Team autonomy | Ops cost | Selected |
| Serverless | Lowest ops | Cold starts, lock-in | Deferred |
## Top risks
| ID | Risk | Mitigation | Owner |
|----|------|------------|-------|
| R-01 | Aurora cutover during peak | Freeze window, dry runs | @data |
| R-02 | IdP vendor delay | Parallel POC | @platform |
| R-03 | OTel agent regression | Pinned version + canary | @sre |
## Decision asked
<one sentence: what do you need from the reader?>
Superseded and replaced - never silently edited beyond minor fixes.| Pitfall | Symptom | Fix |
|---|---|---|
| Two pages | Reader skims, misses ask | Cut to one - move detail to ADR/RFC |
| ADRs pasted in | Brief becomes a design doc | Link only |
| No ask | Reader unsure why they read it | "Decision asked" line at the end |
| Stale | Status says Active, content from 2024 | Expiry date enforced |
| Diagram-free | Wall of text | Always embed C4 L1 |
docs/architecture/brief.md in the system repo.docs/architecture/archive/YYYY-MM/.