Working From a Document the User Already Has

The same rule governs Phases 3, 4 and 5. If Phase 2 turned up an existing job post, interview guide, or offer letter, that document is the structural template.

The rule

The user's format is the source of truth. The reference file is a checklist, not an override.

Mirror their section names, ordering, tone, and any boilerplate they have established — company description, benefits blurb, how-to-apply language, signature blocks, legal clauses. Someone who has already settled on a format has usually settled on it for a reason, and a silent rewrite reads as the skill knowing better.

The merge step

1. Map the existing document's sections against the matching reference file.
2. Identify what the reference has that their version does not.
3. Surface the gaps in one question before writing.
4. Add the missing components only if the user confirms.

Never silently expand their format.

How the question sounds

Phase 3, job post:

"Your existing JD has a responsibilities section and requirements list, but I didn't see an opening hook or a description of what success looks like in year one. Want me to add those, or keep it to your current format?"

Phase 4, interview guide:

"Your existing guide has a question bank and scoring rubric, but I noticed it doesn't include an interview stage map or a debrief guide. Want me to add those, or keep it to your current structure?"

Phase 5, offer letter:

"Your existing offer letter has compensation and position details, but I noticed it doesn't include an at-will employment clause or a legal review disclaimer. Want me to add those, or keep it to your current format?"

Short, specific about what is missing, and easy to decline.

When nothing was found

Build from scratch using the phase's reference file as the full template. No merge question is needed — there is nothing to merge with.