코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn ambiguous requests into an executable implementation plan with assumptions, sequence, acceptance checks, and rollback thinking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare customer or executive business reviews with outcome tracking, adoption health, ROI narrative, risks, commitments, and next-quarter plan using customer success and CX frameworks. Use when teams need QBRs, success plans, churn-risk conversations, or executive account reviews. Do not use for generic slide beautification or cold outreach prospecting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build structured behavioral interview guides using the STAR method. Map job competencies to interview questions, provide scoring rubrics (1–5), and include follow-up probes and red/green flag indicators. Use when preparing for hiring interviews or standardizing interview practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review changes with a risk-first mindset that prioritizes bugs, regressions, missing tests, and operational gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 competitive intelligence briefs following the CI cycle — Plan, Collect, Analyze, Disseminate. Profile competitors, create feature comparison matrices, analyze pricing, build positioning maps, and identify win/loss patterns. Use when preparing for product launches, sales enablement, or strategic reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.