# Frog framework: prompt pack and templates By Kushagra Gupta. Companion to *Frog framework: start with your experience*. © 2026 Kushagra Gupta. All rights reserved. You’re welcome to use this guide and copy or adapt the prompts and templates for your own career preparation, and to share the link. Please don’t republish, host, sell or build this guide, its design or its prompts into a website, product or course without written permission. **Attach this file at the start of a new chat. Use it for the process and file templates only.** Paste each prompt into your AI chat and fill in the [brackets]. The wording here is identical to the guide. ## How to use this pack - Build your records with Stages 1 to 4 (Prompts 1 to 7). Use them with A to D (Prompts 8 to 11). - Keep one current copy of `Career_bank.md` and one record per experience, named `E01_short_name.md`, `E02_short_name.md` and so on. - Attach this prompt pack, `Career_bank.md` and the record you are working on to every new chat. A new chat does not remember earlier ones. - Run Prompt 5 only after Prompt 4 has marked the record Approved. - If your AI cannot create real files, it should return the complete Markdown for you to save. If it says it saved something you cannot open or download, treat it as not saved. - Statuses: Heading only, In progress, Draft for review, Approved. ## Prompt 1: Pick a direction *Stage 1* ```text I’m using the Frog framework to explore my experiences before making career decisions. The goal is a short, honest direction note, not a career diagnosis. If I attach Career_bank.md or my CV, read them first, and treat the CV as incomplete context rather than proof of what I did. Ask me up to five questions, one at a time, about roles I’m considering, what interests me and any constraints I choose to share. I may be unsure, and that is a valid answer. Do not infer my personality or abilities from my degree, CV or job titles. Create or update Career_bank.md. If I attach the Frog templates, follow them. Otherwise keep these sections in this order: Version and Approval lines, Direction note (Confirmed, Possible, Open), Experience index, Next actions, Change history. Raise the version number each time the file changes. Show me the note and ask me to approve or correct it. If you cannot create or edit files, return the complete Career_bank.md as Markdown for me to save, and do not say it has been saved. Finish by suggesting the next step: listing my experiences. ``` ## Prompt 2: Map your experiences *Stage 2* ```text Read my latest Career_bank.md and, if I have chosen to share it, my CV. Help me list short experience headings across coursework, jobs, part-time work, internships, volunteering, society roles, personal projects and changes of direction. Start by walking backwards through my timeline, most recent first, one period at a time, then ask about gaps one area at a time. Do not invent experiences, and use only headings I confirm. Give each heading a stable ID (E01, E02 and so on) in rough chronological order, and never renumber existing IDs. For each one, add the status Heading only and one useful question to explore later. Do not create detailed experience files yet. Once all the headings are listed, update the Experience index in Career_bank.md, show me the changes for approval and only then ask which experience I want to explore first. If you cannot edit files, return the complete current Career_bank.md as Markdown for me to save. ``` ## Prompt 3: Interview one experience *Stage 3* ```text I’m using Frog to explore one experience before deciding which career and interview stories it can support. Read the latest Career_bank.md, my CV if supplied and the latest record for [E##], if one exists. The experience I want to explore is [heading]. Start with what actually happened and what I personally did. Ask one focused question at a time, wait for my answer and probe the parts that remain vague. Follow the evidence, not a fixed STAR template. Ask about a particular decision or disagreement, the alternatives I saw, my responsibilities versus other people’s, what changed, what I can substantiate and what I still do not know. If I mention a number, ask what it measures, the period, the source and whether it is observed, reported or estimated. If I have no number, do not invent or require one. Let me say ‘skip’, ‘not sure’ or ‘pause’. If I correct something you said, follow my correction. Create or update one detailed record named [E##]_short_name.md, marked Draft for review. Start it with Version, Approval and Privacy lines, following the record template if I attach it, and raise the version each time it changes. Keep the chronology, dates if known, my actions separately from others’, evidence strength, open questions and corrections. Update its status in Career_bank.md and show me the material changes. Do not write polished interview answers yet. If you cannot edit files, return the complete current Markdown for both files for me to save. ``` ## Prompt 4: Check every claim *Stage 4* ```text Audit the current [E##_short_name.md] line by line before I approve it. Read it alongside our conversation and any documents I supplied. For each ownership claim, outcome, figure, causal claim, tool and motivation, quote the exact answer or document that supports it. Classify each as directly supported, self-reported, estimated, interpretation or unsupported. Flag wording that makes a team result mine alone, turns an estimate into a realised result or widens the scope beyond what I described, even if I have not questioned it. Show the risky wording beside a narrower alternative and ask me to resolve each uncertainty. Do not quietly substitute your interpretation for my memory, and keep anything we cannot resolve visible as an open question. Show the full audit in the chat. In the record, keep only the corrected wording, open questions, a one-line change history entry and a short evidence list: one line per kept claim giving its category and where it came from, such as ‘my answer in this session’ with the date, or a document name and section. Return the updated draft. Mark it Approved, in the record and in Career_bank.md, only when I confirm. If you cannot edit files, return complete current Markdown for both files. ``` ## Prompt 5: Build an interview card *Stage 4* ```text First check the record’s Approval line. If it is not Approved, stop and tell me to finish Prompt 4 before building the card. Using my approved [E##_short_name.md], prepare a compact interview-navigation section inside that same record. Include a memory cue, four to six interview questions this evidence can genuinely answer, a natural 30-second summary, a natural 60-second answer, three to five likely follow-up probes and any source limits I must remember. Write the answers in plain spoken English I would actually say, not a polished script. Use only confirmed or explicitly qualified evidence, and do not force the story into a role or question where it does not fit. Show the new wording to me for approval, then update this record and the Career_bank.md index. If files cannot be updated, return complete current Markdown for both. ``` ## Prompt 6: End a session with a handover *Any session* ```text We’re ending this session. Create a handover from the latest documents. List every file that changed, its current version and approval status, unresolved questions and the next recommended action. Ask me to check any material factual change before it is finalised. Then return the complete current Career_bank.md and every experience, role, application or interview file touched in this session. If you can create real downloadable files, do so and tell me exactly which ones exist. Otherwise supply complete Markdown under each filename and tell me which files to save. Do not assume the next chat will remember this one. ``` ## Prompt 7: Resume in a new chat *Any session* ```text I’m continuing Frog framework work in a new chat. Read the attached latest Career_bank.md and [E##_short_name.md]. Do not assume you have any file I have not attached, or that you remember earlier chats. Summarise the experience’s current version and approval status, the last approved changes and the most useful next question, then ask it. Ask one question at a time. Keep confirmed facts unless I correct them, and mark new material as Draft for review. When I say ‘save this session’, prepare complete updated versions with changes and approval status. Create files only if your tools genuinely support it; otherwise return complete Markdown for me to save. ``` ## Prompt 8: Compare roles *Use A* ```text Help me investigate [role A] and [role B]. Read Career_bank.md, my approved experience records, my CV if I provide it and the current official job descriptions I paste in. For each role, separate confirmed interests, demonstrated evidence (cite the experience ID), transferable examples, hard requirements such as qualifications or eligibility, unknowns and gaps. Do not treat an attractive story as proof that I meet a formal requirement, and do not diagnose my personality or suitability. Ask me up to three questions where my preferences are unclear. Create or update Role_note.md with a short comparison and the questions I should investigate next, and show it to me for approval. If you cannot edit files, return the complete Role_note.md as Markdown. ``` ## Prompt 9: Improve an application *Use B* ```text I want to improve my own [CV bullet, cover letter or application answer] for [role and employer]. Read my draft, the official job description, Career_bank.md and the relevant approved experience records, plus my CV if supplied. Map the vacancy’s actual requirements to evidence IDs. Suggest specific changes and explain each one, and ask me for my genuine motivation and any missing facts rather than inventing them. Do not introduce metrics, tools, tenure, scope or ownership the records do not support, and keep estimates labelled as estimates. I will review, revise and control the final wording. Remind me to follow the employer’s rules on AI use. Create or update Application_note.md with the requirement map and the edits I choose. If you cannot edit files, return the complete Markdown. Do not apply on my behalf. ``` ## Prompt 10: Plan an interview *Use C* ```text Help me prepare for [employer, role, interview stage, date]. Read the invitation, the official role description, my CV if supplied, Career_bank.md and my approved records. Tell me what is known about this stage and what is uncertain. Use current first-party employer information for factual claims and treat candidate forums as unverified practice leads. Create Interview_plan.md covering motivation and CV walkthrough questions, likely behavioural questions with the experience IDs that can answer them, gaps where I have no strong story yet, and case, technical or group tasks only if relevant. Include a short priority list and preparation plan. Do not invent official interview questions or scoring. Show the plan for my approval, and if you cannot edit files, return the complete Markdown. ``` ## Prompt 11: Practise aloud *Use D* ```text Act as a practice interviewer for [role and stage]. Read Interview_plan.md, the job description, my CV if supplied and my approved experience records. Ask one realistic question at a time and wait for my spoken or typed reply. After each answer, give specific feedback on clarity, reasoning, my actual ownership, accuracy against the record and whether I answered the question. Tell me if I claimed more than the record supports. Ask one follow-up probe on the weakest point, then let me retry once. Record gaps you observed and any new details I confirm in Interview_plan.md, and change a story record only after I approve a new fact. Never invent official scores. If you cannot edit files, return the complete Markdown at the end. ``` ## Template: Career_bank.md ```markdown # Career bank Version: v0.1 Approval: Draft for review Privacy: Private by default ## Direction note Confirmed: Possible: Open: ## Experience index | ID | Heading | Record | Status | Useful question | | --- | --- | --- | --- | --- | | E01 | | E01_short_name.md | Heading only | | ## Next actions - ## Change history - v0.1: ``` ## Template: E##_short_name.md ```markdown # E01: [Exact title] Version: v0.1 Approval: Draft for review Privacy: Private by default Dates: [if known] ## Context and timeline Confirmed: Not remembered: ## My actions and decisions What I did: What others did: Key decision or disagreement: Alternatives considered: ## Outcomes and evidence Observed or reported: Estimated (how and by whom): Unknown: ## Evidence list (one line per kept claim) - [claim] | [category] | [source] ## Reflection What I learnt, in my words: ## Open questions - ## Privacy boundaries Keep private: Never include: real client names, private records, confidential documents ## Interview navigation (added after approval) Memory cue: Questions it can answer: 30-second answer: 60-second answer: Likely follow-ups: Source limits to remember: ## Change history - v0.1: ``` Evidence categories: directly supported, self-reported, estimated, interpretation, unsupported.