52건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks "why did we decide X". Deduces the filename scheme, section set and status vocabulary from the records already there; ships a validator with an exit code, so the audit is a check and not an opinion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and maintain Architecture Decision Records (ADRs) for significant technical choices—frameworks, data stores, API shapes, ML platform decisions. Use when documenting a decision, onboarding, or superseding a prior approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding which Salesforce automation tool should own a requirement, including before-save and after-save Flow, screen Flow, scheduled Flow, invocable Apex, Apex triggers, and migration off Workflow Rules or Process Builder. Triggers: 'Flow or Apex trigger', 'which automation tool should I use', 'Process Builder migration', 'Workflow Rule retirement', 'same-record update or trigger', 'automation decision record', 'why did we reject Apex', 'one object one order', 'automation inventory for this object', 'scheduled Flow or Batch Apex'. NOT for 'which tool should stamp this field on save, and will it recurse' — use admin/workflow-field-update-patterns. NOT for actually running the conversion of an existing Process Builder — use flow/process-builder-to-flow-migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to select the right Salesforce integration pattern — from point-to-point to event-driven to hub-and-spoke — by applying the official Salesforce two-axis decision framework (integration type × timing) to a business integration scenario. Trigger keywords: integration pattern decision, choose integration approach, Salesforce integration architecture, when to use platform events vs API, integration type selection. NOT for implementation of any specific integration pattern (use domain-specific integration skills), MuleSoft architecture (use architect/mulesoft-anypoint-architecture), or middleware vendor selection. More triggers: integration decision record, Bulk API vs REST for a nightly load, external Id upsert, Named Credential vs Remote Site Setting, platform event vs CDC, who calls whom.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when choosing between alternatives with trade-offs — X-or-Y decisions or a weighted decision matrix / gewichtete Entscheidungsmatrix ('score my options'); ADR via `adr-create`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Padrões abrangentes para criar, manter e gerenciar Registros de Decisões de Arquitetura (ADRs) que capturam o contexto e a lógica por trás de decisões técnicas significativas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a risk owner wants to accept a residual risk instead of treating it further, or when someone asks "write a risk acceptance", "we want to accept this risk", "risk exception form", "document the risk acceptance for the auditor", "security exception for this system", "can we sign off this risk" or "management accepted the risk, how do we record it". Drafts a one-page decision record per risk: the risk and its score, the options considered with cost, why acceptance is reasonable, compensating measures with evidence, conditions, expiry and the triggers that reopen it, with a signature block for the person who holds the authority.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns one decision discussion (meeting transcript, chat thread, email chain or notes) into a DRAFT one-page decision memo: the decision as stated, status, options considered, evidence cited, dissent recorded verbatim, owner, effective date and review date, with UNKNOWN for anything the discussion did not settle. Use when the user asks to "write up the decision", "record what we decided", "capture the decision from this thread", "draft the decision memo" or "add this to the decision log". Do not use for full minutes or action items, use transcript-to-actions instead; for a technical design decision, use architecture-decision-record; for a paper seeking a decision not yet taken, use board-paper-skeleton. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 architect...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude Codeセッション中に行われたアーキテクチャ上の意思決定を構造化されたADRとして記録する。意思決定の瞬間を自動検出し、コンテキスト、検討された代替案、根拠を記録する。将来の開発者がコードベースの形状の理由を理解できるようADRログを維持する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.