'decision' 검색 결과

Create ADRs, short records of architectural decisions, that explain what was chosen, why, and with what trade-offs. Choose among three formats and organize dates, status, numbering, and related links for future team members.

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

• Recording why a database was chosen
• Preserving the rationale for a framework choice
• Documenting an authentication approach

Document approved decisions as concise ADRs, or architecture decision records. It preserves the user's meaning and conditions, removes conversational filler, follows the project's numbering, and presents the saved record for review.

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

• Record a decision approved in conversation
• Preserve the conditions and scope of a decision
• Add a numbered ADR to existing records

Run a decision asynchronously — the memo, the silent-read window, the comment protocol, and the deadline that makes it land without a meeting. Use when asked to decide something async, replace a decision meeting with a document, run an Amazon-style written decision process, or when a decision keeps stalling in comment threads. Produces the decision memo plus the process wrapper: reader roles, response windows, comment-resolution rules, and the tie-breaker. For the document structure alone use decision-memo; this skill runs the process around it.

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

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

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

Manages GDPR Article 22 rights related to solely automated decision-making and profiling, including identification of automated decisions, meaningful human oversight implementation, logic explanation requirements, and contestation mechanisms. Activate for automated decision, profiling, Art. 22, algorithmic decision, AI decision queries.

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

Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.

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

Erzeugt aus einem Bestand offener und gefallener Entscheidungen einen strukturierten ASCII-Abhängigkeitsgraphen (maximal 100 Spalten) für das Terminal. Bewertet Knoten nach fünf festen Kriterien: sinnvoll, empfohlen, usertypisch (Richtung und decision-avatar-Konfidenz getrennt), zusammenpassend und widersprechend; Kanten tragen Beziehungstyp und Belegstatus. Deckt Blocker, Freischaltungen, Reihenfolgen und widersprüchliche Empfehlungen gnadenlos auf. Nutze diesen Skill bei "welche Entscheidungen hängen voneinander ab", "Abhängigkeitsgraph der Entscheidungen", "Entscheidungspfad visualisieren", "Widersprüche zwischen Entscheidungen prüfen", "Reihenfolge der Beschlüsse", /decision-path. NICHT nutzen, um Entscheidungen erst zu inventarisieren -- das macht decision-briefing; NICHT nutzen, um das empfohlene Gesamtkonzept zur Abnahme zu bündeln -- das macht decision-draw; NICHT für kompakte Fünfteiler- Einzelblöcke mit Optionen und Pro/Contra -- das macht decision-shot; NICHT für die Einzelfall-Erwägung mit Frameworks -- das macht decide.

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

Verdichtet gebündelte offene Entscheidungen zu EINEM zusammenhängenden, prosa-basierten Gesamtkonzept auf Basis aller empfohlenen Varianten. Zeigt, wie die Teilsysteme nach der Umsetzung konkret ineinandergreifen, statt den Nutzer durch Dutzende isolierte Einzelfragen zu zwingen. Der Nutzer nimmt das Bild als Ganzes ab oder gibt zielgerichtete Korrekturen, die automatisch in Einzelentscheidungen übersetzt und über decision-briefing Phase 4 ins Register zurückgeschrieben werden. Nutze diesen Skill bei "wie sieht das Ganze aus wenn wir allem zustimmen", "zeichne mir das Gesamtbild", "Gesamtkonzept der Entscheidungen", "decision draw", /decision-draw, "wie greifen die Systeme zusammen". NICHT nutzen, wenn Alternativen pro Einzelpunkt diskutiert werden sollen -- das macht decision-briefing; NICHT für den Abhängigkeitsgraphen -- das macht decision-path; NICHT für strukturierte Einzelblöcke mit Optionen und Pro/Contra (auch bei eng zusammengehörigen Gruppen) -- das macht decision-shot; NICHT zur Herleitung einer einzelnen Entscheidung -- das macht decide.

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

후보 탐색과 비교를 반복하며 근거와 판단을 추가 기록 방식의 장부에 남깁니다. 이전 결과와의 일관성과 재검증 결과를 확인하고 실거래나 운영 작업의 실행 조건을 명확히 합니다.

• 여러 차례 시도하며 후보를 비교할 때
• 판단의 근거를 기록할 때
• 새 정보로 이전 채택 후보를 재평가할 때

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

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

• Record the reasoning behind adopting a technology
• Start an ADR for an API or data model change
• Document an infrastructure decision

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

Organize treatment decisions already supplied and verified by authorized licensed professionals into local JSON documents. Check document structure, source references, declared review status, and supplied dates to support documentation handoffs without making clinical decisions.

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

• Organize verified clinician-authored treatment records
• Check source references and missing documentation fields
• List checkpoint dates already supplied by clinicians

Design meeting schedules, weekly metric reports, and quarterly planning for growing companies. Clarify who makes decisions, assign owners to priorities, and structure written updates so teams can coordinate work and reserve meetings for issues needing discussion.

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

• Redesign meetings that fail to produce decisions
• Standardize weekly business metric reports
• Align quarterly priorities and resources across teams

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

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

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

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Work through founder decisions with 13 executive-role agents and 21 slash commands. Use focused questions or multi-role discussions to clarify tradeoffs, record decisions, and turn the outcome into a 90-day action plan.

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

• Reviewing a hiring decision from several executive perspectives
• Examining pricing changes in a multi-role discussion
• Identifying priorities under cash runway pressure

Turn meeting notes, research, and business feedback into a one-page decision memo. Present a clear recommendation with confidence, supporting facts, option comparisons, risks, and next steps so decision-makers can assess the choice quickly.

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

• Preparing a product strategy decision
• Comparing options for budget approval
• Briefing leaders on an urgent risk

Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.

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

• Deciding whether agent work needs human review
• Preparing decision requests with evidence and recommended choices
• Designing a dashboard for pending human decisions

Organize software project documents from proposals through decisions, implementation specs, and incident reviews. Defines document status changes, links between records, and checks that help teams maintain related guides and preserve decision history.

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

• Organizing a software project's documentation
• Tracking proposal and decision statuses
• Linking incident reviews to related guides

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.

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

Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.

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

Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.

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

Structured approaches to decisions under uncertainty and complexity. Covers expected value, decision trees, multi-criteria decision analysis, System 1 vs System 2 allocation, pre-mortems, reversible vs irreversible decisions, and the distinction between good decisions and good outcomes. Use when choosing among alternatives with uncertain or multi-dimensional consequences, especially when the stakes justify a deliberate rather than intuitive process.

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