Open your Strategist Coach. Invoke the Offer Architect skill. Build your v1 Offer Doc with the principles from 2.2 live in the coach as you go. Plan for 60–90 minutes the first time.
You installed the Offer Architect skill when you set up your Strategist Coach back in 0.2. It's a procedure your Strategist Coach follows when you signal you're ready to build (or iterate) the Offer Doc.
This page walks you through what to expect when you run it the first time — the trigger phrases that invoke the skill, the question sequence the coach will walk you through, what good answers sound like, and how to handle the iteration loop that follows every market conversation you have.
Both are non-negotiable. If either is missing, fix it first — the skill will refuse to build on weak inputs, and you'll waste a session.
If you haven't installed it yet, go back to 2.1. You need the system prompt loaded, the skill-offer-architect.md file in your knowledge base, and your Phase 1 files uploaded.
The coach will move fast through the question sequence. If you don't know what makes the load-bearing four load-bearing, what failure modes look like, or what the value equation is doing — you'll give safe answers without realizing they're weak. Read 2.2 first.
This is a 60–90 minute focused session. The coach will push back. You'll feel friction. That's the point — a comfortable build session produces a weak offer doc. Block the time, kill notifications, and bring honest answers.
Skills aren't buttons you click. They're modes the Strategist Coach enters when you signal intent. Use any of these trigger phrases — or anything equivalent — and the skill runs.
When the skill is active, the coach will:
The coach pushes hardest on the load-bearing blocks (A, B, C). It moves efficiently through the mechanical ones (D, E). It surfaces founder substance honestly (F). Knowing what's coming helps you prepare.
Goes deeper than positioning. Daily experience, what they've already tried, what they won't say out loud.
What specifically changes after the engagement. What they tell a friend six months later.
How the engagement works. What makes your approach structurally different — not "better."
Format, touchpoints, cadence. Access and support structure. Translated to outcomes, not features.
Outcome-value pricing, defensibility test. Guarantee structured by structure, trigger, consequence. Specific CTA.
Personal connection to the problem. Proof points that matter to this specific buyer.
The coach will reject weak answers in the load-bearing blocks. That friction is the point. Here's how to recognize when you're giving a strong answer vs a soft one — so you can correct yourself before the coach has to.
Specific. A scene. Words you'd hear the buyer say.
Abstract. Could be anyone. No buyer would recognize themselves here.
Concrete markers. Things you can point at.
Generic transformation language. Every consultant in your category could promise this.
v1 of your offer doc is almost always wrong. That's expected. The Offer Architect skill isn't a one-time build tool — it's also the iteration engine. Every time you bring real market signal back to your Strategist Coach, you re-invoke the skill and the doc gets sharper.
Your job is to bring honest market signal in, decide what to accept, commit the change. The coach handles the analysis and the rewrite.
The Offer Architect produces your offer doc as structured markdown. It's not chat output you scroll back to find — it's a canonical file in your Compound O.S.
offer.mdoffer.md in your knowledge library (same folder as positioning.md, icp.md, etc.).offer.md, add a changelog: ## v1 — [date] with a one-line note about what's in this version. Every future revision gets its own entry with what changed and why.offer.md to your Strategist Coach projectThe changelog is your reasoning trail. Six months from now you'll want to know which assumption the market corrected and why. It also helps the coach — when you bring new signal, it can compare against past versions to see what's already been tried.
Three causes. (1) The skill-offer-architect.md file isn't uploaded to your project. Check the knowledge area. (2) The system prompt didn't paste correctly — it doesn't know the skill exists. Re-paste from 0.2. (3) Your trigger phrase was too vague. Try one of the explicit triggers: "Let's build my offer doc" or "Walk me through the offer doc."
Older version of the skill file, or the skill file isn't being read. Re-copy skill-offer-architect.md from 0.2, replace the file in your project, start a new chat. Ask explicitly: "Are you reading the skill file? Confirm you see the section hierarchy and pre-delivery checks."
Tell it to stop. The Strategist Coach's system prompt has a hard stop after offer doc v1 — but if you didn't paste the prompt fully, this rule isn't loaded. Re-paste the system prompt from 2.1 and start a fresh chat.
Confirm files are in the project's knowledge area as .md or .txt (not Word docs or PDFs). Start a new chat and explicitly say: "Read my positioning files and the offer-architect skill before we begin."
Don't start over. Tell the coach exactly which section to redo: "Re-do Section 4 — the outcome promise. The current draft is too soft on concrete markers. Push harder."