Development skills

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Review changes with a risk-first mindset that prioritizes bugs, regressions, missing tests, and operational gaps.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Package interview loops, schedules, feedback follow-ups, and candidate next steps for recruiting operations. Use when the work is routine hiring coordination and recap packaging. Do not use for final hiring decisions, compensation judgment, or sensitive people-policy advice.

The English summary is being prepared. Showing the original description.

Triage email, Slack, ticket, or shared request backlogs into priority buckets, owners, and next actions. Use when the work is repetitive queue handling, intake cleanup, or response sorting. Do not use for strategic decisions, policy interpretation, or substantive contract review.

The English summary is being prepared. Showing the original description.

Turn ambiguous requests into an executable implementation plan with assumptions, sequence, acceptance checks, and rollback thinking.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.

The English summary is being prepared. Showing the original description.