187건 · 관련도순
Choose a prioritization method that fits your product stage, team, stakeholder needs, and available data. Get a recommended framework, practical setup steps, a scoring example, and an alternative approach with its tradeoffs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Expert in feature prioritization - the art and science of deciding what to build and in what order. Covers prioritization frameworks, roadmap planning, stakeholder management, and the trade-offs between different approaches. Knows that prioritization is about saying no, and how to make those decisions defensible. Use when "prioritization, roadmap, what to build, feature request, backlog, scope, trade-off, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare nine methods for setting priorities, including RICE and ICE, which score ideas using factors such as impact and confidence. Use formulas, selection guidance, and linked templates to choose an approach for customer problems, initiatives, or requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Rank problems and proposed fixes using four scored criteria: expected benefit, implementation cost, deployment ease, and risk. The skill produces a sorted priority table with scoring rationales and explains why the top three items should come first.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Product manager toolkit covering RICE prioritization, customer interview analysis, PRDs, and discovery frameworks. Use for feature prioritization, user research synthesis, requirement documentation, or product strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides audit findings remediation program management including finding prioritization by severity (critical, high, medium, low), owner assignment, remediation planning, deadline tracking, verification testing, closure criteria, escalation protocols, and management reporting. Covers remediation lifecycle from finding issuance to verified closure. Keywords: audit remediation, finding management, prioritization, verification testing, closure criteria, remediation tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when prioritizing a Salesforce backlog with the MoSCoW method (Must / Should / Could / Won't) plus an effort + value lens, deciding what fits in the next sprint or release, and using WSJF as a tie-break when MoSCoW alone produces ties. Trigger keywords: MoSCoW prioritization, must should could won't, WSJF salesforce, prioritize salesforce stories, sprint commit, backlog grooming. NOT for story writing or splitting (use admin/user-story-writing-for-salesforce). NOT for release train planning (use agents/release-train-planner). NOT for sizing/estimation method debates — this skill assumes a sizing convention is already in place.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prioritize product features, analyze customer interviews, and draft product requirements documents. Scoring scripts and document templates help turn customer problems, expected impact, and development effort into a roadmap with clear scope and success measures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn business goals and customer problems into a product roadmap. Define initiatives, rank priorities, check dependencies and team capacity, and organize releases with clear reasons stakeholders can review and discuss.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates complete conventional non-oncology bioinformatics research designs from a user-provided disease context, process-related gene family or biological theme, and validation direction. Use when a study centers on multi-dataset bulk transcriptome integration, DEG analysis, process-gene intersection, enrichment analysis, GSEA, PPI hub-gene prioritization, TF/miRNA regulatory networks, ROC-based biomarker evaluation, and immune infiltration analysis. Covers five study patterns (process-DEG discovery, enrichment/GSEA interpretation, hub-gene prioritization, regulatory-network and immune interpretation, multi-layer public validation) and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation. Use for Productboard administration, prioritization workflows, and programmatic API operations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
User story mapping for backlog management and outcome-based prioritization. Load during Phase 2.5 (User Story Mapping) to produce story-map.md and prioritization.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master prioritization frameworks, roadmap planning, timeline estimation, and resource allocation. Create executable roadmaps that drive focus and alignment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and maintain a product or project backlog with prioritized items, acceptance criteria, and estimates. Covers user story writing, MoSCoW prioritization, backlog grooming, item splitting, and status tracking. Use when starting a new project and converting scope into actionable items, during ongoing grooming before sprint planning, re-prioritizing after stakeholder feedback or scope changes, or splitting oversized items into implementable pieces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.