skills/magicplan-project-summary/references/output-modes.md

# Output Modes

Each mode below is a template for the summary. Fill it from the magicplan data read in Step 2. Keep
observed facts separate from inferences, and never fabricate values. Where a field has no data, write
what is missing rather than leaving it blank or inventing it.

## 1. Client call prep

A brief to glance at while on the phone. Optimize for skimming, not prose. No file header needed unless
the user wants a leave-behind.

```
# Call prep — [Project name] · [Address]
Claim/loss: [loss type, category/class if set] · Documented [date]

## Where things stand (say this first)
- [1–3 plain-language sentences on the current state]

## Rooms affected
- [Room] — [damage in one line]
- [Room] — [damage in one line]

## What we've documented
- Photos: [n across m rooms] · Moisture readings: [status] · Estimate: [status]

## Likely client questions & answers
- "How long will drying take?" → [answer from readings/goals, or "still assessing"]
- "What happens next?" → [next step]
- "Is this covered?" → [neutral: defer to carrier/adjuster]

## Watch-outs (don't over-promise)
- [Any gap or unknown that could bite you on the call]
```

## 2. Client email / update

A ready-to-send message. Warm, plain-language, reassuring but honest. No jargon, no S500 codes, no
carrier-facing hedging. Include a subject line and the company header.

```
Subject: Update on the water damage work at [address]

[Company name] · [phone] · [email]

Hi [client first name],

[One warm sentence acknowledging the situation.]

Here's where we are: [2–4 sentences — rooms affected, what's been done, what's happening now, and the
next step with rough timing.]

[If there's something you need from them — access, a decision — one clear ask.]

[One sentence of reassurance and how to reach you.]

Best,
[Name], [Company name]
```

## 3. Internal team brief

An operational catch-up for a colleague or crew taking the job over. Direct, complete, jargon is fine.

```
# Internal brief — [Project name]
Assignee: [name] · Address: [address] · Last modified: [date]

## Loss
[Type, cause if known, category/class, migration path.]

## Rooms & measurements
[Per affected room: dimensions, affected floor/wall area, ceiling height.]

## Equipment on plan
[Air movers, dehus, cavity dryers, meters, per room.]

## Documentation status
Photos: [per room]. Moisture: [per instrument]. Forms: [which]. Estimate: [status].

## Gaps to close
[Bullet list of documentation gaps and open questions.]

## Next actions
[Concrete crew actions.]
```

## 4. Adjuster / carrier status

Neutral and factual. Present conditions observed, not advocacy. No editorializing about whether the
estimate is high or low. Mirror the tone of the adjuster-handoff playbook. This is a lightweight status,
not the full handoff — if the user wants the complete carrier package, point them to the
adjuster-handoff skill.

```
# Project status — [Project name]
Address: [address] · Loss documented: [date] · Prepared by: [company]

## Property & affected areas
[Property type, floors, approximate area. Affected rooms by name/floor with the documented damage type.]

## Documentation on file
Photos: [count]. Moisture readings: [status]. Forms: [which]. Files: [which].

## Estimate posture
[What the estimate covers and its status — no opinion on adequacy.]

## Open items
[Neutral questions: field re-inspection, pending approvals, access, third-party testing.]
```

## 5. Quick status

No file. A short in-chat readout: one line on overall state, affected rooms in a compact line,
documentation status in a compact line, and the single most important gap. Offer to expand into any of
the fuller modes.