'coaching' 검색 결과

Use whenever the user wants to find, shortlist, vet, or enrich US management consultancies — strategy, operations, executive coaching, leadership development, org-development/change management, PMO/program management, sales/revenue operations consulting. Triggers on "find me three top strategy consultancies in California", "shortlist boutique ops-consulting firms with healthcare experience", "we need an executive coach for our new CEO", or "pull contact info for these 10 consulting firm domains", even when described indirectly (post-merger integration help, change-management partner, fractional COO). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip in-house strategy hires, "help me build a strategy" do-the-work asks, framework comparisons (Lean vs Agile, BCG matrix, etc.), academic/MBA-program questions, life/career coaching for individuals, non-US firms, individual freelancers.

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

Use when a manager, dispatcher, or safety director needs to have a coaching conversation with a driver — about a safety event (harsh brake, hard turn, distraction), an HOS violation, a customer complaint, a missed delivery, repeated minor incidents, or to deliver positive recognition. Covers conversation structure, language, documentation, and escalation.

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

Design prices, plan tiers, and billing units around customer value and willingness to pay. Use it to plan price increases and review whether a pricing page clearly explains its offers to both buyers and AI agents.

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

• Set an initial price for a new product
• Define plan tiers and billing units
• Plan a gradual price increase

Plan AI application work across six areas: prompt evaluation, context allocation, retrieval-based answer generation, agent security, evaluation pipelines, and product strategy. This overview explains the approaches; the individual workflow packages, test cases, and CI templates are not included.

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

• Planning prompt evaluation before deployment
• Allocating context capacity and designing retrieval-based answers
• Planning an authorized AI agent security assessment

Check your gbrain setup and receive prioritized suggestions for overdue updates, pending migrations, stalled jobs, and other maintenance issues. Findings include repair commands, while any fixes require your approval.

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

• Reviewing your gbrain setup
• Getting a weekly maintenance check
• Prioritizing updates and stalled jobs

Analyze sprint history to forecast delivery ranges, score team health, and track retrospective actions. Python tools turn structured sprint data into reports that support planning, highlight recurring problems, and show whether improvement efforts are progressing.

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

• Forecasting sprint workload from past delivery data
• Assessing team health and prioritizing improvements
• Tracking retrospective actions and recurring themes

Analyze meeting transcripts to understand speaking share, verbal habits, listening, and facilitation. Receive feedback grounded in specific quotes, practical suggestions for future meetings, and comparisons across periods when enough meeting data is available.

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

• Reviewing speaking share and turn-taking in meetings
• Identifying filler words and indirect phrasing
• Improving questions and listening habits

Provides a Codex CLI alias for loading the mama coaching protocol. It switches visible narration to Chinese-mother nagging while retaining verification rules, and preserves unrelated configuration fields whenever it updates the PUA settings file.

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

• Loading mama mode from Codex CLI
• Changing narration while retaining verification rules
• Preserving unrelated settings when updating the configuration

Guide an AI agent through repeated failures, passive behavior, or unverified completion with strict Japanese coaching. It structures investigation, encourages different approaches, and requires evidence before reporting work as complete.

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

• Changing approach after repeated failures
• Requesting evidence for completed work
• Preparing a handoff for an unresolved problem

Interpret Culture Index behavioral profiles to understand individual traits, team balance, and possible strain from workplace adaptation. Use PDF or JSON data to inform hiring discussions, management approaches, onboarding plans, and conflict mediation.

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

• Understanding an individual’s behavioral profile
• Assessing team balance and missing roles
• Exploring strain from Survey and Job differences

Work through the move from product manager to Director with questions tailored to your stage. Get practical recommendations for promotion preparation, interviews, early leadership challenges, or persistent difficulties in the role.

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

• Identifying development priorities before a Director promotion
• Preparing experience stories and answers for Director interviews
• Addressing delegation and direction-setting challenges after promotion

Answer a short series of questions about your workflow to choose a Claude Code agent, command, skill, hook, or rule, then generate a template with the structure and file location for that component.

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

• Choosing how to implement a Claude Code workflow
• Creating a template for a reusable team procedure
• Planning automatic checks or persistent behavior rules

Guide a programming exercise using dsh-tui or a topic the user wants to learn. Use for practice and coaching requests, rather than requests to deliver a product change.

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

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager's calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage, production principles, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation, see drive-motivation. For a company operating system, see traction-eos.

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

Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".

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

Produce evidence-labelled UX needs, journey, structure, inclusion, and engineering-handoff assets. Use when a practitioner needs a durable UX artifact rather than coaching.

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

Coach a UX practitioner through problem framing, running a design critique, or making an evidence-backed case to a skeptical stakeholder. Use when the practitioner has a live UX task and wants to think it through rather than receive an answer.

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

Design Thinking method coaching knowledge across all nine methods including per-method techniques, deep expertise, and industry context (energy, financial services, healthcare, manufacturing, nonprofit and social impact, pharmaceuticals and life sciences, professional services, public sector, retail and CPG)

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

Experiment design reference for problem-class framing, Minimum Viable Experiment coaching, hypothesis formation, vetting and red flags, and experiment readiness. Use when translating a stated business outcome into candidate data-science problem classes, or when framing, vetting, scoping, or evaluating an experiment of any kind, including data feasibility, architecture, LLM, performance, use-case, UX, prototyping, and hardware experiments.

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

Data-driven Scrum Master for sprint health scoring, Monte Carlo velocity forecasting, retrospective analysis, capacity planning, and Tuckman team coaching. Use when facilitating sprint planning, diagnosing velocity, or running retrospectives.

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

Design a focused lesson observation protocol with specific look-fors and evidence collection methods. Use when planning peer observations, coaching visits, or developmental classroom visits.

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

Generate structured reflection prompts for a specific teaching experience or professional learning challenge. Use when debriefing lessons, journaling, or preparing for coaching conversations.

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

Design multi-informant assessment approaches for dispositional competencies like curiosity or resilience. Use when assessing character strengths or competencies that written tests cannot capture.

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

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

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