'formal' 검색 결과

Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment, automation, or irreversible action whose failure would matter; when the user asks for a quality gate, acceptance criteria, QA, completeness, validation, audit, evidence, preflight, release readiness, or a definition of done; or before claiming completion on medium- or high-risk work. Automatically decide whether a formal gate is warranted, derive task-specific pass/fail criteria, gather evidence, and block unsupported completion. Make sure to use this skill even when the user does not say "quality gate" if consequential work needs acceptance criteria or completion evidence. Skip formal gating for trivial, reversible, low-impact requests.

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

SOP for formal mathematical domain modeling. Trigger when: - Creating new formal models or applying mathematical lenses to analyze existing specifications. - Navigating phases: Identify, Select, Construct, Validate, Record, Connect. - Prompt contains: /form, form workflow, categorical, coalgebraic, linear logic, information-theoretic, validation.

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

Generate formal IT/hardware purchase request documents from informal requirements. Use when creating purchase justifications, cost-benefit analyses, ROI calculations, vendor comparisons, or MARP presentation slides for management approval.

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

Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).

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

Baut und prüft neue Agentenrollen im ellmos-Ökosystem: native Claude-Code- Subagenten (dauerhafte Rollendefinition) und Companion-Worker (SendMessage- wiederverwendete Instanz für eine Ticket-/Aufgabenserie). Formalisiert das bislang unformalisierte eigene Wissen aus dem laufenden Bau von Agentenrollen (ati-agent, bueroassistent, versicherungs-agent u. a.) zu einem wiederverwendbaren Scaffold-plus-Verify-Ablauf. Nutze diesen Skill, wenn eine neue Rolle entstehen soll ("neue Agentenrolle bauen", "Subagent anlegen", "Companion-Worker starten") oder eine bestehende gegen die Haus-Konventionen geprüft werden soll ("ist dieser Agent richtig aufgesetzt?").

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

Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.

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

Defensive counterpart to federated-harbor-redteam: closes the smells that red team opens against The Federated Harbor whitepaper. Federation-specific defenses for cross-harbor primitives — mechanization commitments, scope hedges, cross-paper dependency formalization, pre-emptive analogies (CT, Macaroons, atomic swaps), and defense-in-depth framing (refuses vs prices). Use during a versioned red-vs-white round; pairs with federated-harbor-redteam. NOT for ad-hoc code review, NOT for the Anchor or Bonded papers (use whitehat-defense).

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

Structure persuasive speeches and formal arguments in forensic, legal, policy, and competitive debate styles. Use when the user needs to prepare talks, opening or closing arguments, policy pitches, public explanations, debate speeches, or mentions 'forensic speech', 'formal argument', 'persuasive speech structure', 'debate speech', 'opening statement', 'closing argument'. Turns structured claims into audience-tuned persuasive delivery.

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

경영 판단에 필요한 선택지, 위험, 권고안을 독립형 HTML 슬라이드로 정리합니다. 차분한 남색과 금색 디자인으로 CEO, 전략팀, 이사회에 설명할 자료를 만듭니다.

• 수익화 여부를 결정할 대안을 비교합니다
• 권고안을 담은 이사회 자료를 만듭니다
• 경영진을 위한 전략 설명을 정리합니다

연구 지원금 심사를 위해 가설, 연구 방법, 단계별 목표, 위험을 정리합니다. 상아색 바탕과 검은 글자를 사용해 차분한 글 중심 HTML 슬라이드로 만듭니다.

• 연구 지원금 심사용 자료 제작
• 연구 결과를 글 중심 보고서로 정리
• 학술 및 정책 설명 자료 제작

Have agents with different roles challenge a proposed approach, exposing weak assumptions, missed interactions, and unnecessary complexity. Surviving findings go to a dedicated planning agent, which produces sequenced tasks with explicit success criteria.

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

• Checking assumptions before committing to a plan
• Finding integration risks and overlooked edge cases
• Challenging unnecessary complexity in a design

Uses multiple agents with different critical roles to challenge assumptions, complexity, risks, and alternatives. Findings that withstand review go to a dedicated planner, who turns them into sequenced tasks with explicit success criteria.

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

• Reviewing assumptions before implementation
• Checking integration risks and edge cases
• Comparing alternative approaches

Assess scientific claims by examining study design, statistics, bias, and evidence quality. Use structured appraisal frameworks to identify supported conclusions, explain uncertainties, and propose practical improvements with concerns traced to specific evidence.

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

• Check whether a paper's conclusions match its evidence
• Review study design before collecting data
• Identify statistical problems and potential biases

Plan experiments before collecting data. Helps choose study designs, randomly assign subjects or samples, organize treatment combinations, and generate reproducible schedules while checking for confounding and repeated measurements incorrectly counted as independent samples.

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

• Create random assignments for subjects or samples
• Screen multiple experimental factors
• Balance conditions across batches, days, or plate positions

Turn one scientific paper into a structured, 16-section reading card. Break down its methods, connect claims to experimental evidence, identify limitations, and develop research hypotheses, with source references and clear labels for anything the supplied material cannot support.

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

• Break down a paper’s methods and assumptions
• Connect central claims to experimental evidence
• Organize limitations and gaps in supporting evidence

Draft investment committee memos for private equity deals, investments in privately held companies. Combine due diligence findings, financial analysis, deal terms, return scenarios, and risks into a structured document with a clear recommendation.

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

• Preparing approval materials for an investment committee
• Combining due diligence findings into a deal memo
• Comparing base, upside, and downside return scenarios

Turn an existing GitHub Actions workflow into a structured specification for maintenance and AI reference. Document its purpose, triggers, job dependencies, inputs, outputs, permissions, and failure handling, focusing on expected behavior rather than implementation details.

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

• Documenting an existing GitHub Actions workflow
• Reviewing job order and dependencies
• Organizing permissions and failure handling

Design Chinese and English decorative captions for videos using the 非正式发布会 template. The skill defines gradients, textured lettering, keyword animation, and placement based on actual footage, keeping both languages readable and important subject details visible.

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

• Add Chinese and English titles to a template video
• Emphasize product features with animated keywords
• Place outfit labels around a moving subject

Build a ransomware response playbook for security monitoring teams, covering detection, containment, eradication, and recovery. Include log queries, decision trees, evidence collection, backup restoration, and incident reviews to prepare consistent procedures before an attack occurs.

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

• Creating a standardized ransomware response playbook
• Documenting host isolation and recovery procedures
• Addressing coordination gaps found in tabletop exercises

Analyze existing user permissions to propose roles for role-based access control, which assigns permissions by job role. Compare candidate role sets, identify overlap and excess access, and validate definitions against business responsibilities.

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

• Consolidating overlapping access roles
• Redesigning roles from existing permission data
• Reviewing excess and unusual permissions

Create academic Word documents with APA, Chicago, IEEE, or MLA citation formatting. Organize abstracts, equations, figure and table references, footnotes, and bibliographies, with support for two-column journal layouts in a single .docx file.

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

• Formatting a manuscript in APA style
• Preparing a two-column IEEE conference paper
• Adding numbered equations and figure references to a thesis

Turn descriptions and existing notes into a standard operating procedure, a document explaining how work gets done. Capture process flow, responsibilities, detailed steps, exceptions, and metrics so teams can use it for handoffs or audits.

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

• Documenting a process known only to one person
• Clarifying who performs and owns each step
• Preparing procedures for handoffs or audits

Design company discount rules across contract value, duration, payment terms, and strategic value. Build a discount matrix, define approval routes and required commitments for exceptions, and check the policy for gaps, contradictions, and margin violations.

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

• Create a company's first formal discount policy
• Revise discount rules after margin requirements change
• Define approval routes and commitments for exceptions

Review Apache ShardingSphere pull requests or authorized downstream changes using repository evidence. Assess code correctness, merge readiness, or CI failures, then produce consolidated findings or a ready-to-copy reply to a review discussion.

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

• Review code changes for correctness and regression risks
• Assess whether a pull request is ready to merge
• Investigate CI failures