'prioritization' 검색 결과

Analyzes SIEM alert pipelines for rule optimization, alert fatigue reduction, criticality scoring, asset-based prioritization, and correlation rule design using NIST CSF and detection engineering principles..

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

Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).

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

Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for eliciting the requirements in the first place — use admin/requirements-gathering-for-sf. NOT for user-story authoring — use admin/user-story-writing-for-salesforce. NOT for UAT test design — use admin/uat-test-case-design. NOT for Apex test design — use apex/test-class-standards. NOT for backlog prioritization — use admin/moscow-prioritization-for-sf-backlog. More triggers: traceability.md, build-layer traceability, REQ-XXX and FG-XXX id mapping, artefact-to-requirement orphan report, coverage-gap report, check_rtm.py --manifest-dir, owning run-time agent column, design decision ref column, metadata API name in a traceability row.

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

Produces structured U.S. legal audit summaries that distill compliance findings into executive-ready risk prioritization and remediation plans, covering likelihood/impact scoring, consequence analysis, and corrective actions with timelines and owners. Use for legal audits, compliance audits, regulatory audits, compliance gap analyses, risk assessments, audit report summaries, or remediation roadmaps. Trigger keywords: audit summary, compliance findings, audit report, risk prioritization, remediation plan, regulatory exposure, corrective action plan.

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

Use for prioritization, or when there are more tasks than capacity: "what should we do first?", "rank this backlog", "cut scope for the MVP", "RICE score these". Picks a method (RICE, ICE, MoSCoW, impact-effort), scores items and sets a cut line. Skip for choosing between two designs.

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

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.

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

Guide a startup to set a single quantified traction goal and define the critical path of milestones to reach it. Use whenever a founder needs to prioritize activities, set growth goals, define milestones, decide what NOT to work on, plan quarterly/yearly execution, cascade goals to teams, escape the 'too many things to do' trap, or apply a binary on-path/off-path filter to proposed work. Activates on phrases like 'traction goal', 'critical path', 'what should we focus on', 'too many priorities', 'prioritization', 'milestones', 'quarterly planning', 'yearly goals', 'OKRs', 'where should I spend my time', 'what NOT to do', 'company planning', 'goal setting', 'DuckDuckGo', 'roadmap'.

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

개발 전에 제품의 목적을 검토하고 추진 여부, 첫 사용의 장애물, 기능 우선순위를 정리합니다. 근거와 다음 행동을 담은 기획서나 로드맵을 작성합니다.

• 모호한 아이디어의 기획서 작성
• 개발할 기능의 우선순위 결정
• 출시 전 첫 사용 과정 점검

사용자나 상황에 맞는 상위 후보를 고르는 추천 및 순위 처리 흐름을 설계합니다. 후보 수집부터 점수 계산, 선택, 기록까지 여섯 단계로 나누고 실행 가능한 코드 틀을 만듭니다.

• 개인화 콘텐츠 전달 설계
• 검색 또는 RAG 결과 재정렬
• 작업 우선순위 결정

Design the processes connecting marketing, sales, and customer success. Produce documents for lead scoring, meaning prospect prioritization, along with assignment rules, handoff deadlines, deal stages, CRM workflows, and dashboards that show where prospects stall.

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

• Defining marketing-to-sales handoff rules
• Designing lead scores and assignment rules
• Organizing deal stages and CRM workflows

Build an OpenCTI pipeline that adds external context to indicators of compromise, such as suspicious IP addresses. Connect intelligence services, relate indicators to known attackers and campaigns, and score confidence to help analysts prioritize investigations.

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

• Deploying OpenCTI and configuring enrichment connectors
• Automatically adding context to suspicious IP addresses and domains
• Relating indicators to known attackers and campaigns

Create a competitive brief comparing products or specific features, including pricing, positioning, customer feedback, and market changes. Translate findings into product priorities, differentiation choices, and practical material for sales teams or executive discussions.

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

• Set development priorities using feature comparisons
• Decide where to differentiate or match competitors
• Prepare competitive analysis for boards or investors

Analyze team workloads, available hours, and upcoming demand to build a resource capacity plan. Identify staffing gaps and bottlenecks, then compare hiring, contracting, reprioritizing, or delaying work within budget and schedule constraints.

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

• Quarterly staffing and workload planning
• Checking workload imbalances across team members
• Comparing hiring with project reprioritization

Route product questions to a specialist for prioritization, research, analytics, experiments, or implementation. Support recurring discovery by tracking interviews and assumption tests, checking how customer needs connect to proposed solutions, and returning results with a concise digest.

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

• Prioritizing features with an explicit framework
• Planning product experiments and sample sizes
• Tracking weekly interviews and assumption tests

Manage complex software and SaaS projects by assessing schedules, budgets, quality, risks, and team capacity. Compare priorities across projects, identify resource constraints, and turn portfolio analysis into executive reports with recommendations for decisions and follow-up.

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

• Review progress and health across multiple projects
• Assess risks and prioritize response actions
• Rebalance staffing based on team capacity

Turn feature requests and customer interviews into product plans. Rank features with RICE, a scoring method for reach, impact, confidence, and effort, extract research findings, and draft requirements and roadmaps that reflect team capacity.

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

• Ranking feature requests within team capacity
• Finding shared pain points across customer interviews
• Drafting product requirements with success metrics

Investigate hidden attacker activity using focused hypotheses, indicators of compromise such as malicious domains, and statistical checks on logs. Rank investigation priorities, generate indicator sweep targets, and flag unusual behavior for human review.

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

• Prioritizing threat-hunting hypotheses
• Generating log sweep targets from compromise indicators
• Finding unusual activity against historical baselines

Guide product strategy for growing companies by assessing customer fit, product investment priorities, and team structure. Produces scorecards, portfolio recommendations, organization proposals, and board reporting materials to support decisions about what to build and fund.

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

• Defining a product vision for the next three to five years
• Assessing product fit using retention and customer feedback
• Choosing which products to invest in, maintain, or retire

Prioritize product or business assumptions using an impact and risk matrix. Sort them into implementation, deferral, rejection, or testing, then propose experiments for assumptions that need validation, using actual behavior and clear success metrics and thresholds.

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

• Deciding which assumptions to test first
• Comparing assumptions by impact and risk
• Defining experiments and success thresholds

Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.

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

• Reviewing assumptions behind a feature idea
• Assessing risks from three professional perspectives
• Planning how to test uncertain assumptions

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

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

• Grouping customer requests into themes
• Selecting the top three requests for product goals
• Considering alternatives to requested features

Build a graph of functions and calls across multiple programming languages to investigate entry points, paths to sensitive operations, and potential impact. Use the results to prioritize security reviews and connect external findings with source code.

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

• Tracing call paths from entry points to sensitive functions
• Prioritizing code for a security audit
• Connecting calls across language and RPC boundaries

Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.

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

• Agreeing on the user problem before proposing solutions
• Writing a concise problem statement for a PRD
• Finding the underlying problem behind feature requests

Practice spoken answers to product manager interview questions about designing or improving products. Follow six steps to clarify assumptions, choose users, prioritize a problem, and compare solutions before selecting an MVP, a first version with limited scope.

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

• Practicing answers to product improvement interview questions
• Preparing for product design interview questions
• Turning scattered ideas into a clear spoken answer