underwrite

Estrelas5

Forks1

Atualizado7 de julho de 2026 às 21:21

Underwrite a screened Target to the IRR hurdles and set the walk-away price (GATE 1: the user approves the number).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

Play-New

Play-New/bending-spoons-ontology

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas financeiros e de investimentosNegócios e Operações Financeiras·SOC 13-2051

SKILL.md

readonly

name	underwrite
description	Underwrite a screened Target to the IRR hurdles and set the walk-away price (GATE 1: the user approves the number).

Execute the underwrite verb of the Bending Spoons world model, per its contract.

Read the contract: capabilities/actions/deal-value.md — parameters, submission criteria, gate. Follow it exactly.
Build the ASSUMPTIONS with the user before any number (the contract's anti-bias rule: assumptions are frozen BEFORE the model runs — will.md, deal discipline):
- 5-yr FCF trajectory attributable to the business (pre-diligence = estimates, say so)
- terminal value: years 6-10 growth + WACC (current method) or EV/EBITDA at year 5 (legacy)
- levered case: assumed debt = LOWER of 85% of EV and what 5-yr FCF can repay
- margin of safety: does the case hold "even under severely unfavorable scenarios"? Then compute levered/unlevered IRR and the walk-away price; the engine enforces 65/25.
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('underwrite', PARAMS), indent=2))" If the engine REFUSES, report the refusal verbatim — it is a submission criterion firing (a will constraint or an invariant), not an error to work around.
Show the user: the checks, the gate, and the exact diff. GATE 1: the walk-away price needs the user's explicit approval by name.
Only on the user's explicit yes, apply (phase 2): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine; print(engine.apply('PROPOSAL_ID', 'USER_NAME'))" The engine runs the audit and commits if green; report the outcome. Never edit the csvs directly.

Mais deste repositório

mesmo repositório

radar-sweep

Play-New/bending-spoons-ontology

The market-radar's sensing pass — sweep recent public signal (HN + Reddit, free, recency-windowed) on a company or theme and bucket every hit against the contract's watch signals (distress, ownership, momentum, valuation, AI-pressure). Use to scout a candidate or refresh the pipeline.

2026-07-085

bsp-audit

Play-New/bending-spoons-ontology

Run the model's audit (the model's audit service, mechanical subset) and summarize — green/red, defects with the invariant each violates. Run after any batch of edits.

2026-07-075

Play-New/bending-spoons-ontology

Close an acquisition: create the Deal + Business + Interface(s) (GATE 2: go/no-go is the user's).

2026-07-075

deal-desk

Play-New/bending-spoons-ontology

The desk over the whole deal machine — pipeline status, pending proposals, and which verb applies next. Start here ("/deal-desk") to see the state and be guided to the right action skill.

2026-07-075

hire

Play-New/bending-spoons-ontology

The hiring assistant — run a candidate through Bending Spoons' selection funnel and score them against the disclosed gates. Read-only, advisory: it drafts a recommendation; the committee decides. The people-side twin of screen-target.

2026-07-075

screen

Play-New/bending-spoons-ontology

Screen a Target against the hard gates (the screen verb). Applies auto — the write IS the screen.

2026-07-075

name	underwrite
description	Underwrite a screened Target to the IRR hurdles and set the walk-away price (GATE 1: the user approves the number).

Execute the underwrite verb of the Bending Spoons world model, per its contract.

Read the contract: capabilities/actions/deal-value.md — parameters, submission criteria, gate. Follow it exactly.
Build the ASSUMPTIONS with the user before any number (the contract's anti-bias rule: assumptions are frozen BEFORE the model runs — will.md, deal discipline):
- 5-yr FCF trajectory attributable to the business (pre-diligence = estimates, say so)
- terminal value: years 6-10 growth + WACC (current method) or EV/EBITDA at year 5 (legacy)
- levered case: assumed debt = LOWER of 85% of EV and what 5-yr FCF can repay
- margin of safety: does the case hold "even under severely unfavorable scenarios"? Then compute levered/unlevered IRR and the walk-away price; the engine enforces 65/25.
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('underwrite', PARAMS), indent=2))" If the engine REFUSES, report the refusal verbatim — it is a submission criterion firing (a will constraint or an invariant), not an error to work around.
Show the user: the checks, the gate, and the exact diff. GATE 1: the walk-away price needs the user's explicit approval by name.
Only on the user's explicit yes, apply (phase 2): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine; print(engine.apply('PROPOSAL_ID', 'USER_NAME'))" The engine runs the audit and commits if green; report the outcome. Never edit the csvs directly.