'consulting' 검색 결과

Shows you how to use Cowork's parallel workers to run multiple tasks at the same time instead of one after another — dramatically cutting the time on batch work. For processing large batches of files or research tasks, when running multiple independent analyses simultaneously, or during a performance optimization session. Use when the user says "speed up", "parallel workers", "batch task", "process multiple files", "why is cowork so slow", "faster", "do several things at once", or "can cowork multitask".

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

Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to produce a comprehensive pulse on what happened and what is coming. Useful for reviewing your week, during end-of-week wrap-ups, for preparing Monday priorities, and when catching up after time away. Use when the user says "weekly pulse", "weekly briefing", "week summary", "what happened this week", "weekly review", or "business pulse".

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

Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client relationships, and when multiple clients need isolated context. Use when the user says "set up a client", "new client project", "client system", "client context", "client workspace", or "onboard a client".

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

Teaches you how to delegate tasks to Cowork so clearly that you get exactly what you asked for — every time. Use when learning how to give better instructions, for improving your delegation technique, during early Cowork adoption when results feel off, when writing clearer task descriptions, or when the user says "how do I ask cowork to do things", "delegation tips", "better instructions", "cowork isn't doing what I want", "help me delegate", "my results are bad", "how do I give better prompts", "cowork keeps getting it wrong", "I don't know how to use this", or "how do I get good results".

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

See the difference between Chat and Cowork with a live side-by-side comparison for understanding why Cowork is built differently. Use when evaluating AI tools, for comparing chat versus agent capabilities, during an AI tool decision, when switching from ChatGPT or Claude Chat, or when the user says "what is different about cowork", "cowork vs chat", "why not just use chatgpt", "show me the difference", "compare chat and cowork", or "why should I use cowork instead of chat".

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

A 15-minute guided setup that teaches Cowork who you are, how you work, and what tools you use — so every result feels tailored instead of generic. Use when setting up Cowork for the first time, for personalizing your workspace preferences, during onboarding after your first session, when configuring your tools and context, or when the user says "set up cowork", "configure cowork", "why is cowork giving me generic results", "cowork setup", "personalize cowork", "make cowork know me", "cowork feels like chatgpt", or "how do I get better results from cowork".

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

Discover what Cowork can do for YOUR specific role and tasks, for mapping your daily work to Cowork capabilities. Use when exploring what Cowork offers, for planning your Cowork adoption, during onboarding and role discovery, when figuring out where to start, or when the user says "what can cowork do", "what is cowork", "show me cowork features", "how can cowork help me", "what should I use cowork for", or "cowork capabilities".

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

Write a structured client status report for a consulting engagement. Use when a consultant says "write my weekly status update", "I need to send a status report", "draft the client update", "what should be in the weekly report", "client wants a progress update", "help me write the RAG status", "I need to report on blockers", "end of week update to the client", or "help me communicate what's stuck". Also trigger when someone needs to communicate engagement progress, surface blockers to the client, or flag decisions that need to be made by the sponsor.

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

Write a consulting engagement proposal. Use when a consultant says "write me a proposal", "draft a proposal for [your client]", "I need to send a proposal", "how do I structure a proposal", "client wants a SOW", "write a statement of work", "I need to propose a project", or "help me price and scope this engagement". Also trigger when someone describes a client conversation that ended with "send me something in writing".

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

Structure a consulting findings presentation using the Pyramid Principle storyline. Use when a consultant says "help me structure my presentation", "I have findings and need to present them", "how do I structure the deck", "build me the storyline", "help me tell the story of the findings", "I have data but no narrative", "client presentation is next week", "how do I present recommendations to the steering committee", or "the deck needs a through-line". Also trigger when someone has completed analysis and needs to communicate findings and recommendations to senior client stakeholders in a structured, persuasive format.

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

Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.

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

Use when an ISV or consulting partner is creating, pricing, publishing, or maintaining an AgentExchange listing through the Partner Console — covers the listing plan, the 5-step Listing Builder workflow (Fill in the Basics, Set Pricing, Add Details, Link Your Solution, Grow Your Business), commercialization models (revenue share vs. annual fee vs. freemium), AgentExchange Checkout setup (Stripe connection, pricing plans, fees, geographic eligibility), Private Offers, Security Review gating, and post-publish listing updates. NOT for building the agent or managed package itself (use agentforce/agentforce-agent-creation and devops/second-generation-managed-packages), NOT for LMA/Trialforce licensing internals (use devops/isv-license-management-and-trialforce), and NOT for the customer-side install experience.

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

Use this skill to execute AetherLang V3 AI workflows from Claude Code. AetherLang provides 9 specialized AI engines for culinary consulting, business strategy, scientific research, and more.

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

Phase 5 part of disease-market-sizing-orchestration. Injects consulting palette (navy/gold/blue) + base CSS + floating TOC + section dividers into raw report HTML. Validates token coverage ≥60% (warn) and floating TOC li ≥5 (block). Use AFTER content-verification passes, BEFORE report-bundle-builder build_all_deliverables.

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

Comprehensive Lean Six Sigma consulting skill supporting all belt levels (White Belt to Master Black Belt). Use this skill for DMAIC/DMADV project execution, Lean waste elimination (VSM, 8 Wastes/DOWNTIME, 5S), statistical analysis (process capability Cp/Cpk, control charts, hypothesis testing), and Six Sigma training/education. Triggers include "improve process", "reduce defects", "sigma level", "DMAIC project", "value stream mapping", "Kaizen", "process capability", "control chart", "root cause analysis", "5 Whys", "Fishbone diagram", "FMEA", "DOE", or requests involving process improvement methodologies.

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

This skill should be used when providing ITIL 4-based IT service management consulting. Use this when organizations need guidance on implementing ITIL 4 practices, improving service management maturity, optimizing IT operations, or aligning IT services with business objectives. Provides tailored recommendations based on department, scenario, and organizational context using comprehensive ITIL 4 knowledge.

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

The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).

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

Signpost (not a knowledge pack) for the ECSS European space standards: the E-ST-10 system engineering family, the discipline standards a reader commonly mis-cites (radiation is E-ST-10-12, not a RAM standard; software is E-ST-40, not E-ST-70), the M-branch project management standards, the Q-branch product assurance standards, and the sustainability and system documents, with designation, edition, owner, status, and catalogue URL only. Contains no source content. Free process paths are existing NASA packs in this catalogue, named by slug, and are not ECSS clause substitutes. Several needs have no in-repo pack.

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

Reconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with no standard text; RG 1.152 Rev 4, BTP 7-18, BTP 7-19, other SRP Chapter 7 sections, and NUREG/CR contractor reports are outside the pack; reflects the pinned 2013 and 2016 editions, not later agency actions; synthesized reference notes, not legal or licensing advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. § 105).

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

Signpost (not a knowledge pack) for the railway RAMS and signalling assurance standards: EN 50126-1:2017 and EN 50126-2:2017 (both with A1:2024) for the RAMS process, EN 50128:2011 (A1:2020, A2:2020) for software for railway control and protection systems, and EN 50129:2018 and EN 50129:2026 for safety-related electronic systems for signalling, plus the free CSM regulations and ORR guidance that cover the risk-process need. Contains no source content: each row carries only the designation, title, edition, owner, redistributability status, and an official URL. Use when you need to identify, cite, or locate one of these documents. No in-repo pack covers these standards.

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

Knowledge pack reconstructed from JSP 815 Defence Safety Management System V1.3 (Ministry of Defence, Open Government Licence v3.0): the SMS Framework, all 12 Elements with their Expectations and Performance Statement themes, and Annexes A to F plus H. Covers the Defence Safety Function and which JSP applies, leadership and safety culture, organisation and SEMS applicability, legislation and exemption certificates, risk assessment and safety cases, supervision and contracting, competence and letters of delegation, equipment and infrastructure safety, performance and incident management, and assurance, audit, and the ISO 45001 clause mapping. SCOPE LIMITS: single-source (JSP 815 V1.3 with Annex H V1.2); carries no DEF-STAN 00-051 or DEF-STAN 00-970 content, no JSP 375, JSP 816; acquisition safety policy is in jsp-376, no Annex G (Assurance Toolkit), and no ISO 45001 text (clause numbers only). This pack is reconstructed reference notes, not MOD guidance, and has no official status.

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

Reconstructed reference notes on EASA acceptable means of compliance for airborne software and airborne electronic hardware, built from AMC 20-115D (ED Decision 2017/020/R, AMC-20 Amendment 14, consolidated in Amendment 23) and AMC 20-152A (ED Decision 2020/010/R, AMC-20 Amendment 19, consolidated in Amendment 23), read from the Easy Access Rules AMC-20 compilation (Amendment 23, June 2023) and pinned 2026-09-26. Use for EASA software means of compliance, EASA AEH means of compliance, AltMoC, ETSO software, and the joint software and hardware certification workflow. SCOPE LIMITS: the two AMC sections only; no FAA content (use faa-8110-49); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, or supplement clause text (use avionics-signpost to name them); no Part-21 body; no bulk AMC-20; AMC 20-193 and AMC 20-189 are name-only; reflects Amendment 23 as consolidated in the June 2023 EAR, not a later AMC-20 amendment; synthesized reference notes, not legal advice and not the official AMC. LICENCE: per-document (EASA site reproduction-with-acknowledgement grant, qualified by ED Decision all-rights-reserved footers); pack-level commercial use is not granted.

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

Reconstructed reference notes on US FAA approval guidance for airborne software and airborne electronic hardware, built from four public-domain sources (FAA Order 8110.49A, AC 20-115D, AC 20-152A, AC 00-69; documents dated 2017-07-21 to 2022-10-07, pinned 2026-10-12). Use for how FAA certification staff plan and conduct software reviews (certification liaison, desk versus on-site review, review planning agreements), how the level of FAA involvement (LOI) is picked and scored with the Appendix A worksheets, how software conformity inspection works (software part and installation conformity, ASE and ASI tasks, Form 8120-10), what AC 20-115D recognizes and how DO-178B processes and tool qualification transition to DO-178C/DO-330 (supplements, FLS, UMS, legacy software changes), and what AC 20-152A adds for airborne electronic hardware (simple versus complex custom devices, robustness and HDL code coverage, tool assessment, previously developed hardware, COTS IP, COTS devices, circuit board assemblies), and what AC 00-69 adds as best practices for change impact analysis, data and control coupling, and design-level error handling (best practices, not guidance and not a means of compliance). SCOPE LIMITS: FAA guidance only, and guidance is not regulation (ACs are acceptable means, not the only means); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, supplement, or SAE ARP text, which are copyrighted and named only (see the avionics-signpost pack); no AC 00-72 (named, not packed); no DO-178C software-level objective tables; no EASA AMC 20-115D or AMC 20-152A content (use easa-rules); reflects the pinned source dates, not later FAA actions; synthesized reference notes, not legal advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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

Reconstructed reference notes on US FDA medical-device software regulation, built from seven public-domain FDA sources (the QMSR final rule 89 FR 7496, FDA device software guidance documents, and the eSTAR program page; pinned 2026-10-12). Use for regulatory pathways and premarket submissions (510(k), De Novo, PMA, eSTAR), premarket software documentation levels (Basic or Enhanced), software validation and Computer Software Assurance, the Quality Management System Regulation (QMSR, 21 CFR 820), medical-device cybersecurity (secure product development, SBOMs, FD&C Act section 524B, labelling), clinical decision support boundaries, off-the-shelf software, MDDS and other software-function scope questions, and the 510(k) software-change trigger. SCOPE LIMITS: US FDA device regulation only; no EU MDR or UKCA content (see `med-device-eu`); no ISO 13485, ISO 14971, or IEC 62304 text, which are named and summarized only as FDA obligations; no drug, biologic, or combination-product rules; reflects the pinned source dates, not later FDA actions; synthesized reference notes, not legal advice and not a substitute for the guidance documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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