Identify the riskiest unknown and compare confidence against investment size.
npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill bet-sizer
Please help me install this Agent Skill. Skill: bet-sizer Source: https://github.com/microsoft/amplifier-bundle-skills/tree/main/skills/bet-sizer Command: npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill bet-sizer
This Skill helps you judge whether a plan, roadmap item, or investment is asking for more time and commitment than the team can honestly support. It surfaces the single riskiest unknown, checks whether confidence matches the size of the bet, and calls out when a timeline looks more like pressure than belief.
Ask the bet-sizer skill to review this plan and tell me the riskiest unknown, whether the investment is oversized for our confidence, and what smaller bet would de-risk it.
High-intent search queries and answers about installing and using this skill.
Assess delivery risk sizing by identifying the most likely slip factor and comparing it against actual team confidence. If timelines or headcount exceed genuine knowledge, recommend a smaller de-risking bet like a spike or pilot.
Bet sizing matches investment and timeline commitments to actual team confidence. Review it at product checkpoints, roadmap milestones, or funding requests when stated timelines or headcount may exceed what is genuinely known.
Identify the riskiest unknown by reviewing the roadmap to name the single most likely cause of slip or failure. This distinguishes stated timelines from real confidence to reveal where knowledge gaps threaten delivery.
De-risk an oversized product investment by recommending a smaller bet, such as a targeted spike, prototype, or pilot. This aligns the commitment size with actual team knowledge before full delivery.
A delivery timeline looks like pressure when stated commitments exceed actual knowledge. Confidence assessment surfaces this gap by distinguishing between timeline pressure and the team's genuine belief in the plan.
Yes, review a funding request by comparing the requested commitment level against actual team confidence. This identifies the riskiest unknown and calls out when investment decisions outpace genuine knowledge.
cy-waliPlan organizational structure and headcount with cost modeling and hiring roadmaps.
marchattonExecute timeboxed spikes to validate technical unknowns and document proof.
edwardmonteiroTranslate strategy into a sequenced delivery roadmap with risks and stakeholder communication.
augustoheissCoordinate cross-functional projects with timelines, dependencies, risks, and stakeholder communications.
