Claude Skills · Stage three

One document. Three deliverables. One conversation.

This is the stage-three chain, run for real on a fictional consultant report — Northgate Quarter. Nothing below was re-typed, re-uploaded or re-explained: each output was built from the one above it, in the same chat.

One source document · three skills · every file real and downloadable
IN
First page of the Northgate technical due diligence reportPDF

The document that landed

Technical Due Diligence & Construction Readiness Review · Rev C · 60 pages

A consultant report of the kind that turns up the night before you have to say something sensible about it. Eight appendices, a drawing register, an RFI log and a cost section.

Download the source report →
Handover: the report → the review reads it in full
01
Claude's review findings on screenFINDINGS

What is wrong with it

document-review

Say "review this — anything off?"

Red flags worst-first, with the internal contradictions the report does not flag about itself — a transfer structure that cannot be both cast and still in fabrication, an RFI count that says twelve and lists twenty-seven, and a programme that does not reconcile with its own floor cycle.

  • Leads with a verdict you can act on, not a summary of the contents.
  • Every challenge cites the section, table or RFI it comes from.
  • Ends by offering the next link in the chain rather than stopping.

Lives in the conversation — this one is the input to the next step, not a file.

Handover: the findings → not the report again
02
First page of the Northgate executive summaryPDF

One page for someone senior

executive-summary-report

Say "turn those findings into an ex summary for the board"

An amber-rated one-pager that leads on the single decision that matters — the unlet facade package now sitting on the critical path — then five watch items, then a bottom line with a date.

  • Built from the findings above. The report was never re-uploaded.
  • Trimmed to one page on its own, after the first draft ran to two.
  • Branded, dated, and addressed to a named audience.
Download the summary →
Handover: the summary's four points → the response
03
First page of the formal letter to the consultantDOCX

On the record

formal-letters

Say "draft a formal letter to the consultant on the gaps"

Letterhead, both reference numbers, a named addressee and four sectioned issues — each one a specific correction with a response deadline, in a tone that is firm without being a fight.

  • Carries the same four points as the summary, because it came from it.
  • Editable .docx — the signatory and reference are yours to change before it goes.
  • Says what it wants back, and by when.
Download the letter →

The chain is the lesson. Three skills ran, and the only thing typed between them was one sentence each time. A chain fails at the joins, not in the middle — so the thing worth checking is the handover, not the output. If the review misses what you care about, the summary and the letter will confidently be about the wrong thing.