90건(hoavdc의 저장소) · 인기순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct structured legal due diligence for M&A, joint ventures, or investment transactions. Cover all 9 workstreams — Corporate, Contracts, IP, Litigation, Regulatory, Employment, Tax, Environmental, and Data Privacy. Produce a risk matrix with deal-breaker flags and closing conditions. Use when evaluating a target or counterparty.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break complex work into bounded Codex delegation tasks with clear ownership, expected outputs, and integration checkpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze budget-versus-actual or forecast-versus-actual performance and turn finance data into a management-ready narrative using variance logic, drivers, cash impact, and forward actions. Use when finance, FP&A, or business leaders need commentary, management accounts, or performance explanation. Do not use for bookkeeping entries, tax filing preparation, or legal accounting sign-off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft commercial contracts from scratch by contract type — NDAs, service agreements, vendor contracts, employment agreements, and licensing deals. Follow a clause library approach with risk-balanced terms. Use when creating new contracts. Do not replace legal counsel sign-off on finalized agreements. For reviewing existing contracts, use contract-risk-review instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design KPI dashboards with SMART metrics, visualization selection, alert thresholds, and refresh cadence. Covers leading vs lagging indicators, data dictionary, and stakeholder-specific views. Use when building operational dashboards, executive scorecards, or team performance views.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize month-end or quarter-end close blockers, reconciliations, owners, and evidence gaps into a routine control pack. Use when the work is finance close coordination and issue tracking. Do not use for accounting judgment, policy interpretation, or final technical accounting conclusions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write structured business cases with problem framing, options analysis, financial modeling (NPV/ROI/Payback), risk assessment, and implementation roadmap. Follows HBR business case structure. Use when seeking budget approval, proposing new initiatives, or justifying investment decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.