ワンクリックでManusで任意のスキルを実行

architecture-decision-record

スター1

フォーク0

更新日2026年5月1日 04:04

Capture significant architectural decisions as immutable, versioned MADR 4.0 records. Use when a choice is hard to reverse, affects multiple teams, or sets a long-lived constraint.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

SwapnilPopat

SwapnilPopat/ai-assistant-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Architecture Decision Records (ADR)

ADRs make architectural intent legible. They convert tribal knowledge into a durable, searchable log of context, options, and consequences so future contributors understand why, not just what. Adopt MADR 4.0 (2025) as the canonical schema and keep records co-located with the code they govern.

Stack Baseline (2026)

Concern	Recommended
Schema	MADR 4.0 (`adr.github.io`)
Storage	`docs/adr/NNNN-title.md` in the owning repo
Tooling	`adr-tools` v4, `log4brains`, or Backstage TechDocs
Lifecycle states	Proposed, Accepted, Deprecated, Superseded
Review	PR-based, CODEOWNERS-gated, async RFC channel
Index	Auto-generated `README.md` rolled up in Backstage

When to Use

Choosing a runtime, datastore, message bus, or auth model.
Defining cross-cutting conventions (multi-tenancy, error contracts, eventing schema).
Deprecating or replacing a previously accepted ADR.
Recording a deliberate non-decision ("we will defer this until...").

Prerequisites

Repo with docs/adr/ directory and CODEOWNERS entry.
Markdown linter and PR template referencing an ADR checklist.
Agreed numbering scheme (zero-padded, monotonic).
Stakeholder list (consulted vs. informed) per Team Topologies.

Instructions

flowchart LR
  A[Trigger: significant decision] --> B[Draft ADR Proposed]
  B --> C[Async review on PR]
  C --> D{Consensus?}
  D -- yes --> E[Merge as Accepted]
  D -- no --> B
  E --> F[Implement + link from code]
  F --> G{Context changed?}
  G -- yes --> H[New ADR Supersedes prior]
  G -- no --> E

Detect a decision. If the choice is reversible within a sprint and local to one module, skip the ADR. Otherwise open a draft.
Scaffold from MADR 4.0. Use the template below; assign the next number; set status Proposed.
Frame the problem. State context, drivers (quality attributes), constraints. Link a Wardley Map or Cynefin domain when relevant.
Enumerate options. Minimum two viable alternatives plus "do nothing". Cite evidence (benchmarks, vendor docs, ThoughtWorks Radar Vol 31+).
Decide and record consequences. Capture positive, negative, and neutral consequences. Name owners and a review date.
Open PR for async review. Require approvals from CODEOWNERS and one consulted stakeholder. Resolve threads in-line.
Merge as Accepted. Reference the ADR id from affected READMEs and source files (// see ADR-0042).
Maintain lifecycle. Never edit accepted ADRs except to flip status. Supersede via a new ADR that links back: Supersedes: ADR-0042.

MADR 4.0 Template

# ADR-NNNN: <Short title of decision>

- Status: Proposed | Accepted | Deprecated | Superseded by ADR-XXXX
- Date: YYYY-MM-DD
- Deciders: @handle1, @handle2
- Consulted: @teamA
- Informed: #channel

## Context and Problem Statement
<2-4 sentences. What forces are at play? Link tickets, metrics, ADRs.>

## Decision Drivers
- <Quality attribute or constraint>
- <Cost / time-to-market>

## Considered Options
1. <Option A>
2. <Option B>
3. Do nothing

## Decision Outcome
Chosen option: "<Option B>", because <justification>.

### Consequences
- Positive: <…>
- Negative: <…>
- Neutral: <…>

## Pros and Cons of the Options
### <Option A>
- Good, because …
- Bad, because …

## More Information
Links, benchmarks, prototypes, related ADRs.

Common Pitfalls

Pitfall	Symptom	Mitigation
Retrofitting ADRs months later	Vague context, no alternatives	Write at decision time; allow short ADRs
Editing accepted ADRs	Audit trail lost	Supersede via new ADR; keep originals immutable
One-option ADRs	Rubber-stamp culture	Require >=2 alternatives + "do nothing"
ADRs in a wiki	Drifts from code	Co-locate in repo under `docs/adr/`
No index	Discoverability collapses	Auto-generate index in CI

Output Format

One Markdown file per decision: docs/adr/NNNN-kebab-title.md.
Auto-generated docs/adr/README.md index grouped by status.
Cross-links from affected source files and service READMEs.

Authoritative References

MADR 4.0 specification - https://adr.github.io
Michael Nygard, "Documenting Architecture Decisions" (2011, canonical)
ThoughtWorks Technology Radar Vol 31 (2026) - Lightweight ADRs (Adopt)
Team Topologies, Skelton & Pais - stakeholder modes
adr-tools v4 - https://github.com/npryce/adr-tools

このリポジトリの他の Skills

同じリポジトリ

anthropic-claude

SwapnilPopat/ai-assistant-skills

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.

2026-05-011

cloudflare-deploy

SwapnilPopat/ai-assistant-skills

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.

2026-05-011

netlify-deploy

SwapnilPopat/ai-assistant-skills

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.

2026-05-011

openai-transcribe

SwapnilPopat/ai-assistant-skills

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.

2026-05-011

render-deploy

SwapnilPopat/ai-assistant-skills

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).

2026-05-011

sentry-observability

SwapnilPopat/ai-assistant-skills

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.

2026-05-011

Architecture Decision Records (ADR)

Stack Baseline (2026)

Concern

Recommended

Schema

MADR 4.0 (adr.github.io)

Storage

docs/adr/NNNN-title.md in the owning repo

Tooling

adr-tools v4, log4brains, or Backstage TechDocs

Lifecycle states

Proposed, Accepted, Deprecated, Superseded

Review

PR-based, CODEOWNERS-gated, async RFC channel

Index

Auto-generated README.md rolled up in Backstage

When to Use

Choosing a runtime, datastore, message bus, or auth model.

Defining cross-cutting conventions (multi-tenancy, error contracts, eventing schema).

Deprecating or replacing a previously accepted ADR.

Recording a deliberate non-decision ("we will defer this until...").

Prerequisites

Repo with docs/adr/ directory and CODEOWNERS entry.

Markdown linter and PR template referencing an ADR checklist.

Agreed numbering scheme (zero-padded, monotonic).

Stakeholder list (consulted vs. informed) per Team Topologies.

Instructions

flowchart LR A[Trigger: significant decision] --> B[Draft ADR Proposed] B --> C[Async review on PR] C --> D{Consensus?} D -- yes --> E[Merge as Accepted] D -- no --> B E --> F[Implement + link from code] F --> G{Context changed?} G -- yes --> H[New ADR Supersedes prior] G -- no --> E

Detect a decision. If the choice is reversible within a sprint and local to one module, skip the ADR. Otherwise open a draft.

Scaffold from MADR 4.0. Use the template below; assign the next number; set status Proposed.

Frame the problem. State context, drivers (quality attributes), constraints. Link a Wardley Map or Cynefin domain when relevant.

Enumerate options. Minimum two viable alternatives plus "do nothing". Cite evidence (benchmarks, vendor docs, ThoughtWorks Radar Vol 31+).

Decide and record consequences. Capture positive, negative, and neutral consequences. Name owners and a review date.

Open PR for async review. Require approvals from CODEOWNERS and one consulted stakeholder. Resolve threads in-line.

Merge as Accepted. Reference the ADR id from affected READMEs and source files (// see ADR-0042).

Maintain lifecycle. Never edit accepted ADRs except to flip status. Supersede via a new ADR that links back: Supersedes: ADR-0042.

MADR 4.0 Template

# ADR-NNNN: <Short title of decision> - Status: Proposed | Accepted | Deprecated | Superseded by ADR-XXXX - Date: YYYY-MM-DD - Deciders: @handle1, @handle2 - Consulted: @teamA - Informed: #channel ## Context and Problem Statement <2-4 sentences. What forces are at play? Link tickets, metrics, ADRs.> ## Decision Drivers - <Quality attribute or constraint> - <Cost / time-to-market> ## Considered Options 1. <Option A> 2. <Option B> 3. Do nothing ## Decision Outcome Chosen option: "<Option B>", because <justification>. ### Consequences - Positive: <…> - Negative: <…> - Neutral: <…> ## Pros and Cons of the Options ### <Option A> - Good, because … - Bad, because … ## More Information Links, benchmarks, prototypes, related ADRs.

Common Pitfalls

Pitfall

Symptom

Mitigation

Retrofitting ADRs months later

Vague context, no alternatives

Write at decision time; allow short ADRs

Editing accepted ADRs

Audit trail lost

Supersede via new ADR; keep originals immutable

One-option ADRs

Rubber-stamp culture

Require >=2 alternatives + "do nothing"

ADRs in a wiki

Drifts from code

Co-locate in repo under docs/adr/

No index

Discoverability collapses

Auto-generate index in CI

Output Format

One Markdown file per decision: docs/adr/NNNN-kebab-title.md.

Auto-generated docs/adr/README.md index grouped by status.

Cross-links from affected source files and service READMEs.

Authoritative References

MADR 4.0 specification - https://adr.github.io

Michael Nygard, "Documenting Architecture Decisions" (2011, canonical)

ThoughtWorks Technology Radar Vol 31 (2026) - Lightweight ADRs (Adopt)

Team Topologies, Skelton & Pais - stakeholder modes

adr-tools v4 - https://github.com/npryce/adr-tools

name	architecture-decision-record
description	Capture significant architectural decisions as immutable, versioned MADR 4.0 records. Use when a choice is hard to reverse, affects multiple teams, or sets a long-lived constraint.