Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write API reference documentation for an endpoint or SDK method. Use when asked to "document this endpoint", "write API reference docs", or "document this SDK method".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing API documentation for completeness, accuracy, and developer experience. Use when asked to "audit our API docs", "are our docs accurate", or "review documentation quality".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing typography in a codebase — find inconsistencies, hardcoded sizes, and hierarchy gaps. Use when asked to "audit our typography", "find hardcoded font sizes", or "our type is inconsistent".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Survey documentation coverage across an API or SDK — find undocumented endpoints and gaps. Use when asked "what is undocumented", "find docs coverage gaps", or "survey our API documentation".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing layout patterns in a codebase — find ad-hoc spacing, inconsistent grids, and missing primitives. Use when asked to "audit our layout patterns", "we have ad-hoc spacing everywhere", or "our grids are inconsistent".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a layout system — spacing scale, grid columns, and layout primitives. Use when asked to "design a spacing system", "set up a layout grid", or "build layout primitives".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design guardrail layers — input classifiers, output validators, PII scrubbers, policy rule engines. Use when asked to "add safety filters", "scrub PII from LLM output", or "design content moderation".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map current AI safety controls — filter inventory, coverage gaps, latency impact, incident history. Use when asked "what AI safety controls do we have", "find guardrail coverage gaps", or "map our filters".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt. Use when asked to "audit our API quality controls", "find missing lint rules", or "assess our API governance".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a type scale and hierarchy — sizes, weights, line-heights, and named tokens. Use when asked to "design a type scale", "set up type hierarchy", or "define typography tokens".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft or review legal ops documents — NDA, MSA, SaaS agreement review checklist, vendor contract terms. Use when asked to "review this contract", "draft an NDA", "what should I look for in this agreement", or "build our contract review process".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build or audit compliance program — SOC2, GDPR, HIPAA, or ISO 27001 readiness assessment, gap analysis, and remediation roadmap. Use when asked to "do we need SOC2", "are we GDPR compliant", "what does our compliance program need", or "build a security policy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document or redesign a business process — standard operating procedure (SOP), process map, RACI, and owner assignment. Use when asked to "document this process", "write a runbook", "design how we handle X", or "map the process for Y".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a threat hunting program — maturity assessment, hunting calendar, and playbook library. Use when asked to "build a threat hunting program", "assess our hunting maturity", or "create a hunt playbook library".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage vendor relationships — vendor selection scorecard, contract review checklist, renewal tracking, and vendor consolidation audit. Use when asked to "evaluate this vendor", "review this contract", "track vendor renewals", or "reduce our SaaS spend".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.