'adr' 검색 결과

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.

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

Genera un nuevo Registro de Decisión de Arquitectura (ADR) copiando la plantilla de ADR en el siguiente archivo numerado y registrándolo en el índice de decisiones. Úsalo cuando la persona quiera registrar una decisión de arquitectura, crear/añadir un ADR o documentar una elección técnica (p. ej. "escribe un ADR para cambiar la base de datos", "añade un registro de decisión").

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

This skill recommends lifelong biochemical testing for recurrence in all patients with Cushing's syndrome after adrenalectomy, except those with resected adrenal adenoma showing CT density <10 Hounsfield units. Use when determining long‑term follow‑up strategy for a post‑adrenalectomy CS patient; triggers include “post‑adrenalectomy Cushing’s syndrome”, “CT density <10 HU”, and “adrenal adenoma resection”.

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

This skill guides evaluation for malignancy using imaging in patients with a history of adrenal adenoma (post‑adrenalectomy Cushing’s syndrome) when the adenoma demonstrates a CT density of ≥10 Hounsfield units or when pathology is consistent with possible carcinoma. Trigger phrases include “CT density ≥10 HU”, “possible carcinoma on pathology”, and “post‑adrenalectomy CS patient with adrenal adenoma history”.

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

계획이나 설계를 깊이 묻는 질문으로 구체화하면서 설계 결정 기록과 용어집도 작성합니다. 하나의 대화에서 검토와 문서화를 함께 진행할 때 사용합니다.

• 질문에 답하며 계획 구체화
• 대화로 설계 심층 검토
• 검토 중 설계 결정 기록

프로젝트 문서 정리 요청에 맞는 전문 스킬을 선택합니다. 요청 시 문서 역할, 로컬 링크, 설계 결정 기록 색인과 근거 참조를 파일 변경 없이 점검합니다.

• 프로젝트 문서 정리 절차 선택
• 기존 문서의 정보 출처 파악
• 로컬 링크와 설계 결정 색인 점검

Investigate a Homecore capability by tracing relevant source files, tests, and accepted architecture decisions. Check documented status and limitations before proposing code, while keeping implementation presence separate from deployment compatibility or claims of Home Assistant parity.

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

• Find source files and design decisions for a Homecore capability
• Check documented implementation status and limitations
• Review focused tests before proposing code changes

Investigate a username, file, code identifier, URL, or concept by exploring connected entities across relevant sources. Produce a dossier with a summary, relationship diagram, source references, and a machine-readable JSON graph.

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

• Mapping connections around a username or concept
• Investigating references to a file or code identifier
• Tracing links to an architecture decision record

Use ROADrecon and roadtx during authorized Microsoft Entra ID testing to inspect directory objects and authentication tokens, which represent access permissions. Explore collected configuration offline, test token exchanges, and assess conditional access and device controls.

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

• Mapping tenant users, groups, roles, and applications
• Reviewing conditional access policies
• Testing token exchanges and device-based single sign-on

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

Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.

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

• Compare technologies before choosing one
• Document the reasoning behind a design decision
• Review a proposed system design

Design and review system architecture, compare databases and structural approaches, and document technical decisions. Included tools generate architecture diagrams, inspect dependencies, and assess project structure to identify circular relationships, excessive coupling, and opportunities for improvement.

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

• Comparing monolith and microservices approaches
• Choosing a database for project requirements
• Generating diagrams from an existing project

Check whether development tasks are ready for implementation by reviewing acceptance criteria, design decisions, dependencies, and required evidence. Receive one of four verdicts for each task, with specific gaps and suggested fixes.

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

• Checking a task before assigning implementation
• Reviewing all tasks in the current sprint
• Finding ambiguous acceptance criteria

Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.

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

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.

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

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Create and organize API documentation, READMEs, onboarding guides, and architecture decision records that explain design choices. Structure content around readers’ tasks, with consistent terminology, complete code examples, and separate sections for instructions, reference details, and explanations.

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

• Writing a README with installation and quick-start instructions
• Documenting API parameters, return values, and errors
• Recording architecture decisions and their consequences

Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.

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

• Build planning files from existing project documents
• Add documented requirements and phases to an existing plan
• Identify conflicting statements across planning documents

Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.

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

• Compare technologies before choosing one
• Document the reasoning behind a design decision
• Review a proposed system design

Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.

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

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth Toolkit

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

Inspect ADR health read-only; optionally select one ADR with --adr N.

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

Real-time quotes, K-line charts, order book, trade ticks, intraday capital flow, market sentiment temperature, trading session schedule, security lists, exchange rates, and IPO calendar for HK/US/A-share/SG via Longbridge. Also covers ADR premium and FX carry frameworks. Triggers: "股价", "行情", "K线", "走势", "盘口", "资金流", "市场温度", "汇率", "IPO", "打新", "隔夜股", "ADR溢价", "外汇套息", "K線", "盤口", "資金流", "市場溫度", "匯率", "ADR溢價", "外匯套息", "现在多少钱", "多少钱", "stock price", "quote", "kline", "chart", "depth", "orderbook", "capital flow", "market sentiment", "exchange rate", "IPO calendar", "security list", "ADR premium", "fx carry", "market open", "trading hours", "开市", "溢价", "NVDA.US", "700.HK", "600519.SH", "股價", "走勢", "開盤", "今天開市"

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

Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.

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

Presentation/Core/Engine split control plane — the canonical entry point for any work decomposing the Yuzu server into three binaries (presentation · core · engine) per ADR-0031-presentation-core-engine-decomposition / ADR-0032 (the admission interlock) / ADR-0033 (access-control spine). Use when the user says "/split", "/pce-split", "/decomposition", asks to plan or implement a split workstream (WS-A*, WS-B*, WS-X*), asks "what's our gap to the presentation/core split" or "is it safe to extract presentation/the engine yet", asks to audit split readiness, or starts work touching the seam (handlers calling stores directly, the INV-31-4 contract test, the Drogon port, `server/presentation` or `server/engine`, the `uce` DB grants, component service identity, or the ADR-0032 admission/grant/audit substrate — `use_case_run_id`, the release log, the capability-declaration registry).

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