50 件 ・ 関連度順
概要と使いどころ
Use when working ON the joelparkerhenderson/architecture-decision-record repository itself (this repo) — adding or editing a decision-record template, example, tool/guardrail link, or translation; reviewing a contributor's PR against it; or keeping README.md and locales/en-001/ in sync. Not for writing an ADR for some other project — use architecture-decision-record-skill for that.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user wants to create, write, name, place, or organize an Architecture Decision Record (ADR) in a software project — e.g. "write an ADR for choosing a database", "document this architecture decision", "set up an adr/ or decisions/ directory", "which ADR template should I use", "supersede an old ADR". Covers picking a template, naming the file, filling in context/decision/consequences, and deciding whether a decision even needs an ADR.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require repeated explanation, one term has multiple meanings, unclear language causes module-boundary mistakes, or domain semantics must remain separate from architecture decisions.
日本語の概要は準備中です。原文の説明を表示しています。
技術や設計を選んだ理由を、背景・比較案・影響とともにMarkdownへ記録するスキル。連番と索引で整理し、既存の記録から過去の判断理由も確認します。
Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
日本語の概要は準備中です。原文の説明を表示しています。
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
日本語の概要は準備中です。原文の説明を表示しています。
Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
日本語の概要は準備中です。原文の説明を表示しています。
Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.
日本語の概要は準備中です。原文の説明を表示しています。
Records one architecture decision with alternatives, consequences and status; does not design the whole system.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Create, extract, or convert an ADR (architectural decision record) using the ADR template. Use when creating new ADRs, extracting an ADR from existing documentation, converting a document into an ADR, recording an architecture or design decision, or updating the status of an existing ADR. Does not create or update enforceable coding standards or conventions — use coding-standard for that. Does not write feature or system documentation — use project-documentation instead.
日本語の概要は準備中です。原文の説明を表示しています。
Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian MCP server. Does not document to local files only — use project-documentation for that. Does not publish an arbitrary existing markdown file — use markdown-to-confluence for that. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence for that. Does not create architectural decision records — use architectural-decision-record. Does not create coding standards — use coding-standard. Does not produce runbooks — use runbook.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.
日本語の概要は準備中です。原文の説明を表示しています。
Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.
日本語の概要は準備中です。原文の説明を表示しています。