'decision-record' 검색 결과

Maintain a collection of architecture decision record templates, examples, translations, and tool links. It explains which files to update for each contribution and how to review pull requests for completeness, consistent formatting, and relevant content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add an ADR template to the collection
• Add a worked decision record example
• Update links to ADR tools and pull request checks

Write architecture decision records, short documents explaining a software design choice, its context, and its consequences. It helps decide what deserves a record, select a template, organize files, and link replacement decisions to earlier records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record why a database or library was chosen
• Set up a directory for decision records
• Choose an ADR template that fits the decision

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain clear business definitions and relationships in an existing glossary or CONTEXT.md. Flag unresolved meanings and refer lasting design choices to the existing architecture decision record workflow, keeping terminology separate from decision rationale and task status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Document business terms that need repeated explanation
• Clarify terms with multiple meanings
• Track domain interpretations awaiting confirmation

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기술이나 설계를 선택한 이유를 배경, 대안, 영향과 함께 Markdown으로 기록합니다. 일련번호와 색인으로 정리하고 기존 기록에서 과거 판단의 근거도 찾습니다.

• 프레임워크나 데이터베이스 선택 이유 기록
• 설계 대안과 장단점 정리
• 과거 기술 결정의 근거 확인

Write an architecture decision record, a document explaining a team's design choice. Capture the context, rejected alternatives, and future costs so newcomers can understand the reasoning, then review the draft before saving it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording an agreed architecture decision
• Preserving reasons for rejecting alternatives
• Explaining past design choices to new team members

Document major technical choices as Architecture Decision Records, or ADRs. Capture the context, alternatives, reasons, and consequences, then organize related records and track whether decisions are proposed, accepted, retired, or replaced.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording reasons for choosing a framework or database
• Comparing design options and their trade-offs
• Sharing past decisions with new team members

Write and maintain Architecture Decision Records (ADRs), documents explaining important technical choices. Capture the context, options, decision, and consequences, then organize records and track their status so teams can revisit the reasoning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record the reasons for choosing a framework or database
• Document design options and their trade-offs
• Explain past technical decisions to new team members

Create an Architectural Decision Record, a document explaining a system design choice. Organize context, rationale, alternatives, benefits, drawbacks, and implementation notes in consistent Markdown that people can read and AI tools can parse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording the reasons behind a system design choice
• Documenting rejected alternatives and trade-offs
• Sharing decision context with new team members

Document major technical decisions with their context, alternatives, reasoning, and consequences. The skill provides Architecture Decision Record templates and maintenance practices so teams can review past choices, track replacements, and explain decisions to new members.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording reasons for technology choices
• Comparing design options and trade-offs
• Explaining past decisions to new team members

Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update Composio documentation content and changelogs
• Revise Fumadocs settings and documentation automation prompts
• Record or update documentation 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.