90 件（hoavdc のリポジトリ） ・ 人気順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.
日本語の概要は準備中です。原文の説明を表示しています。
Draft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。