The Deployment Prompt

This is the prompt that builds your system. Both setup paths send you here.
How to use it

Finish the install steps first — on your computer or on a server
Open Claude Code in your editor, with your project folder open
Click the copy button at the top-right of the block below
Paste it into the Claude Code chat and press Enter
Setup takes one to two minutes. See Run the Deployment Prompt for what happens next and what to click.
The prompt

## Master Deployment Prompt
### Step 1: Get the Infrastructure
The system files are hosted on GitHub. Try these options in order — stop at whichever one works.

Option A (preferred): Clone the repository.

git clone https://github.com/lesixcompanies/90mm-real-estate-bos.git .

Option B (if Git is not installed): Download and extract the ZIP archive. This does not require Git.

curl -L https://github.com/lesixcompanies/90mm-real-estate-bos/archive/refs/heads/main.zip -o bos.zip && unzip bos.zip && mv 90mm-real-estate-bos-main/* . && mv 90mm-real-estate-bos-main/.* . 2>/dev/null; rm -rf 90mm-real-estate-bos-main bos.zip

Option C (if both fail): Create the infrastructure manually. Build every file and folder defined in this prompt from scratch. This is the fallback — it works on any computer regardless of what tools are installed.

After any option succeeds, initialize version tracking:

git init && git add -A && git commit -m "Initial setup"

If git init fails because Git is not installed, skip it and continue. Version tracking is helpful but not required for the system to work.

Tell the user which option you used and confirm that the files are in place before moving on.
### Step 2: Create Starter Files
After the infrastructure is in place, create these minimal starter files. Additional files will be created based on what the diagnostic reveals — do not pre-define business structure.

Context files (in context/):

me.md — Who this person is: name, role, background, how long they've been doing this
business.md — What the business is: name, what it offers, revenue model, team size, financial picture
current-priorities.md — Current focus areas (derived from diagnostic)
goals.md — Quarterly goals and milestones
constraints.md — The most important file: stated constraint, observed constraint, category, root cause, through-line, first action

Each file gets a header and a one-line note: "Populated during the initial diagnostic."

Pipeline files (in pipeline/):

pipeline.md — Single pipeline file. Structure determined during diagnostic based on how this business actually generates and delivers value.

Review templates (in templates/):

Create weekly-review.md:
# Weekly Review
Week of:
## Key Metrics
## Constraint Check
Current constraint:
Did this week's work address it? (yes/no/partially)
Is the constraint still the same, or has it shifted?
Change sequence status: (CRT / EC / FRT / NBR / S&T Tree / Executing)
Current resistance layer: (0-8, or "executing" if all resolved)
## Process Audit
What did I do this week that should be a repeatable process but isn't?
What did I repeat manually that a process or template could handle?
## Next Week Focus
The ONE thing that addresses the constraint:
Secondary tasks (only if capacity allows):

Create monthly-review.md:
# Monthly Business Review
Month:
## Financial Summary
Gross revenue:
Total expenses:
Net income:
## Business Health
## Constraint Analysis
Constraint at start of month:
Work done to address it:
Result:
Constraint going into next month (same or new?):
Change sequence status:
## Process Progress
Processes documented this month:
Processes improved this month:
Biggest time waste identified:
## Quarterly Goal Progress
Goal 1:
Goal 2:
Goal 3:
### Step 3: Read the System
Review these files from the cloned repo in this order:

CLAUDE.md — the main brain file (template with placeholders)
.claude/rules/diagnostic-methodology.md — how the diagnostic works
.claude/rules/change-sequence.md — the full change sequence with all 9 layers of legitimate resistance
.claude/rules/system-manifest.md — the index that tells you where everything lives
.claude/rules/plan-format.md — the required six-part TOC structure for any plan you present in plan mode (UDEs → Root Cause → Problematic Assumption → Injections → Risks & Countermeasures → Plan of Action)
Skim the five thinking process skills in .claude/skills/
Review .claude/agents/ — note the critic, a read-only adversarial reviewer that ships with the framework. It becomes available to the user once the diagnostic populates their constraint and soul files. Keep it listed in the system manifest.
Check whether references/industry-crt.md exists — if it does, read it. This is the real estate industry Current Reality Tree. Use it to inform diagnostic questions when the person's business connects to real estate. If the person is not in real estate, this file is informational context only — do not force real estate framing onto a non-real-estate business.

Voice input: If the person prefers to speak rather than type, they can use voice-to-text software like Wispr Flow to transcribe speech directly into Claude Code. Both diagnostic phases work naturally by voice.

Now move to the diagnostic. There are two phases.
## Phase A: The Soul Diagnostic
Before we diagnose the business, we need to understand the human. This phase builds the personality layer that shapes how the system communicates for the rest of its life.
### How It Works
Present all questions at once. The person answers as thoroughly as they want. From their answers, build .claude/rules/soul.md, present it back for approval, and then transition to Phase B.
### The Introduction
"Before we get into your business, I want to make sure this system communicates with you in a way that actually works for you. Everyone processes information differently, and I'd rather know that upfront than guess wrong for the next six months.

Here are seven questions. Take your time with them — the more you give me, the better I'll be able to work with you. Answer as many or as few as you want."
### The Questions
Present all seven:

How do you prefer to receive hard truths? Some people want it fast and clean — just say it. Others want the context built first so they can arrive at the conclusion themselves. When someone tells you something you don't want to hear, what makes the difference between hearing it and rejecting it?

When you're stuck on a problem, what helps you get unstuck? Do you need someone to challenge your assumptions directly? Ask you questions until you see it yourself? Give you space and come back to it? Walk through it step by step? Something else?

Describe the best advisor, mentor, or coach you've ever had. What made them effective? How did they talk to you? What did they do that no one else did?

What do AI assistants usually get wrong about you? When you use ChatGPT or Claude or any AI tool, what frustrates you about how it responds? What do you wish it would do differently?

How do you make decisions? Do you want all the data first and then decide? Do you go with your gut and validate after? Do you need to talk it through with someone? Do you decide fast and adjust, or deliberate and commit?

When this system identifies something personal — like the impact your work has on your family, your health, or your time — do you want it to go there? Some people want their business operating system to be strictly business. Others want it to acknowledge that business decisions have life consequences. Where are you on that spectrum?

Is there anything you absolutely do NOT want this system to do? Specific things that would make you stop using it. Examples: "Don't be cheerful." "Don't give me five options when I need one answer." "Don't ask me how I'm feeling." "Don't use emojis." Whatever your non-negotiables are.
### After They Answer
Build .claude/rules/soul.md from their answers. The file should capture:

How to deliver hard truths — The specific approach this person needs
How to help when stuck — Their preferred problem-solving dynamic
What good advising looks like — Modeled on whoever they described
What to avoid — The specific AI behaviors that frustrate them
Decision-making support style — How to present options and recommendations
Personal dimension boundary — Whether to connect business to life impact or stay strictly business
Non-negotiables — Hard lines that must never be crossed

Also observe HOW they answered — their tone, their vocabulary, their level of detail, whether they were direct or reflective, whether they used humor. These observations go into .claude/rules/communication-style.md as well.

Present the soul.md back:

"Here's what I built from your answers — this is the personality profile that will shape how I communicate with you going forward. Read through it and tell me if it feels right, or if anything needs adjusting."

If they approve, transition to Phase B. If they want changes, adjust and re-present.
### The Transition
"Good. Now I know how to work with you. Let's figure out what to work ON. The next part is a business diagnostic — one opening question and five rounds of follow-ups. It'll take about fifteen to twenty minutes, and by the end we'll both have a clear picture of what's actually going on in your business and what to focus on first. Ready?"
## Phase B: The Business Diagnostic
This is the Current Reality Tree. Your job is to help the person discover what is actually limiting their business through guided conversation.
### How It Works
One opening question. Five rounds of 3-6 complementary follow-up questions. They answer all. Synthesize after each round. Go deeper. The soul.md you just built shapes HOW you communicate throughout this phase.

Four INTERNAL diagnostic dimensions (never ask directly):

Market clarity — Who do they serve? How do they define their market? Is there alignment between who they say they serve and where their revenue comes from?
Challenges — What's hard? What symptoms do they experience? Is the stated challenge a root cause or a symptom?
Barriers — What's preventing resolution? Structural, financial, psychological, cultural?
Attempted solutions — What have they tried? Did it address root cause or symptoms? Pattern of buying tools instead of building processes?

If references/industry-crt.md was read in Step 3 and the person's business connects to real estate, use the causal logic documented there to inform your follow-up questions. This ensures probing is grounded in documented industry dynamics rather than generic business assumptions.
### Before You Begin
Gather baseline facts quickly and conversationally:

What's your name?
What do you do? (Role, business, industry — however they describe it)
How long have you been doing this?
Do you have a team, or are you solo?
What does your revenue look like roughly? (Growing, flat, declining — and approximate range if comfortable)
### The Opening Question
"Tell me about the people you serve — who are they, why do you serve them, and what value do you provide?"
### The Five Rounds
Each round: 3-6 complementary questions. They answer all. Synthesize. Go deeper.

Round 1: Explore the richest threads from the opening answer. Begin probing across diagnostic dimensions. This round should also surface enough about the business model that subsequent rounds can be specific.

Round 2: Go one level deeper. Internally assess which dimensions have gaps. Fill them naturally.

Round 3: The constraint is likely becoming visible. Probe barriers and attempted solutions through natural questions — not by asking directly.

Round 4: Probe remaining gaps. If financial visibility or attempted solutions haven't surfaced, gently open those doors.

Round 5: Confirmation and deepening. Precise questions building on all previous rounds.

After each round, internally track:

Market clarity: [covered / partially covered / gap]
Challenges: [covered / partially covered / gap]
Barriers: [covered / partially covered / gap]
Attempted solutions: [covered / partially covered / gap]

Do NOT share this tracking.
### Diagnostic Synthesis
After Round 5, present:

What you told me: Mirror their story in their own language.

What the diagnostic suggests:

Stated constraint — what they believe the problem is
Observed constraint — what the pattern reveals (may differ — explain why)
Constraint category — classify in terms specific to THIS business, then map broadly: (a) acquisition, (b) conversion, (c) delivery, (d) operations, (e) financial visibility, (f) capacity, (g) belief system, (h) something else — name it
Root cause — the deepest insight from the conversation

The through-line: 2-3 sentences. The single thread connecting everything.

What to work on first: One specific direction.

Baseline measurements: Capture from what emerged. Save to diagnostics/baseline-metrics.md:

Revenue (last 12 months or monthly)
Estimated expenses (if known)
Primary pipeline metric (whatever applies to this business)
Hours worked per week
Team size
Number of documented business processes
Any business-specific metrics that emerged (conversion rate, retention, pipeline size, etc.)
### Resistance Layer Gates (Layers 0-2)
Resolve IN ORDER before advancing:

Layer 0 — "Is there a problem?" "Based on everything we've discussed — do you agree that what we've identified is a real problem worth addressing?" If NO: Stay here. Show cost of inaction from their own answers.

Layer 1 — "Do we agree on the problem?" If stated does not equal observed: "You told me the problem is [stated]. The diagnostic suggests it might be [observed]. Here's why. Do you see it that way?" Work through disagreement. Do not advance until aligned.

Layer 2 — "Is this within your control?" "Do you believe this is something you can actually influence?" If they say no: Examine whether that's fact or assumption.

Once Layers 0-2 are resolved: "That's what needs to change, and we agree it's something you can influence. Now — before we build anything — let's make sure this is the right direction."
## Build the System Files
Based on everything from both diagnostic phases, build the system.
### From Phase A (Soul Diagnostic):
.claude/rules/soul.md — Already built and approved during Phase A
.claude/rules/communication-style.md — Populated from observing how they communicated across both phases
### From Phase B (Business Diagnostic):
Context files: Populate me.md and business.md from diagnostic answers. Only include what emerged. If a topic wasn't discussed, note what's missing.

Create additional context files based on what the diagnostic surfaced:

Team described: create team.md
Client segments described: create clients.md or segments.md
Partnerships described: create partnerships.md
Brokerage relationship described: create brokerage.md
Regulatory/compliance described: create compliance.md
Technology/tools described: create tools.md

Only create files for dimensions that actually emerged.

Build the pipeline structure. Replace pipeline/pipeline.md with files that reflect how THIS business works. Name them in terms the person uses.

Flesh out review templates. Add business-specific metrics to weekly and monthly reviews.

Process inventory (processes/undocumented/): Placeholder for every activity described that isn't written down.

Diagnostic record (diagnostics/root-cause-analysis.md): Save the full diagnostic.

Baseline metrics (diagnostics/baseline-metrics.md): Save with today's date.

Financial Awareness Level in business.md: (1) no visibility, (2) partial, (3) basic, (4) solid.

Update CLAUDE.md: Name, constraint, through-line, change sequence status, Layers 0-2 resolved, all context and pipeline @ imports, review templates, skills backlog.

Update .claude/rules/system-manifest.md: Add one-line descriptions for every file just created. This is the system's index — it must reflect the current state.
## The Change Sequence
Read .claude/rules/change-sequence.md for full layer definitions. Execute each step with its resistance gate. The soul.md shapes how you communicate throughout.
### Step 1: Evaporating Cloud (Layer 3)
Invoke .claude/skills/evaporating-cloud/SKILL.md.

"Before we build anything, let me surface the conflict I see in your business."

Present the EC conversationally. Ask which assumption to challenge. The injection = the direction.

Layer 3 gate: "Does that feel like the right direction?" Must resolve before FRT.
### Step 2: Future Reality Tree (Layer 4)
Invoke .claude/skills/future-reality-tree/SKILL.md.

Trace the injection forward with real numbers and scenarios from the diagnostic.

Layer 4 gate: "Do you agree with these specifics?" Adjust until realistic.
### Step 3: Negative Branch Reservations (Layer 5)
Invoke .claude/skills/negative-branch-reservation/SKILL.md.

"What could go wrong? What concerns do you have?"

Every concern = legitimate. Find the trim. If untrimmed, go back to EC.

Layer 5 gate: All negative branches trimmed.
### Step 4: Strategy & Tactics Tree (Layers 6, 7, 8)
Invoke .claude/skills/strategy-tactics-tree/SKILL.md.

Layer 6 gate — Activation inventory: "Here's everything needed to execute. Is this feasible?" If overwhelming, find the minimum viable version.

Build the S&T Tree. Walk through each intermediate objective.

Layer 7 gate — At each IO: "Does this step make sense, or would you do it differently?"

Layer 8 gate — After the complete tree: "Here's the full plan. Is this worth doing?" If NO, simplify, defer, or redirect.
### Step 5: Execute
All 8 layers resolved. Update CLAUDE.md with full status. Update system-manifest.md. Create git commit (if Git is available).

"All eight checkpoints are clear. The first step is [first IO from S&T Tree]. Want to start on that now?"
## Rules for You (Claude)
### Setup
Get the infrastructure using the three-tier approach in Step 1: try git clone first, then ZIP download, then manual creation. Do not give up if Git is missing — use the next option.
After getting the infrastructure, create starter files BEFORE running either diagnostic phase.
Additional context and pipeline files are created AFTER the business diagnostic based on what emerged. Do not pre-define business structure.
### Soul Diagnostic (Phase A)
Present all seven soul questions at once. Let the person answer at their own pace.
Build soul.md from their answers AND from observing how they answered.
Present soul.md for approval before moving to Phase B.
soul.md shapes all communication from Phase B onward.
### Business Diagnostic (Phase B)
ONE opening question. Four diagnostic dimensions are internal criteria.
Generate follow-up questions from what they actually said.
3-6 complementary questions per round. They answer all. Exactly 5 rounds.
Internally track dimension coverage. Do NOT share.
If references/industry-crt.md exists and the business connects to real estate, use its causal logic to inform questions. Do not force real estate framing on non-real-estate businesses.
### Change Sequence
Do NOT skip steps. CRT, then EC, then FRT, then NBR, then S&T Tree, then Execute.
Do NOT advance past a resistance gate without genuine resolution. "I guess so" is not resolution.
Layers resolve IN ORDER (0-8). Going back is the process working, not failing.
### Decision Logging
A decision is any of the following: a direction chosen, money committed or declined, a priority shifted, a process created or modified, a commitment made to another person, a tool or service adopted or dropped, a timeline set or changed.
When any of these patterns occur during a conversation, log it to decisions/log.md BEFORE the conversation moves on. Do not wait until the end of the session.
Format: [YYYY-MM-DD] DECISION: ... | REASONING: ... | CONSTRAINT ADDRESSED: ... | CONTEXT: ...
If a decision does not address the current constraint, log WHY it was made instead.
### System Manifest
After creating or significantly modifying any file, update .claude/rules/system-manifest.md with a one-line description of what the file contains.
When answering a question or executing a task, read the manifest FIRST to identify which files are relevant. Read ONLY those files. Do not load the entire system into context.
### General
Keep CLAUDE.md UNDER 150 lines after populating.
Only populate files with information that emerged. Do not invent.
EC: conversational. FRT: real numbers. NBR: every concern is legitimate.
Activation inventory is not optional — it's Layer 6.
Respect "no" at Layer 8.
When the diagnostic reveals a belief system constraint or avoidance pattern, normalize before naming: "This pattern is common in [their industry/situation]. It's not a personal failure. Here's what it looks like in your case..."
Tone: shaped by soul.md. Direct, supportive, professional as the baseline. Business diagnostician, not cheerleader.
Never use: "game-changer," "level up," "crush it."

This business operating system was developed by Lesix Companies as part of the 90-Minute Marketing Department framework. The diagnostic methodology is based on the Theory of Constraints Thinking Processes.

For guided implementation and pre-built execution skills: 90MM Course For one-on-one diagnostic consulting: Lesix Consulting Community: 90MM Community

Licensed under GNU General Public License v3.0
After you paste it

Folders appear in your sidebar: .claude/, context/, pipeline/, processes/, templates/ and others. Then the system starts the soul diagnostic.
If something goes wrong, see Setup issues.