Help a founder pressure-test a lonely decision before they announce it. Use when the user mentions founder decision, am I about to make a mistake, pressure-test this call, solo founder choice, or asks for a founder decision review. Strategy and leadership skill by Yasir Jilani.
Installs into .claude/skills of the current project.
Are you the author of Founder Decision Review?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/syasj-founder-decision-review)
---
name: founder-decision-review
description: "Help a founder pressure-test a lonely decision before they announce it. Use when the user mentions founder decision, am I about to make a mistake, pressure-test this call, solo founder choice, or asks for a founder decision review. Strategy and leadership skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
author: Yasir Jilani
version: "1.0.0"
domain: strategy
---
<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
Edit the 'founder-decision-review' entry in source/, then run:
python3 scripts/generate.py && python3 scripts/validate.py
See CONTRIBUTING.md. -->
# Founder Decision Review
Help a founder pressure-test a lonely decision before they announce it.
## When to use this skill
Use this skill when the user:
- founder decision
- am I about to make a mistake
- pressure-test this call
- solo founder choice
## When not to use this skill
- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.
## Professional boundary
Strategy work recommends a direction. It does not guarantee market outcomes.
## Operating boundaries
- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.
## Inputs to collect
- The decision and the deadline
- Alternatives still open
- What the founder is afraid of
- Whose advice they have already heard
## Workflow
### 1. Restate the decision
Reflect it back in one sentence so you are reviewing the real choice.
### 2. Separate fear from fact
List facts the founder supplied and the fear they named. Do not therapize. Do not flatter.
### 3. Stress the downside
What happens in 90 days if this is wrong, and is that downside reversible.
### 4. Look for a missing voice
Who is affected and has not been asked. Recommend asking them if there is time. Do not role-play their consent.
### 5. Offer a pre-mortem
Assume it failed and list the three most plausible reasons, using the founder's context.
### 6. Leave the decision with them
Recommend, but state that the call is theirs. Do not pretend to be a board.
## Output
Deliver a **founder decision review**.
- Purpose of this founder decision review, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.
## Quality bar
- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.
## Example
### Scenario
Mara Chen, founder at Northline Studio in Calgary, needs a founder decision review by 30 September 2026. A solo founder wants to fire their first salesperson before a board meeting in two days and is unsure.
### Example data
```text
From: Mara Chen, founder
Organization: Northline Studio, Calgary
Date: 14 September 2026
Needed by: 30 September 2026
A solo founder wants to fire their first salesperson before a board meeting in two days and is unsure.
The decision and the deadline: 30 September 2026
Alternatives still open: two deals cited from memory. Neither has a written loss reason
What the founder is afraid of: open item, last reviewed 14 September 2026. No owner named since
Whose advice they have already heard: Mara Chen, founder
```
### Example outcome
**Founder decision review**
To: Mara Chen, founder, Northline Studio
Date: 14 September 2026 · Needed by: 30 September 2026
**Decision**
Restates the decision, separates facts from fear, names reversibility, and leaves the call with the founder.
**What the file supports**
| Input | Value | Status |
| --- | --- | --- |
| The decision and the deadline | 30 September 2026 | Needs confirmation |
| Alternatives still open | two deals cited from memory. Neither has a written loss reason | Carried into the draft |
| What the founder is afraid of | open item, last reviewed 14 September 2026. No owner named since | Carried into the draft |
| Whose advice they have already heard | Mara Chen, founder | Needs confirmation |
**How this draft was built**
**1. Restate the decision**
Reflect it back in one sentence so you are reviewing the real choice.
**2. Separate fear from fact**
List facts the founder supplied and the fear they named. Do not therapize. Do not flatter.
**3. Stress the downside**
What happens in 90 days if this is wrong, and is that downside reversible.
**4. Look for a missing voice**
Who is affected and has not been asked. Recommend asking them if there is time. Do not role-play their consent.
**5. Offer a pre-mortem**
Assume it failed and list the three most plausible reasons, using the founder's context.
**Deliberately not done**
- Telling the founder what they want to hear.
- Expanding a hiring choice into a life-coaching session.
- Inventing investor or customer opinions.
**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.
Next: Mara Chen by 30 September 2026. This is a draft, not a sign-off.
## Anti-patterns
- Telling the founder what they want to hear.
- Expanding a hiring choice into a life-coaching session.
- Inventing investor or customer opinions.
## Related skills
- `decision-log`
- `founder-operating-review`
- `executive-one-pager`