'prioritization' 검색 결과

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Financial goal planner. Takes any goal (house down payment, college fund, wedding, sabbatical, business launch, car, vacation) and builds the required savings amount, monthly contribution, timeline, investment vehicle recommendation, milestone checkpoints, and adjustment scenarios. Supports multiple simultaneous goals with prioritization logic. Produces FINANCE-GOALS.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Kontextspezifische Marketinghypothesen entwickeln, vorprüfen und als messbare Experimente priorisieren. Nutze diesen Skill, wenn Ideen für Kanäle, Kampagnen, Angebote oder Wachstum gesucht werden, wenn eine Ideenliste auf Risiko und Machbarkeit geprüft werden soll, oder wenn aus Vorschlägen Experimentsteckbriefe mit Metrik, Laufzeit, Budget und Stopkriterium werden sollen. Sortiert vor der Bewertung aus, was rechtlich, plattformseitig oder finanziell nicht tragbar ist, und trennt Evidenz von Vermutung. Führt keine Kampagne aus und schaltet keine Anzeigen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

新号没粉丝、推文没人看、怎么度过冷启动时用。涨粉四步漏斗(曝光→展开→Profile门面→关注)诊断丢哪步,按边际回报排序投六策略:大V评论区抢占(最高)/引用转发+深度观点/每日发推/互关社区(≤15/天)/蹭热点/互动率优先;前24h主动加热突破初始池。Trigger:"没粉丝""帖子没人看""冷启动""怎么起量""0 followers""no engagement""cold start"。不适用:开业前装修/蓝V/养号(→x-account-setup)、已有稳定粉丝日常运营、限流封号排查(→x-account-pitfalls)、纯评论技巧(→x-comment-engagement)。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

量化排序功能/需求/实验时使用。适用于 backlog 排序、季度规划、决定先做什么。优先使用 RICE 评分（有数据时）或 ICE 评分（快速决策时）。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic product leadership guidance for SaaS and technology companies. Covers product strategy, roadmap planning, product discovery, user research, growth product management, platform strategy, product analytics, and product launches. Use when defining product vision, prioritizing features, conducting discovery, analyzing metrics, or launching products. Use for "product strategy", "roadmap planning", "feature prioritization", "product discovery", "product metrics", "PRD writing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Clarify priority and emphasis by fixing unclear primary actions, competing visual weight, loud section titles, and weak label/value treatment. Use when the user mentions hierarchy, prioritization, too much competition, grayscale confusion, loud headings, or unclear primary actions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cybersecurity partner skill for acting as a practical security collaborator across architecture review, threat modeling, secure design, risk prioritization, defensive planning, vulnerability remediation, incident readiness, security roadmaps, and technical decision support. Use when the user wants an ongoing security advisor, reviewer, or second set of eyes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage LLM context budgets—prioritization, summarization, compaction, and what to load vs reference. Use for long sessions, large repos, or multi-doc tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"SME and family-business management for Taiwan's industrial structure (98% SME, 70%+ family-controlled listed). Integrates four pillars: resource-constrained decision-making, family governance (Tagiuri-Davis three circles), four-layer succession, and professionalization. Use for sub-200-employee strategy, capital-constrained prioritization, family-vs-professional-manager conflict, founder handover, family-constitution design, or SME financing limits. Triggers: 『二代接班』『家族企業』『中小企業』『家族憲章』『家族辦公室』『傳承規劃』『小公司策略』『資源有限』『家族跟專業經理人』『三圓模型』『隱形冠軍』. For 成大 EMBA SME strategy, 政大 EMBA family-business succession, 逢甲 EMBA SME management cases. Fills Asgard gaps in resource-constrained strategy and Chinese-family governance.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage LLM context windows deliberately — budgeting, prioritization, summarization, and retrieval instead of dumping everything in. Use when prompts grow long, costs rise, or the model loses track of key details.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build autonomous task-driven agents with the BabyAGI loop — task creation, prioritization, and execution from a single objective.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Translate strategy into a balanced scorecard, strategy map, OKR bridge, and executive initiative portfolio with clear measures, targets, and owners. Use when leadership needs strategic alignment, portfolio prioritization, or a management dashboard tied to outcomes. Do not use for ad-hoc brainstorming with no strategic horizon.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this issue still valid?", "what's clogging the backlog?", "run a triage pass", or /gaia-triage. Covers two workstreams: (1) GitHub issue lifecycle — identifying resolved, stale, or need-more-info issues and acting on them via gh CLI; (2) skill-batch intake — evaluating draft proposals in registry-for-review/skill-batches/ and routing them toward promotion or rejection. This is the gatekeeping step before new skills enter the canonical registry; and (3) a cross-repo triage sweep — sizing, P0-P4 prioritization, umbrella/epic synthesis, and assignment across every gaia-research org repo, on the one headquarters tracker.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect, validate, and generate Schema.org structured data with Ahrefs traffic prioritization. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", "markup", or "schema priority".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Annotate genetic variants (GWAS hits, eQTLs, rare variants) with ENCODE functional data to interpret non-coding variation. Use when the user has variants of interest and wants to understand their regulatory context, identify causal variants from GWAS loci, assess variant impact on regulatory elements, perform enrichment testing of variant sets in tissue-specific annotations, or link variants to target genes through enhancer-gene maps. Handles the full post-GWAS workflow from variant set → tissue mapping → functional annotation → fine-mapping awareness → enrichment → variant-to-gene → prioritization. Use this skill for ANY variant interpretation task involving ENCODE chromatin, accessibility, TF binding, or 3D genome data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit emergency and crisis triage systems for call prioritization accuracy, resource dispatching algorithm quality, severity classification model evaluation, response time optimization, geographic coverage analysis, mutual aid protocol readiness, and post-incident review workflows..

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.