코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
Facilitate and document Sprint Retrospectives per Scrum Guide 2020. Choose format by team maturity, structure the session, capture action items, and track improvement across sprints. Use after every sprint. Do not use for individual performance reviews, blame sessions, or annual assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct structured root cause analysis using Ishikawa (Fishbone), 5 Whys, and Pareto methods. Suitable for production incidents, quality defects, customer complaints, and recurring operational problems. Use when problems recur or when initial fixes do not resolve the issue. Do not use for one-time, obvious fixes or strategic decision-making.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 phase MCP adoption with a bias toward the smallest set of integrations that materially improve engineering work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and cascade OKRs (Objectives and Key Results) for company, department, team, or project level. Ensure objectives are inspiring and key results are measurable outcomes. Includes weekly check-in template. Use at the start of each quarter or when aligning strategy to execution. Do not use for KPI performance reviews or daily task tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess organizational training needs using ADDIE methodology and Kirkpatrick's 4-Level evaluation framework. Maps performance gaps to learning objectives using Bloom's taxonomy. Use when planning L&D budgets, designing training programs, or evaluating training effectiveness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create structured employee onboarding plans using the 30-60-90 day framework aligned with SHRM best practices. Cover pre-boarding, Day 1, Week 1, and monthly milestones with task owners, success criteria, and buddy assignments. Use when hiring new employees or revamping the onboarding process.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review changes with a risk-first mindset that prioritizes bugs, regressions, missing tests, and operational gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.