Offer stack

Every line in the offer removes a pain the buyer has already put a number on. A line with no pain behind it is cut.

Banned: no component without a numbered pain.

The rules and the reasons are in references/offer-stack-context.md. Read it before the first draft.

Start here, every time

Scoring needs no setup. If the user handed you a JSON draft or a path, run the scorer first and report every line. Offer kickoff afterwards.

1. $ARGUMENTS is score, or empty with gtm/offer-stack.json present: run the scorer and stop.
2. kickoff, or no draft: work the checklist below.
3. pain: ask the five questions from the context file and write only the pains list.
4. rewrite: the user pasted an existing offer or pricing page. Turn each line into a component, then ask which pain it removes. Lines with no answer go on a cut list you show them.

The draft lives at gtm/offer-stack.json. Create gtm/ if it is missing. Read brand-config.json at the project root if it exists, for icp and the shared psp block. Never write to it.