개발 스킬

Convert scattered progress notes, RAID changes, and milestone movement into a clean weekly or biweekly status update. Use when the work is routine status packaging or steering prep. Do not use for project governance design, root cause analysis, or deep portfolio risk assessment.

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

Conduct strategic analysis using Porter's Five Forces, PESTEL, and SWOT frameworks. Assess competitive dynamics, macro environment, and internal capabilities. Synthesize into strategic implications with ranked options. Use when entering new markets, evaluating competitive position, or strategic planning.

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

Rapidly map a new codebase, identify the runtime model, risk zones, and first high-value next steps.

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

Design and facilitate structured workshops using Design Thinking and Liberating Structures. Produces detailed agendas with time blocks, facilitation notes, participant materials, and retrospective templates. Use when running ideation sessions, retrospectives, planning workshops, or collaborative problem-solving.

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

Evaluate and tier suppliers using a weighted scorecard per SCOR DS Supplier Management practices. Score Quality, Delivery, Cost, Responsiveness, and Sustainability. Classify suppliers as Strategic, Preferred, Approved, or Conditional. Use during vendor reviews or procurement decisions.

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

Summarize support tickets, chats, and customer threads into issue, impact, status, owner, and next response. Use for customer service handoffs, escalation triage, and support backlog review.

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

Analyze survey and feedback data with statistical distributions, cross-tabulations, significance testing, and open-ended theme extraction. Produces executive-ready survey reports with segment comparisons and action recommendations. Use when processing NPS, CSAT, employee engagement, or market research surveys.

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

Triage email, Slack, ticket, or shared request backlogs into priority buckets, owners, and next actions. Use when the work is repetitive queue handling, intake cleanup, or response sorting. Do not use for strategic decisions, policy interpretation, or substantive contract review.

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

Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.

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

Define a Lean Six Sigma improvement project using DMAIC, problem framing, baseline measures, root-cause hypotheses, CTQs, and control planning. Use when an existing process is underperforming and the team needs a charter, SIPOC, baseline, and improvement path. Do not use for brand-new process design or vague complaints with no process boundary.

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

Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.

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

Read and interpret financial statements — Income Statement, Balance Sheet, and Cash Flow Statement. Calculate key ratios, identify trends, and produce an analysis narrative. Use when reviewing company performance, preparing for investor meetings, or conducting due diligence. Do not use for preparing or auditing financial statements — this is an analysis tool only.

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

Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.

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

Turn ambiguous requests into an executable implementation plan with assumptions, sequence, acceptance checks, and rollback thinking.

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

Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.

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

Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.

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

Draft crisis communication packages including holding statements, stakeholder updates, Q&A documents, and internal briefs. Follows ICS (Incident Command System) communication principles. Use during PR crises, data breaches, product recalls, or any event requiring rapid coordinated messaging.

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

Build customer health scores and churn risk models using leading indicators. Define health dimensions (Usage, Engagement, Support, Sentiment, Contract), weight and score customers, segment into Healthy / At-Risk / Red, and generate intervention playbooks. Use during QBR prep, customer success reviews, or when churn spikes.

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

Build change management plans using ADKAR and Kotter's 8-Step framework. Covers stakeholder readiness, communication plans, training schedules, resistance management, and adoption metrics. Use when rolling out new systems, reorganizations, or process changes that affect people.

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

Turn raw budget-versus-actual data into plain-language explanations for non-finance managers. Focus on why numbers moved, what it means for the team, and what action to take — without requiring accounting knowledge. Use when managers need to understand their cost center performance. Do not use for technical accounting analysis, tax preparation, or external audit deliverables.

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

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

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

Write agency-standard creative briefs for marketing campaigns. Structure Background, Objective (SMART), Target Audience persona, Key Message, Mandatories, KPIs, Timeline, and Budget Allocation. Use when briefing agencies, creative teams, or internal marketing on a new campaign.

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

Compare policies, procedures, onboarding files, or operating evidence against a named compliance framework such as AML/KYC, privacy, internal controls, or audit readiness. Use when a team needs a gap matrix, control checklist, remediation priorities, or evidence request list. Do not use when no target framework is specified or when formal legal or regulatory sign-off is required.

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

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

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