개발 스킬

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.

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

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.

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

Record and track organizational decisions using the RAPID framework. Captures decision context, options analysis, RAPID roles, risk assessment, and communication plan. Use when making cross-functional decisions, documenting governance choices, or building an auditable decision trail.

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

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.

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

Analyze Kanban flow metrics to identify bottlenecks and improve team throughput. Covers Cycle Time, Throughput, WIP, and Flow Efficiency using Little's Law and Theory of Constraints. Use when a team wants to optimize delivery flow or improve predictability. Do not use for sprint-based Scrum planning — use sprint-planning-assistant instead.

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

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

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

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

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

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 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.

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

Build and maintain a rolling financial forecast using a 12–18 month horizon. Lock actuals, reforecast remaining periods, extend the planning window, and generate a waterfall bridge showing prior-to-new variance. Use monthly or quarterly when the organization follows a continuous planning cadence instead of annual budgets.

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

Build structured 3-scenario financial models (Base / Bull / Bear) for business planning or investment decisions. Sensitize revenue and cost drivers across scenarios, produce P&L summaries, cash flow bridges, and executive narratives. Aligns with FP&A 2.0 and CIMA Management Accounting standards. Use when leadership needs to understand the financial impact range of a decision. Do not use for statutory financial reporting or audit-ready financials.

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

Build a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.

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

Write blameless incident postmortems following Google SRE methodology. Covers timeline reconstruction, root cause analysis (5 Whys), impact assessment, and action items with owners. Use after production incidents, outages, or significant bugs to prevent recurrence.

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

Write structured job descriptions with clear requirements, responsibilities, and employer value proposition. Follows SHRM BASK competency framework. Adapts tone to employer brand and industry context. Use when creating new positions or updating existing JDs. Do not use for internal performance criteria or career ladder definitions.

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

Draft concise follow-up messages, nudges, reminders, and recap emails from open decisions, stale requests, or recent meetings. Use when the work is repetitive business writing with known context. Do not use for sensitive legal language, high-stakes negotiation, or board-level communication without review.

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

Package interview loops, schedules, feedback follow-ups, and candidate next steps for recruiting operations. Use when the work is routine hiring coordination and recap packaging. Do not use for final hiring decisions, compensation judgment, or sensitive people-policy advice.

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

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.

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

Build or refine brand positioning with audience, category, differentiators, proof, tone, JTBD signals, and competitive context. Use when marketing, founders, or GTM teams need a positioning canvas, messaging pillars, or campaign foundation. Do not use for isolated ad copy tweaks with no strategy question.

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

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.

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

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.

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

Map the end-to-end customer journey across awareness, consideration, purchase, onboarding, adoption, retention, and advocacy stages. Identify touchpoints, pain points, emotions, and Moments of Truth per stage. Use when designing or improving customer experience. Do not use for internal employee process mapping — use process-mapper instead.

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

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.

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

Publish HTML frontend projects to the PushWebly publishing platform, list published projects, obtain shareable project URLs, change a published app's public/private visibility, and package published HTML projects into Android APKs. Use when Codex needs to publish a local zip project, publish and build an APK, build an APK for an existing published project, toggle an app between public and private, list a user's published projects, or log in/register for this publishing platform. Codex should use HTTP APIs with curl when remote MCP tools are not mounted.

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