Produce and deliver the templated output
16 primitives in this stage — 16 skills. Concept-stage catalogue, kept vendor-agnostic.
Draft finding prose from a structured verdict →
"I've scored every dimension — now I need the numbers to become sentences a client can actually read."
Resolve layout and visual formatting judgement calls →
"The merge tool got the content in — but the document still looks like a populated form, not a polished deliverable."
Synthesise the headline verdict and cross-section summary →
"Every section is written but I still need the one paragraph that tells the client what it all means."
Draft interpretive commentary and recommendations →
"The verdict is set — now I need the 'so what do we do about it' that turns a scorecard into a brief they can act on."
Inject client-specific context and tone →
"The content is solid — but it still reads like a template with names swapped in, not something written for this client."
Judge whether populated content is real or stub →
"The scan says it's filled — but I need to confirm it's actually saying something rather than just occupying space."
Reconcile scores against supporting evidence →
"Assembly can drift ratings away from the data — I need a pass that checks each score still matches what it's meant to be based on."
Check facts and conclusions agree across sections →
"The sections were written at different times and I need to know they agree before the client reads across them."
Judge overall client-readiness and polish →
"The lint passed but I want a human eye on whether this actually looks like something I'd be proud to send."
Consolidate and apply all QA corrections →
"I have three QA lists in three places — this is the pass where I work through every flag and confirm the document is clean."
Shape the findings into a client-fit narrative →
"The artefact is done but walking them through it page by page will kill the impact — I need a story arc for this specific room."
Anticipate likely questions and sensitivities →
"There's one number in this report that I know is going to land badly — I'd rather have my response ready than get caught flat-footed."
Draft a response to in-session pushback →
"They've just pushed back hard on our headline score and the room is watching how I respond."
Write the handover and usage note →
"I don't want to send a file and have them message me a week later asking what they're supposed to do with it."
Capture the client reaction and any promises made →
"We said three things in the wrap-up and I need to know which ones were real commitments before anyone forgets."
Extract improvement signal for the next run →
"The session is done and I want to capture the two things I'd do differently before the specifics fade."