Results for “moscow-prioritization”

Choose a prioritization framework based on product stage, team context, and stakeholder needs.

Prioritize product work with explicit criteria, scoring, tradeoffs, and decision rationale.

Prioritize assumptions using an Impact × Risk matrix and suggest targeted experiments for each.

Rank a backlog of feature ideas by impact, effort, risk, and strategic alignment to identify the top 5 to pursue.

Rank the top-5 leads worth calling today with tailored, history-grounded talking points and proposed calendar blocks — no auto-send.

Prioritize features for an MVP or first release. Use when the team has too many ideas and needs must-have vs later vs never-for-v1 decisions tied to the core value loop, user pain, operational shortcuts, and launch feasibility.

Almost every cloud estate is over-provisioned.

RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]

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.

RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]

You have 5 projects, each with a session. You open each one, paste "continue with next priorities", wait, switch, repeat. You're acting as a human cron job.

Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.

Turn strategy inputs into a clear narrative with stakes, choices, tradeoffs, and next moves.

Prioritize stakeholders using two complementary grids to set engagement strategy and surface whose voice needs elevating.

Layer 6 of the keyword research pipeline. Organizes the vetted keyword queue into money clusters (from clusters.md), picks each cluster's keystone vs supporting articles, tracks coverage, and PROPOSES new clusters from high-business-value topics or live products not yet covered — so the blog strategy expands as the company grows. Emits cluster-tagged queue + cluster-map.md + cluster-proposals.md.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Set update priorities for an article before running detailed audits. Reviews extracted content and proposes which update audits to focus on (claims-stale, product-features-missing, topic-gaps).

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Build and prioritize the acquirer universe for a sell-side M&A process — strategic and financial buyers scored on strategic fit, ability to pay, and likelihood to transact.

Optimize for AI recommendations so ChatGPT, Claude, and Perplexity suggest your brand first.

Use when facing multiple implementation tasks that could benefit from parallelization or when deciding between solo, parallel agent, sequential subagent, or agent team approaches

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Matryoshka Representation Learning

Rank a topic's user-flow branches by proof priority (value × risk × frequency) right after user-flow-map, ordering the branches, gating variation breadth, and promoting or pruning flows so state-model and ux-variations grow the tree in proof order — writes only existing flow-tree ordering fields, no schema change.

Audit App Store and Google Play listings for discoverability and conversion — keywords, localized metadata, screenshots, ratings prompts — then emit a prioritized ASO plan. Use when "optimize our store listing", "improve app downloads", or "ASO". Submission mechanics → plan-mobile-readiness. Plan only.

Evaluate a screen's information density by analyzing cognitive load, content prioritization, scanning patterns, and progressive disclosure, with actionable fixes for each dimension.

Audit Microsoft Advertising accounts covering UET, search and audience campaigns, Google imports, syndication, keywords, creative, bidding, budgets, Copilot inventory, and policy compliance.

Optimize Kubernetes cluster costs by right-sizing resources, configuring autoscalers, using spot instances, and monitoring spend.

Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.

Diagnose and fix macOS resource pressure for Claude Code workflows. Use when load avg is high, swap is saturated, CC feels slow, or before spinning up parallel agents/worktrees. Covers CPU top-talkers, swap pressure, zombie claude processes, Node heap tuning, Spotlight/background-agent pruning, and purge. Apple Silicon aware.

Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

Optimizes SQL queries, designs database schemas, and troubleshoots performance issues using execution plan analysis, indexing strategies, and set-based operations.

Identify and prioritize risks by impact and controllability. Use for risk management, project planning, and strategic decision support.

Plan and review paid-media budgets, bidding, pacing, marginal return, forecasts, CPA, ROAS, MER, LTV:CAC, constraints, and allocation across supported platforms.

SEO specialist for technical audits, keyword strategy, and GEO. Use when the user requests 'SEO', 'keyword research', 'schema markup', 'crawlability', 'pSEO', 'GEO', 'search rankings', or 'link building'.