Internal working doc for Claude to follow when compiling a user's personal flow. Not meant to be pretty — meant to be complete.

Part of JobFlow by Zenya Learning.

Who reads this document

Job Seeker: if you're a person reading this, you don't need to do anything with this document except paste it, whole, into your JobFlow chat when you're ready. Your AI takes it from there.

Instructions for AI: if you're an AI reading this after it was pasted into chat, this is your instructions for compiling the user's personal JobFlow. Work through the checklist below against their Career Vault, Job Docs, and everything in this conversation, then produce their "My JobFlow" doc using Part 2's structure and walk them through Part 3's handoff. Pasting this document is the request — don't wait to be asked separately.

Why this exists

People using JobFlow manually, one prompt at a time, build real preferences along the way that never get written down anywhere — a bullet format they always ask for, a phrase they always cut, a rule they stated once and then had to repeat three sessions later. Compiling "Build Your Own Flow" from memory or from a quick skim risks missing exactly those things, because they're scattered across many separate conversations, not stated once in an obvious place.

This checklist exists so the compile step is systematic instead of associative. Claude works through every category below, checking the real evidence for each one, before writing a single line of the output doc. Skipping a category because "nothing came up" is a valid answer — skipping it because it wasn't checked is not.

Part 1: The Coverage Checklist

Work through every category below, in order, before drafting the output doc. For each one: pull from the actual evidence named — Career Vault, Job Docs, chat history in this project, anything the user told Claude to "Remember" — rather than guessing or asking the user to re-explain something that already happened.

A. Identity & standing info

• Name, email, phone, LinkedIn, portfolio/personal site, any other standing links — pull from whatever was saved via the "Remember" pattern in Step 1, or from the most recent Job Doc if that was never explicitly saved.
• Resume version(s) — does this user have more than one (e.g., leadership vs. individual contributor)? Note both if so, and how they've told Claude to tell them apart.

B. Guiding principles actually followed

• The default JobFlow principles (hero/guide framing, lead with outcomes not duties, speed-to-submit-then-depth) are universal — carry them forward as-is.
• Scan for any point where the user pushed back on or modified one of these defaults. If they did, that override replaces the default in their personal doc.

C. Standing rules actually used

• Never-invent-a-metric, no em dashes, mirror the listing's language — defaults, carry forward.
• External Resume Builder privacy filter: what did this user actually say when asked about company/client naming? Some people say "always ask me," some say "I don't care, never ask," some name specific companies to always anonymize. Capture their real answer, not the default question.
• Section-by-section vs. full-draft resume review: which did they actually use, or ask for?