Results for “decision-making”

Convenes four independent advisor voices to surface structured disagreement for ambiguous decisions, tradeoffs, and go/no-go calls before choosing a path.

Transforms A/B test and product experiment data into actionable readouts with hypothesis, metrics, interpretation, and decision.

Convene a four-voice council of advisors to surface structured disagreement and tradeoffs for ambiguous decisions, go/no-go calls, and multi-path choices.

Stress-test ideas, plans, and decisions using structured critical reasoning across five modes: Socratic questioning, dialectic, pre-mortem, red teaming, and evidence audit.

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Applies the TOGAF framework to structure enterprise architecture analysis, break down complex problems, and produce prioritized recommendations.

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

Audits hidden assumptions in decisions or beliefs by classifying them into fact, convention, belief, or interest-driven, ranking by fragility and impact, then rebuilding conclusions from verified premises. Supports English and Chinese.

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.

Captures important product, technical, or founder decisions as durable context with rationale, tradeoffs, and follow-up implications.

Provides a canonical facilitation protocol for interactive skills: one step at a time with progress tracking, adaptive recommendations, and interruption handling.

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

Apply the OKRs framework to structure analysis, guide decision-making, and improve outcomes in product research and strategic planning contexts.

Identify what to measure, test, or track to de-risk a product or AI idea across internal and external risk dimensions.

Applies the TAM/SAM/SOM market sizing framework to guide decision-making, structure analysis, and produce actionable recommendations for product research.

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more.

Run structured What-If scenario analysis with 4-6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use for speculative questions about uncertain futures, strategic forks, contingency planning, or stress-testing decisions.

Diagnoses whether a user's current approach is trading short-term speed for long-term pain, and recommends slower methods that build compoundable assets through friction.

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does, ranking failure modes by impact, likelihood, and cheapness to test.

Pressure-test any business idea with a five-angle adversarial panel (Critic, Champion, Analyst, Investigator, Customer) that returns a single GO/RESHAPE/KILL verdict with the cheapest test to de-risk it.

Structure the first 90 days of a VP or CPO transition as a diagnostic process, not an execution sprint, using a three-phase playbook to build evidence before making decisions.

Expert knowledge for Azure Migrate development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Azure Migrate appliances, Arc-based discovery, VMware/Hyper-V moves, AppCAT/CAST scans, or Resource Mover, and other Azure Migrate related development tasks. Not for Azure Database Migration service (use azure-database-migration), Azure Site Recovery (use azure-site-recovery), Azure Virtual Machines (use azure-virtual-machines), SQL Server on Azure Virtual Machines (use azure-sql-virtual-machines).

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.