「prioritization」の検索結果

End-to-end post-GWAS causal inference pipeline orchestrating heritability partitioning, genetic correlation, Mendelian randomization with CHP-aware sensitivity (CAUSE / LHC-MR), colocalization, fine-mapping with SuSiE / FOCUS, mediation, TWAS triangulation, cis-pQTL drug-target MR, effector-gene prioritization (L2G / PoPS / cS2G), and GenomicSEM common-factor GWAS. Use when triangulating causal inference across multiple complementary methods, prioritizing tissues via stratified LDSC, nominating or de-risking drug targets, mapping a lead SNP to a candidate effector gene, modeling shared genetic architecture across correlated traits, or producing a STROBE-MR-compliant publication-grade evidence battery from GWAS summary statistics.

日本語の概要は準備中です。原文の説明を表示しています。

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

日本語の概要は準備中です。原文の説明を表示しています。

Build a single sprint or release test plan. Covers feature decomposition into testable scenarios, requirements-to-test coverage mapping, effort estimation by test type, prioritization matrices (risk × effort), resource allocation, and scheduling with buffers. Use when: "sprint test plan," "release test plan," "what to test this sprint," "test estimation," "coverage mapping." Not for: multi-quarter strategy — use `test-strategy`. Not for: ranking areas by risk — use `risk-based-testing`. Not for: the go/no-go decision itself — use `release-readiness`. Related: test-strategy, risk-based-testing, release-readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

日本語の概要は準備中です。原文の説明を表示しています。

Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in running effective incident postmortems. Covers blameless analysis, root cause investigation, action item prioritization, and building a learning culture. Understands that incidents are opportunities to improve systems, not punish people. Use when "postmortem, incident review, what went wrong, root cause, blameless, outage, post-incident, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Prioritize roadmap initiatives with tradeoffs. Use when a senior developer needs help ranking projects.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

日本語の概要は準備中です。原文の説明を表示しています。

Use when ordering board tasks - set priority/blocked_by/deploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE/ICE only for a genuine "what next" call across several features

日本語の概要は準備中です。原文の説明を表示しています。

Guides founder-PM discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Controlling combinatorial explosion across multi-dimensional axes: minimum coverage sets, execution plans, test/deploy/UX/risk prioritization. Use when scoping multi-axis combinations.

日本語の概要は準備中です。原文の説明を表示しています。

Prioritize drug targets from a ranked gene list (e.g., scRNA-seq DE output) by orchestrating parallel API queries against UniProt, OpenTargets (with integrated DepMap CRISPR essentiality + gnomAD constraint), PubMed, the Human Protein Atlas (HPA), and ChEMBL tool compounds, then re-ranking by a composite score combining protein localization, druggability, disease genetics, tissue specificity (safety), focus-cell-type expression, CRISPR essentiality, LoF safety constraint, and research maturity. Use whenever the user wants to filter, triage, prioritize, or "do due diligence" on a list of candidate genes for drug discovery, especially after a DE / DEG analysis when they say things like "which of these should I follow up on", "filter for druggable targets", "make a target dossier", "rank these for tractability", "annotate these genes for druggability", or "build a target report". Trigger even when the user says just "filter these candidate genes" or hands over a CSV from a DE pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Seed-stage growth playbook focused on channel selection and prioritization. Helps founders with product-market fit decide where to invest limited resources for maximum traction. By @WeiYipei.

日本語の概要は準備中です。原文の説明を表示しています。

Design, prioritize and run measurable growth experiments across acquisition, activation, retention, referral and revenue. Use when a startup needs an experiment backlog, ICE/RICE prioritization, referral or UGC loops, rapid weekly testing, causal measurement, or stop conditions without spam, fake accounts or dark patterns.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。