Hard Call
/em:hard-call — Framework for decisions with no good options.
Before & after
Same prompt, same agent — the only difference is the skill.
Both options have trade-offs worth considering. Shutting down saves costs but might disappoint existing customers and lose revenue. Modernizing keeps revenue flowing but ties up engineering resources. You'd want to think about how many customers rely on the legacy product, what the modernization would actually cost, and whether there are other priorities. It's also worth considering how your team would feel about either decision. What does your current financial runway look like?
HARD-CALL FRAMEWORK: Shutdown vs modernize THE 10/10/10 LENS: If we shut down TODAY: In 10 days, relief (crisis over). In 10 weeks, customers migrated, support tickets drop 30%. In 10 months, regret: legacy revenue gone ($240k/year), team morale hits spike as cutover chaos settles. If we modernize: In 10 days, team anxious (4-month crunch). In 10 weeks, beta ship, customers nervous. In 10 months, problem solved, but engineering burned out, missed 2 new feature launches, customer acquisition slowed 22%. REGRET MINIMIZATION: Shutdown regret scenario (worst case): Largest 3 customers (18% of revenue) churn within 30 days to competitor. Cost: $180k lost ARR + $45k in refunds. Learning: should have offered migration incentive (-$12k). Regret score: 7/10 (recoverable, but painful 6 months). Modernize regret scenario (worst case): Scope creeps, takes 7 months not 4. Ship is late. Customer churn happens anyway as they lose confidence. $45k wasted engineering spend. Regret score: 9/10 (worst of all worlds). RECOMMENDATION: Shutdown path is lower-regret, but ONLY if executed with 60-day customer migration plan (offer 20% discount on new product for 12 months). Cost: $60k discount liability, but prevents $180k churn. DECISION: Announce sunset. 90-day sunset period. Offer migration path. Reallocate engineering to 2 new feature launches. Revenue impact: net negative $120k first year, positive by year 2.
About this skill
name: hard-call description: Use when /em:hard-call — Framework for decisions with no good options.
Hard Call
/em:hard-call — Framework for decisions with no good options. Use when every option is painful and a structured 10/10/10 + regret-minimization pass is needed — e.g. choosing between a layoff and a down round, or killing a beloved product line.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the hard-call skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Hard Call; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: hard-call
description: Use this skill when facing a decision with no good options and a structured framework is needed to choose between two painful paths.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Hard Call
Framework for decisions with no good options, using a structured 10/10/10 and regret-minimization pass.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.