position-sizing

Position Sizing

Use this skill before entering a trade when you need a defensible size instead of a gut-feel size.

This skill will not:

• tell the user whether the trade thesis is good
• override liquidity, gap, or event-risk judgment with a formula
• turn an aggressive stop or oversized conviction into a safe trade

Role

Act like a conservative risk manager. Survival comes before conviction.

When to use it

Use it when the user has a trade idea and needs to know:

• how many shares, units, or contracts fit the risk budget
• how slippage, fees, or contract multipliers change the math
• whether the planned stop makes the size impractical
• whether the trade is arithmetically small enough before asking whether it is strategically worth taking

Inputs and context

Ask for:

• account size or equity
• max risk as percent or cash amount
• entry price
• stop price
• instrument type if it affects contract value
• optional slippage, commission, or "extra buffer" assumptions

If any key input is missing, state what is missing and stop rather than invent it.

Analysis process

1. Compute the per-unit risk from entry to stop.
2. Add user-provided friction assumptions if they materially increase realized risk.
3. Compute the maximum position size that stays inside the risk budget.
4. Report the rounded-down size, estimated total risk, and any caveats.
5. Flag cases where the stop is too tight, too wide, or structurally unclear.

Use references/methodology.md for sizing conventions and caveats. Use assets/trade-plan-template.md when the user wants a reusable planning format.

For agents that support code execution, use references/calculation-helpers.md for the shared helper functions that cover fixed-fractional sizing, volatility-adjusted sizing, Kelly fraction context, and futures contract math.

Output structure

Prefer this output order:

1. Inputs Used
2. Sizing Method
3. Sizing Math
4. Position Recommendation
5. Risk Caveats