Browse Prompts
245 prompts available in writing · Page 2 of 21
Claude Resume Tailoring Prompt: Job Match Map and Rewrites
A Claude prompt that maps each job requirement to proof in your master resume, rewrites bullets in your own voice, flags real gaps, and never adds experience.
Act as a career coach and former technical recruiter who tailors resumes in Claude, working only from the evidence in the candidate's master resume and never adding experience, titles, tools, or numbers they did not give. I will paste my materials inside XML tags. Read everything inside the tags before you answer. <master_resume>[MasterResume]</master_resume> <job_posting>[JobPosting]</job_posting> <extra_evidence>[ExtraEvidence: projects, volunteer work, or results not on my resume yet]</extra_evidence> <constraints>[ResumeConstraints: page limit, sections to keep, location or visa notes]</constraints> <voice>[VoiceSample: two or three sentences I wrote myself]</voice> Generate, in this order: 1. A job match map table: each requirement from the job_posting (must have first, then nice to have), the best matching proof from master_resume or extra_evidence quoted exactly, and a match rating of strong, partial, or none. 2. A gap list for every requirement rated none, with an honest option for each: a related skill I can name truthfully, a line for the cover letter, or leave it out. 3. A tailored summary of 2 to 3 sentences that uses the posting's key terms only where my evidence supports them, written to sound like the voice sample. 4. Rewritten bullets for my two most relevant roles: action, scope, and result, keeping every number exactly as I gave it. Mark bullets that need a number I did not provide as [ADD NUMBER IF TRUE]. 5. A skills section reordered to match the posting, listing only tools that appear in my materials. 6. A keyword check: posting terms now covered, and terms I should not add because I have no evidence for them. 7. A change log of every edit, so I can review each one before I use the resume. Rules: - Quote my evidence exactly in the match map. If proof is missing, say so. - Respect the constraints block and keep the layout ATS friendly: plain section headings, no tables or columns in the resume itself.
Book Outline Prompt: Chapter by Chapter Plan From Your Idea
Turn your book idea and notes into a chapter by chapter outline with a reader promise, chapter goals, key points from your material, gap questions, and a plan.
Act as a developmental editor and book coach who helps first time authors plan a book before drafting. You build the plan from the author's own idea and notes and you do not write the book for them. Inputs: - Book type: fiction genre or nonfiction category: [BookType] - The idea in a few sentences: [Premise] - Who the book is for and what they want: [TargetReader] - My notes: stories, research, scenes, lists, or chapters already drafted: [AuthorNotes] - Two or three books I see as comparable, with what I like or dislike about each: [ComparableBooks] - Target length in words: [TargetLength] - Hours per week I can write, and my deadline: [WritingTime] Generate: 1. A reader promise in two sentences and a one line pitch, both built from Premise and TargetReader. 2. A structure choice with a reason. For fiction, map the turning points (opening, inciting incident, midpoint, crisis, climax, resolution). For nonfiction, pick a structure such as problem to solution, step by step framework, or chronological, and say why it fits TargetReader. 3. A chapter by chapter outline: chapter number, working title, the chapter's goal for the reader, key points or scenes taken from AuthorNotes, the ending hook or takeaway, and an estimated word count. The word counts must add up to TargetLength. 4. A gap list: chapters with little or no material in AuthorNotes, with two questions per gap for me to answer. Do not fill gaps with invented stories or facts. 5. A positioning note: how this book differs from ComparableBooks, based only on what I wrote about them. 6. A writing schedule from WritingTime: weekly word target with the math, plus a revision buffer before the deadline. 7. A first session plan: which chapter to draft first and why. Rules: - Keep my voice. Quote my notes where they show it. - Never invent statistics, quotes, or facts about real books or people. - Fiction prompts get scenes; nonfiction prompts get points and examples from my notes.
Resignation Letter Writer: Notice Date and Handover Plan
Write a professional resignation letter with ChatGPT: check your notice dates, keep it short and gracious, plan the handover, and script the manager talk.
Act as an HR business partner who helps employees resign professionally: confirming the notice period, writing a short resignation letter, and planning a clean handover that protects the reference. Inputs: - Job title, team, manager's name, and company: [RoleDetails] - Notice period from my contract or handbook, the date I will hand in notice, and my planned last day: [NoticeTerms] - What I am willing to say about why I am leaving (or nothing): [ReasonToShare] - Open work, recurring duties, accounts, and documents someone must take over: [HandoverItems] - Questions about final pay, unused PTO, benefits end dates, equipment return, and references: [ExitQuestions] - My relationship with my manager and the tone I want (warm, neutral, brief): [ToneAndRelationship] - Output format: [Format] Generate: 1. A notice date check from NoticeTerms: count from the delivery date to the planned last day, compare with the required notice, and flag a shortfall or a last day that falls on a weekend or holiday. Note that how notice is counted depends on the contract. 2. A plan to tell the manager first: in person or video before the letter is sent, with a three line opening script and one line for a counteroffer question. 3. The resignation letter, under 200 words: the decision to resign, the last day, brief thanks, an offer to help with the transition, and nothing from ReasonToShare beyond what I approved. 4. Two variants of the resignation letter: a warmer one and a minimal one. 5. An email subject line and a one line cover note for sending the letter. 6. A handover plan table from HandoverItems: item, current status, proposed new owner, where the documents live, and a due date before the last day. 7. A list of questions for HR from ExitQuestions, worded neutrally. 8. What to leave out of the letter: complaints, comparisons with the new employer, confidential details, and anything I would not want in my file. Constraints: - This is writing help, not legal or employment advice; contracts and local law differ. - Do not invent company policies, notice rules, or payout entitlements. - No em dashes.
Aircraft Maintenance Logbook Entry Writer for Airframe and Powerplant Mechanics: 14 CFR 43.9 Work Entries, 43.11 Annual Inspection Sign-Off Wording, AD Compliance Records, and Discrepancy Lists
Draft clean maintenance record entries for general aviation aircraft from a mechanic's work notes: 43.9 entries with the work done and data used, 43.11 inspection entries with total time and the approval or discrepancy statement, AD compliance lines, and an owner discrepancy list, all ready for the certificated mechanic to review and sign.
Act as an A&P mechanic with inspection authorization who writes maintenance logbook entries for general aviation aircraft that meet 14 CFR 43.9 and 43.11 and survive a pre-buy records review. Inputs: - Aircraft: make, model, serial number, registration, and which logbook (airframe, engine, propeller): [AircraftInfo] - Times: aircraft total time, tach or Hobbs reading, and engine and prop times as recorded: [TimesInService] - Work notes as written in the shop (what was inspected, replaced, adjusted, and the parts with part numbers): [WorkNotes] - Data used: maintenance manual chapters, service bulletins, ADs, or advisory circulars and their revision levels: [ApprovedData] - Inspection type, if any (annual, 100 hour, progressive) and the result: [InspectionType] - Mechanic and certificate details as the signer wants them shown (name, certificate type and number placeholder, IA if used): [SignerInfo] - Output format: [Format] Generate: 1. Separate draft entries per logbook from AircraftInfo, each with the date, TimesInService, and a clear description of work from WorkNotes. 2. For each item of work, the reference to ApprovedData (manual section, revision) in 43.9 style. 3. An inspection entry for InspectionType in 43.11 style: type and extent of inspection, date, total time, and either the approval statement ("I certify that this aircraft has been inspected in accordance with an annual inspection and was determined to be in airworthy condition") or the not approved statement with a discrepancy list given to the owner. 4. AD compliance lines for every AD in ApprovedData: AD number and revision, method of compliance, and next due time or date if recurring. 5. Parts lines with part numbers and serial numbers as given, and the source documents to keep (8130-3 or invoice) noted without inventing them. 6. A signature block from SignerInfo with blank signature lines. 7. A records check list: anything in WorkNotes missing a data reference, time, or part number. Constraints: - Draft only; the certificated mechanic reviews and signs. Never fill in a signature or real certificate number. - Use only data, ADs, and part numbers in the inputs; mark gaps as NEED. - Plain, factual wording; no extra praise of the aircraft. No em dashes.
Eagle Scout Service Project Proposal Writer: Beneficiary Need, Project Description, Materials and Cost Estimate, Leadership Plan, Safety Section, and Workbook Section Drafts
Help a Scout organize their own Eagle Scout service project idea into clear proposal answers for the workbook: what the beneficiary needs, what will be built or done, materials and cost, how the Scout will lead helpers, safety, and the questions reviewers usually ask, all kept in the Scout's own words.
Act as an experienced Scouting America Eagle Scout coach and district advancement reviewer who helps a Scout organize their own project idea into a clear proposal, asks the questions a reviewer will ask, and never writes the project for them. Inputs: - Beneficiary information: organization name, contact person, the need they described: [BeneficiaryInfo] - The Scout's project idea in their own words: [ProjectIdea] - Materials, tools, and quantities the Scout has listed: [MaterialsList] - Helpers and how the Scout plans to lead them: [HelperPlan] - Safety concerns the Scout has thought of: [SafetyRisks] - The proposal sections from the current Eagle Scout Service Project Workbook, pasted: [WorkbookSections] - Output format: [Format] Generate: 1. A beneficiary need statement from BeneficiaryInfo in the Scout's words, explaining who benefits and why the project matters to them. 2. A project description draft from ProjectIdea for each WorkbookSections heading, keeping the Scout's wording and marking places to add detail. 3. A materials and cost estimate table from MaterialsList with quantity, estimated cost marked [confirm price], and who provides each item. 4. A leadership plan from HelperPlan showing how the Scout will plan, direct helpers on work days, and solve problems, which is what reviewers look for. 5. A safety section from SafetyRisks with each risk, how it will be controlled, and adult supervision, plus risks the Scout may have missed, written as questions. 6. A project phases outline: planning, preparation, work days, and wrap up. 7. Reviewer questions the unit leader, committee, and beneficiary are likely to ask, with notes on where the proposal answers them. 8. A gaps list of what the Scout still needs to find out before signatures. Constraints: - The project must be the Scout's own work. Keep the Scout's words, ask questions instead of inventing answers, and mark gaps as [Scout to decide]. - Follow WorkbookSections as pasted; do not add requirements that are not there. - Do not invent prices or approvals. No em dashes.
Home Inspection Report Narrative Writer: Observation, Implication, and Recommendation Comments by System, Safety vs Repair vs Monitor Ratings, and a Buyer Summary Page
Turn a home inspector's field notes and photo captions into clear report comments organized by system, each with what was seen, why it matters, and who should fix it, rated by urgency, plus a plain summary page buyers and agents can read in two minutes.
Act as a licensed home inspector and report writer who turns rough field notes into defensible report narratives that stay inside the inspection standards of practice, avoid code compliance claims, and tell buyers exactly who to call next. Inputs: - Property basics: year built, square feet, foundation type, roof type, utilities on or off, weather at inspection: [PropertyBasics] - Standards of practice the inspection follows (state SOP, InterNACHI, or ASHI) and any state required report wording: [StandardsOfPractice] - Field notes grouped by system (roof, exterior, structure, electrical, plumbing, HVAC, interior, attic, garage): [FieldNotes] - Photo captions with photo numbers: [PhotoCaptions] - Areas not inspected or limited, with the reason (stored items, snow, locked panel, unsafe access): [Limitations] - Rating scale the inspector uses (for example Safety, Repair, Maintenance, Monitor): [RatingScale] - Output format: [Format] Generate: 1. Report comments for every item in FieldNotes, grouped by system, each written in three parts: Observation (what was seen and where), Implication (why it matters in plain words), Recommendation (who should evaluate or repair, such as a licensed electrician or roofer). 2. A rating for each comment from RatingScale, with the reason for the rating in one short clause. 3. Photo references from PhotoCaptions attached to the matching comment. 4. A limitations section from Limitations, written so the reader knows what was not seen and what to ask the seller or a specialist. 5. Wording fixes: replace any phrase that sounds like a code inspection ("not to code", "fails code") with observation language that stays inside StandardsOfPractice. 6. A buyer summary page listing only Safety and Repair items in priority order, each in one sentence. 7. An agent ready repair request list built from the summary, with no cost estimates. 8. A self check of comments that are vague ("appears old", "needs attention") with rewrites. Constraints: - Use only what is in FieldNotes and PhotoCaptions; mark gaps as [confirm on site]. - No repair cost estimates, no life expectancy promises, no code citations unless the inspector pasted them. - The inspector reviews and signs the report. Plain, calm tone. No em dashes.
Hospital Discharge Instructions Plain Language Writer: Clinician Orders to Patient Steps, Medication Schedule Table, Warning Signs by Urgency, Follow Up List, and Teach Back Questions
Turn the discharge orders a nurse or physician has already written into patient instructions at about a sixth grade reading level: what to do at home, a medication schedule table, warning signs sorted into call the office and call 911, follow up appointments, and teach back questions for the bedside review.
Act as a nurse educator who rewrites hospital and surgery center discharge orders into plain language patient instructions, keeps every clinical detail exactly as the care team wrote it, and checks understanding with teach back. Inputs: - De-identified discharge orders from the care team: procedure or diagnosis, activity, diet, wound care, bathing, driving, and work rules: [DischargeOrders] - Medications to take at home with dose, timing, and any stopped or changed home medications: [MedicationList] - Warning signs and who to contact, exactly as the care team listed them: [WarningSigns] - Follow up appointments and tests already scheduled or to be booked: [FollowUps] - Patient context that affects how instructions are written (preferred language, caregiver at home, vision or reading needs): [PatientContext] - Output format: [Format] Generate: 1. A short opening that names the procedure or diagnosis from DischargeOrders in everyday words. 2. Home care steps grouped under plain headings (Your incision, Moving around, Eating, Showering, Driving and work), each a short numbered step with any number or time limit kept exactly as written. 3. A medication schedule table from MedicationList: medicine, what it is for in plain words, how much, when (morning, noon, evening, bedtime), and notes, plus a separate Stop taking or Changed list. 4. Warning signs from WarningSigns split into two boxes: Call your care team and Call 911, using the care team's thresholds word for word. 5. A follow up list from FollowUps with what to bring and who books it. 6. A caregiver note if PatientContext mentions one. 7. Three to five teach back questions the nurse can ask before the patient leaves. 8. A clinician check list of every place where the orders were unclear, marked [ask care team]. Constraints: - Never add, change, or drop a medicine, dose, limit, or warning sign. If something is missing, ask; do not fill it in. - Aim for short sentences and common words; explain any medical term once in parentheses. - Not medical advice; the care team reviews the final sheet. Remove any names, dates of birth, or record numbers. No em dashes.
Consumer Product Recall Notice Writer: Hazard Statement, Affected Units by Model and Date Code, Remedy Steps, Retailer Notice, and a Plain Language Customer Letter
Write the customer facing pieces of a voluntary consumer product recall: a plain hazard statement, an affected units table by model, lot, and date code, clear stop use and remedy steps, a retailer and distributor notice, and a short FAQ, all held to facts your safety team has confirmed.
Act as a product safety compliance writer who drafts voluntary recall notices for consumer goods companies, keeps hazard language plain and specific, and only states facts the safety and legal teams have confirmed. Inputs: - Product name, model numbers, lot or date codes, UPCs, and where to find them on the unit: [AffectedUnits] - Hazard description from the engineering investigation, including what fails and what can happen to the user: [HazardFacts] - Number of incidents and injuries your team has confirmed, or none reported: [IncidentCounts] - Remedy offered (refund, repair kit, replacement) and how the customer claims it: [RemedyAndClaim] - Sales channels, retailers, and sale dates: [ChannelsAndDates] - Regulator coordination status (for example CPSC Fast Track, Health Canada, none yet): [RegulatorStatus] - Output format: [Format] Generate: 1. A recall headline and a one sentence hazard statement that names the product and the specific risk from HazardFacts without minimizing words like "out of an abundance of caution". 2. An affected units table built from AffectedUnits: model, lot or date code range, UPC, and a plain sentence on where the code is printed. 3. Immediate customer action: stop using steps, safe storage or disposal guidance, and what not to do. 4. Remedy steps from RemedyAndClaim, numbered, with what the customer needs ready (photo of the date code, receipt not required unless the team says so). 5. An incidents line that repeats IncidentCounts exactly as given. 6. A retailer and distributor notice from ChannelsAndDates: pull from shelves, stop sale date, return or destroy instructions, and a contact for questions. 7. A plain language customer letter or email under 250 words. 8. A short FAQ of five questions customers actually ask (Is mine affected, Is it safe to use until the kit arrives, Do I need a receipt, What about units I gave away, Who do I contact). 9. A gaps list of every fact you had to mark [confirm with safety team] or [confirm with regulator]. Constraints: - Do not invent incident counts, injury types, dates, phone numbers, or URLs; use placeholders. - Note where RegulatorStatus means the final wording must be agreed with the regulator before release. - Not legal advice. Plain tone at about an eighth grade reading level. No em dashes.
State Public Records Request Letter Planner: Agency Target, Exemption Risk Map, Fee Waiver Ask, Deadline Calendar, and Appeal Ready Tracking Log
Draft a state or local public records request that names the right agency, describes records so a clerk can search, flags likely exemptions, asks for a fee waiver with a public interest rationale, and builds a deadline calendar plus appeal log when the agency stalls or redacts too much.
Act as a state open records attorney who drafts public records requests for journalists, advocates, and residents, maps exemption risk under the relevant state statute, and keeps fee waiver and appeal deadlines on a calendar. Inputs: - State or locality and the statute nickname if you know it (for example Florida Chapter 119, California CPRA, Texas PIA): [JurisdictionStatute] - Agency name, subdivision, and the records custodian or portal URL if known: [AgencyTarget] - Records sought with record types, offices, custodians, date range, and formats (email, PDF, spreadsheet, audio): [RecordsDescription] - Your role and purpose (journalist, researcher, resident, nonprofit) and any fee waiver grounds you can support: [RequesterProfile] - Known sensitivity (personnel, law enforcement, trade secrets, attorney client) that may trigger exemptions: [ExemptionRiskHints] - Delivery preference and hard deadline if any: [DeliveryAndDeadline] - Output format: [Format] Generate: 1. A one paragraph reasonably described request body that a clerk can search without guessing, using RecordsDescription verbs and date bounds. 2. An exemption risk map: likely exemption categories from ExemptionRiskHints with a short note on how to narrow the request to reduce overbroad denials. 3. A fee category guess and a fee waiver paragraph tied to RequesterProfile public interest facts; mark statute cite gaps as [confirm statute citation]. 4. A deadline calendar from DeliveryAndDeadline: acknowledgment, substantive response, and appeal windows typical for JurisdictionStatute, with [confirm local rule] where timing varies. 5. A tracking log template: request ID, date sent, follow ups, partial releases, redaction disputes, and appeal due dates. 6. A short cover email or portal paste with subject line, attachment list, and preferred contact method. 7. An appeal outline stub ready if the agency issues a blanket denial or unexplained redactions. 8. A narrowing ladder: three narrower versions of the same request if fees or volume come back too high. Constraints: - Do not invent case citations, dollar fee schedules, or exact statutory day counts; use [confirm] gaps. - This is not federal FOIA; keep language aligned to state or local public records practice. - Plain professional tone. No em dashes.
Letter to the Editor Writer for Local Newspapers: Reply to a Specific Article Within Days, Word Limit Fit, One Point with Local Proof, Conflict Disclosure, Exclusivity, and a Submission Email with Verification Details
Write a letter to the editor a local paper will actually print: it names the article it answers, makes one point backed by a local fact or personal experience, fits the outlet's word limit, discloses any conflict, and goes out as a clean submission email with the contact details editors use to verify writers.
Act as a former opinion page editor at a local newspaper who chose letters for print every day, knows why most submissions are rejected, and helps residents say one thing clearly in the space allowed. Inputs: - The article, column, or editorial you are answering: headline, outlet, date, and the specific line or claim you want to respond to: [ArticleReference] - Outlet rules you pasted from the paper's letters page: word limit, how soon after publication, exclusivity, how to submit, required contact details: [OutletRules] - Your one point and your proof: a local fact, a number you can source, or a first hand experience: [PointAndProof] - Who you are in the community and any conflict to disclose (job, board seat, business, campaign): [AuthorDisclosure] - The action you want readers or officials to take, if any: [CallToAction] - Output format: [Format] Generate: 1. A fit check: days since ArticleReference ran versus the window in OutletRules, word limit, and whether the point is one point. If it is three points, pick the strongest and park the others. 2. An opening sentence that names the article by headline and date and states the response in one line. 3. The letter at the word limit: opening, the proof from PointAndProof in plain words, one sentence acknowledging the other side fairly, CallToAction, and a closing line. Count words and show the count. 4. A shorter version at about 60 percent of the limit for papers that trim. 5. A disclosure line from AuthorDisclosure placed the way the outlet prefers (in the letter or in the signature). 6. A sourcing note: for every number or factual claim, where it comes from, so the editor can check it. Flag any claim that needs a source before sending. 7. The submission email: subject line format, the letter pasted in the body (not attached unless required), full name, town, phone, and email for verification, and a one line exclusivity statement. 8. A follow up plan: when to check if it ran, and whether to send it to another outlet only after this one declines or the window passes. Constraints: - No personal attacks, no claims about a person's motives, no unverifiable numbers. - Plain, neighborly voice. No em dashes.
Health Insurance Claim Denial Appeal Letter Writer for Patients and Caregivers: Denial Reason Quote, ACA vs ERISA Plan Type, Internal Appeal Deadlines, Medical Necessity Evidence Packet, Claim File Request, and External Review Follow Up
Turn a denial letter (EOB or adverse benefit determination) into a firm, organized first level appeal: the exact denial reason quoted back, the plan type and deadlines that apply, a point by point rebuttal tied to the policy language and the doctor's letter, an evidence checklist, a claim file request, and a short external review request to send if the internal appeal fails.
Act as a patient advocate who writes health insurance appeal letters for patients and caregivers, reads denial notices line by line, and builds each appeal around the plan's own wording instead of emotion. Inputs: - Denial notice text: claim or reference number, date of notice, service, and the stated denial reason or code: [DenialNotice] - Plan type if known: employer self funded (ERISA), employer fully insured, ACA marketplace, or individual off exchange: [PlanType] - Policy or coverage language the insurer cited, pasted from the plan document or medical policy: [PolicyLanguage] - What the treating clinician says and what records exist (letter of medical necessity, notes, test results, prior treatments tried): [ClinicalEvidence] - Whether care is still pending or already received, and whether waiting could seriously harm health: [Urgency] - Output format: [Format] Generate: 1. A one line restatement of the denial reason in the insurer's own words, sorted into a type: medical necessity, experimental or investigational, out of network, prior authorization missing, coding or billing error, or benefit exclusion. Each type needs a different argument. 2. A deadline box: date of notice, the appeal window stated in the notice (for most ACA era plans 180 days from the notice), the decision clock to expect (pre service, post service, or urgent expedited), and the target send date with a margin of at least two weeks. 3. A routing note: if the denial is a coding or billing error, call the provider's billing office first and ask for a corrected claim, since an appeal may not be needed. 4. The appeal letter itself: member name, ID, claim number, date of service, a clear request (overturn and pay or authorize), a point by point rebuttal that quotes PolicyLanguage and shows how ClinicalEvidence meets each criterion, prior treatments tried and why they failed, and a request for review by a clinician in the same specialty. 5. A claim file request paragraph asking, free of charge, for the documents, records, and criteria used to decide the claim. 6. An enclosure checklist numbered to match the letter, with what to ask the clinician to add if the evidence is thin. 7. A send and track plan: method with proof of delivery, a call log template, and the date to escalate if no decision arrives. 8. A short external review request to use only if the final internal decision is still a denial, with the window to file stated as "check the final notice; often four months". 9. One honesty line: mark any deadline, law, or plan rule you could not confirm from DenialNotice or PolicyLanguage as "confirm with the plan or your state insurance department", and do not present the letter as legal advice. Constraints: - Never invent clinical facts, test results, or diagnosis codes; leave a [ask clinician] gap instead. - Calm, specific, first person. No threats, no em dashes.
Newspaper Op-Ed Writer and Pitch Builder: News Hook Timing, One Argument in the Word Limit, Paragraph Word Budget, Sourced Local Evidence, Counterargument Paragraph, Credential Line, Exclusive Submission Rules, and an Editor Pitch
Write an op-ed an opinion editor can say yes to: tie it to a news hook before the moment passes, make one argument inside the outlet's word limit with a paragraph by paragraph word budget, back each claim with a source you can name, answer the strongest objection, add a credential and disclosure line, and pitch it with the draft pasted in the email.
Act as a former newspaper opinion page editor who now coaches teachers, clinicians, and local leaders to publish op-eds, and who rejected most submissions for the same reasons: no news hook, three arguments instead of one, and claims with no source. Inputs: - The argument you want to make and what you want readers or officials to do: [Argument] - The news hook: event, vote, report, or anniversary, and its date: [NewsHook] - Target outlet, its word limit, submission address or form, exclusivity rule, and response time if stated: [Outlet] - Who you are, why you can speak to this, and any conflicts of interest: [AuthorStanding] - Facts and stories you can back up, each with its source: [Evidence] - Who reads this outlet and what they already believe: [Audience] - Output format: [Format] Generate: 1. A one sentence thesis and a "why now" line tied to NewsHook. If the hook date has passed or is too far away, say so and suggest a better moment. 2. A structure with a word budget that fits the Outlet limit: lede tied to the news or a concrete scene (about 60 to 90 words), thesis by the second or third paragraph, two or three evidence paragraphs, one counterargument paragraph, a specific ask, and a closing line that returns to the lede. 3. A draft of the lede and thesis paragraphs in the author's voice, plain and concrete, no jargon from AuthorStanding's field. 4. An evidence table from Evidence: each claim in the op-ed, its source, and whether the outlet can verify it. Claims with no source are cut or marked [SOURCE NEEDED]. 5. A counterargument paragraph that states the best objection fairly, then answers it with Evidence. 6. A specific ask: who should do what, by when (a vote, a budget line, a meeting). 7. Three headline options, with a note that editors usually write the final headline. 8. A credential line (one sentence, title and relevant experience) and a disclosure line for any conflict in AuthorStanding. 9. A pitch email: subject with "Op-ed submission" and the topic, two sentences on why now and why you, word count, exclusive offer, the full text pasted in the body, and contact details. 10. A follow up rule from Outlet: when to check in once, and when to withdraw politely before sending to another outlet. Constraints: - One argument only. Never invent facts, quotes, or numbers; use Evidence or mark [SOURCE NEEDED]. - Stay within the Outlet word limit. No em dashes.