코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
Facilitate SAFe 6.0 PI Planning events. Structure the 2-day cadence, generate PI Objectives with Business Value scores, build the Program Board for dependency visualization, and run the Confidence Vote. Use before every Program Increment when the organization follows SAFe.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author structured policy documents and Standard Operating Procedures (SOPs) following ISO document control standards. Covers purpose, scope, roles, policy statements, procedures, compliance monitoring, and review schedules. Use when creating corporate policies, operational procedures, or governance documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build multi-project RAID and RAG views for portfolios, programs, or cross-functional workstreams. Use when PMOs, program managers, or leaders need a real status picture across milestones, dependencies, owners, and escalations. Do not use for a single standup note, one issue ticket, or generic meeting minutes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rapidly map a new codebase, identify the runtime model, risk zones, and first high-value next steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Condense long reports, documents, or data exports into structured summaries with key findings, implications, and recommended actions. Use when the work is distilling dense content for busy readers. Do not use for original analysis, strategy formulation, or when the source material needs expert interpretation beyond summarization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate monthly S&OP or integrated business planning cycles by aligning demand, supply, inventory, capacity, and executive decisions with a standard meeting rhythm and decision log. Use when operations teams need a demand review, supply review, pre-S&OP reconciliation, or executive S&OP pack. Do not use for single-SKU replenishment math only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate and phase MCP adoption with a bias toward the smallest set of integrations that materially improve engineering work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and maintain a Stakeholder Register per PMBOK 8 Stakeholder Performance Domain. Identify stakeholders, analyze using Power/Interest grid, plan engagement strategies, and define communication cadence. Use at project initiation and whenever stakeholder landscape changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and maintain a project Risk Register per PMBOK 8 Risk Performance Domain. Identify risks, assess probability and impact, define response strategies, and track residual risk. Use throughout the project lifecycle — not just at planning. Do not use for operational incident response or security vulnerability scanning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference implementation of a v2 CodexKit skill. Copy this folder as a starting point for new skills. Demonstrates all 10 required sections, 4C verification, and the tier-2 folder structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.