Podcast Producer & AI Audio Production Specialist
Learn professional podcast workflows with 120 detailed, editable prompts across 12 modules. Search by keyword or shortcode, open each prompt, and copy it in one click. Designed for remote-job and client portfolio preparation.
120 of 120 prompts shown
How to use this library
- Choose a module or search a specific task or shortcode.
- Expand a prompt and select Copy full prompt.
- Replace every [BRACKETED FIELD] with genuine project information and verified references.
- Review all AI output against original audio, licensing, guest consent and platform specifications.
- Keep a before/after case study for your portfolio; never fabricate client results or metrics.
Example workflow: POD-011 (episode brief) → POD-019 (run of show) → POD-041 (recording setup) → POD-051 (edit decision list) → POD-061 (transcript) → POD-081 (clip selection) → POD-100 (publishing QA) → POD-118 (portfolio case study).
Module 01: Podcast Strategy & Audience
Define a podcast positioning statement
Use this when you need to define a podcast positioning statement for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: define a podcast positioning statement. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: define a podcast positioning statement. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Define a podcast positioning statement — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Develop a specific listener persona
Use this when you need to develop a specific listener persona for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: develop a specific listener persona. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: develop a specific listener persona. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Develop a specific listener persona — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Audit competing podcasts ethically
Use this when you need to audit competing podcasts ethically for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: audit competing podcasts ethically. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: audit competing podcasts ethically. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Audit competing podcasts ethically — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Select a defensible show niche
Use this when you need to select a defensible show niche for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: select a defensible show niche. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: select a defensible show niche. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Select a defensible show niche — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a show concept and promise
Use this when you need to write a show concept and promise for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a show concept and promise. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a show concept and promise. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a show concept and promise — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create three editorial content pillars
Use this when you need to create three editorial content pillars for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create three editorial content pillars. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create three editorial content pillars. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create three editorial content pillars — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a season-level content roadmap
Use this when you need to build a season-level content roadmap for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a season-level content roadmap. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a season-level content roadmap. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a season-level content roadmap — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Choose a sustainable episode format
Use this when you need to choose a sustainable episode format for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: choose a sustainable episode format. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: choose a sustainable episode format. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Choose a sustainable episode format — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan an accessible and inclusive show
Use this when you need to plan an accessible and inclusive show for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan an accessible and inclusive show. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan an accessible and inclusive show. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan an accessible and inclusive show — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Set measurable podcast goals
Use this when you need to set measurable podcast goals for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: set measurable podcast goals. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (show concept, target listener, genre, format, business goal): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: set measurable podcast goals. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for audience fit, differentiation and sustainability. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Set measurable podcast goals — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 02: Episode Research & Planning
Build a source-verified episode brief
Use this when you need to build a source-verified episode brief for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a source-verified episode brief. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a source-verified episode brief. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a source-verified episode brief — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Find compelling episode angles
Use this when you need to find compelling episode angles for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: find compelling episode angles. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: find compelling episode angles. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Find compelling episode angles — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design a balanced research question set
Use this when you need to design a balanced research question set for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design a balanced research question set. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design a balanced research question set. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design a balanced research question set — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a preproduction checklist
Use this when you need to create a preproduction checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a preproduction checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a preproduction checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a preproduction checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Outline a solo educational episode
Use this when you need to outline a solo educational episode for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: outline a solo educational episode. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: outline a solo educational episode. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Outline a solo educational episode — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan a narrative documentary episode
Use this when you need to plan a narrative documentary episode for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan a narrative documentary episode. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan a narrative documentary episode. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan a narrative documentary episode — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan a multi-guest roundtable
Use this when you need to plan a multi-guest roundtable for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan a multi-guest roundtable. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan a multi-guest roundtable. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan a multi-guest roundtable — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Develop a fact-checking worksheet
Use this when you need to develop a fact-checking worksheet for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: develop a fact-checking worksheet. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: develop a fact-checking worksheet. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Develop a fact-checking worksheet — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create an episode run of show
Use this when you need to create an episode run of show for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create an episode run of show. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create an episode run of show. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create an episode run of show — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design a backup plan for missing guests
Use this when you need to design a backup plan for missing guests for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design a backup plan for missing guests. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode topic, listener knowledge, research notes, source URLs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design a backup plan for missing guests. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for source accuracy, balanced framing and feasible production. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design a backup plan for missing guests — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 03: Scripts & Storytelling
Write a strong cold open
Use this when you need to write a strong cold open for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a strong cold open. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a strong cold open. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a strong cold open — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft a conversational host introduction
Use this when you need to draft a conversational host introduction for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft a conversational host introduction. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft a conversational host introduction. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft a conversational host introduction — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a story arc with meaningful stakes
Use this when you need to build a story arc with meaningful stakes for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a story arc with meaningful stakes. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a story arc with meaningful stakes. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a story arc with meaningful stakes — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a smooth segment transition
Use this when you need to write a smooth segment transition for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a smooth segment transition. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a smooth segment transition. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a smooth segment transition — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft an evidence-led explainer segment
Use this when you need to draft an evidence-led explainer segment for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft an evidence-led explainer segment. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft an evidence-led explainer segment. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft an evidence-led explainer segment — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Turn technical concepts into plain language
Use this when you need to turn technical concepts into plain language for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: turn technical concepts into plain language. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: turn technical concepts into plain language. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Turn technical concepts into plain language — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a non-manipulative call to action
Use this when you need to write a non-manipulative call to action for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a non-manipulative call to action. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a non-manipulative call to action. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a non-manipulative call to action — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a respectful content advisory
Use this when you need to create a respectful content advisory for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a respectful content advisory. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a respectful content advisory. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a respectful content advisory — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft an accurate episode recap
Use this when you need to draft an accurate episode recap for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft an accurate episode recap. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft an accurate episode recap. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft an accurate episode recap — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Edit a script for natural spoken rhythm
Use this when you need to edit a script for natural spoken rhythm for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: edit a script for natural spoken rhythm. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode objective, host voice, outline, verified facts): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: edit a script for natural spoken rhythm. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for spoken clarity, narrative flow and factual fidelity. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Edit a script for natural spoken rhythm — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 04: Guests & Interviews
Research a guest using supplied sources
Use this when you need to research a guest using supplied sources for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: research a guest using supplied sources. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: research a guest using supplied sources. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Research a guest using supplied sources — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a personalized guest invitation
Use this when you need to write a personalized guest invitation for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a personalized guest invitation. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a personalized guest invitation. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a personalized guest invitation — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create an interview preparation dossier
Use this when you need to create an interview preparation dossier for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create an interview preparation dossier. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create an interview preparation dossier. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create an interview preparation dossier — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft open-ended interview questions
Use this when you need to draft open-ended interview questions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft open-ended interview questions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft open-ended interview questions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft open-ended interview questions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Develop thoughtful follow-up questions
Use this when you need to develop thoughtful follow-up questions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: develop thoughtful follow-up questions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: develop thoughtful follow-up questions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Develop thoughtful follow-up questions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan a sensitive-topic interview
Use this when you need to plan a sensitive-topic interview for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan a sensitive-topic interview. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan a sensitive-topic interview. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan a sensitive-topic interview — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Prepare a guest briefing email
Use this when you need to prepare a guest briefing email for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare a guest briefing email. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare a guest briefing email. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare a guest briefing email — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a time-boxed interview agenda
Use this when you need to create a time-boxed interview agenda for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a time-boxed interview agenda. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a time-boxed interview agenda. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a time-boxed interview agenda — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft a post-interview thank-you note
Use this when you need to draft a post-interview thank-you note for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft a post-interview thank-you note. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft a post-interview thank-you note. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft a post-interview thank-you note — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Review interview balance and fairness
Use this when you need to review interview balance and fairness for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: review interview balance and fairness. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (guest background, interview objective, time limit, approved sources): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: review interview balance and fairness. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for respectful guest treatment, consent and open-ended questioning. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Review interview balance and fairness — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 05: Recording & Production
Select an appropriate home recording setup
Use this when you need to select an appropriate home recording setup for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: select an appropriate home recording setup. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: select an appropriate home recording setup. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Select an appropriate home recording setup — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a remote recording checklist
Use this when you need to create a remote recording checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a remote recording checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a remote recording checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a remote recording checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a microphone placement guide
Use this when you need to build a microphone placement guide for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a microphone placement guide. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a microphone placement guide. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a microphone placement guide — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan gain staging and headroom
Use this when you need to plan gain staging and headroom for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan gain staging and headroom. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan gain staging and headroom. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan gain staging and headroom — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Troubleshoot echo and room reflections
Use this when you need to troubleshoot echo and room reflections for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: troubleshoot echo and room reflections. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: troubleshoot echo and room reflections. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Troubleshoot echo and room reflections — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Reduce plosives at the source
Use this when you need to reduce plosives at the source for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: reduce plosives at the source. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: reduce plosives at the source. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Reduce plosives at the source — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Coordinate separate guest audio tracks
Use this when you need to coordinate separate guest audio tracks for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: coordinate separate guest audio tracks. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: coordinate separate guest audio tracks. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Coordinate separate guest audio tracks — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a recording consent checklist
Use this when you need to create a recording consent checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a recording consent checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a recording consent checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a recording consent checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design a file naming convention
Use this when you need to design a file naming convention for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design a file naming convention. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design a file naming convention. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design a file naming convention — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Prepare a session recovery protocol
Use this when you need to prepare a session recovery protocol for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare a session recovery protocol. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (room and equipment, remote/in-person setup, budget, risks): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare a session recovery protocol. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for recording safety, redundancy and usable sound. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare a session recovery protocol — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 06: Audio Editing & Mixing
Create an episode editing decision list
Use this when you need to create an episode editing decision list for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create an episode editing decision list. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create an episode editing decision list. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create an episode editing decision list — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Remove filler without changing meaning
Use this when you need to remove filler without changing meaning for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: remove filler without changing meaning. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: remove filler without changing meaning. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Remove filler without changing meaning — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan dialogue cleanup and noise reduction
Use this when you need to plan dialogue cleanup and noise reduction for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan dialogue cleanup and noise reduction. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan dialogue cleanup and noise reduction. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan dialogue cleanup and noise reduction — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Set a consistent dialogue level
Use this when you need to set a consistent dialogue level for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: set a consistent dialogue level. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: set a consistent dialogue level. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Set a consistent dialogue level — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design an EQ review for speech clarity
Use this when you need to design an eq review for speech clarity for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design an eq review for speech clarity. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design an eq review for speech clarity. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design an EQ review for speech clarity — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan transparent compression settings
Use this when you need to plan transparent compression settings for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan transparent compression settings. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan transparent compression settings. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan transparent compression settings — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Check cuts for pacing and continuity
Use this when you need to check cuts for pacing and continuity for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: check cuts for pacing and continuity. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: check cuts for pacing and continuity. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Check cuts for pacing and continuity — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create an intro and outro mix plan
Use this when you need to create an intro and outro mix plan for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create an intro and outro mix plan. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create an intro and outro mix plan. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create an intro and outro mix plan — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Review loudness and true peak targets
Use this when you need to review loudness and true peak targets for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: review loudness and true peak targets. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: review loudness and true peak targets. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Review loudness and true peak targets — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Perform a final headphone and speaker QA
Use this when you need to perform a final headphone and speaker qa for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: perform a final headphone and speaker qa. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (raw recording characteristics, editing software, delivery specification): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: perform a final headphone and speaker qa. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for intelligibility, consistent levels, naturalness and reversibility. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Perform a final headphone and speaker QA — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 07: AI Transcription & Accessibility
Create a verbatim transcript workflow
Use this when you need to create a verbatim transcript workflow for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a verbatim transcript workflow. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a verbatim transcript workflow. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a verbatim transcript workflow — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Correct names and technical terms
Use this when you need to correct names and technical terms for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: correct names and technical terms. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: correct names and technical terms. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Correct names and technical terms — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Add meaningful speaker labels
Use this when you need to add meaningful speaker labels for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: add meaningful speaker labels. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: add meaningful speaker labels. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Add meaningful speaker labels — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create accurate timestamped chapters
Use this when you need to create accurate timestamped chapters for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create accurate timestamped chapters. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create accurate timestamped chapters. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create accurate timestamped chapters — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Produce an accessible transcript page
Use this when you need to produce an accessible transcript page for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: produce an accessible transcript page. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: produce an accessible transcript page. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Produce an accessible transcript page — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Identify transcription uncertainty
Use this when you need to identify transcription uncertainty for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: identify transcription uncertainty. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: identify transcription uncertainty. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Identify transcription uncertainty — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Prepare human-reviewed captions
Use this when you need to prepare human-reviewed captions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare human-reviewed captions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare human-reviewed captions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare human-reviewed captions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write meaningful descriptions of audio cues
Use this when you need to write meaningful descriptions of audio cues for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write meaningful descriptions of audio cues. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write meaningful descriptions of audio cues. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write meaningful descriptions of audio cues — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Translate captions with a review workflow
Use this when you need to translate captions with a review workflow for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: translate captions with a review workflow. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: translate captions with a review workflow. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Translate captions with a review workflow — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a privacy-safe transcript redaction plan
Use this when you need to create a privacy-safe transcript redaction plan for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a privacy-safe transcript redaction plan. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (audio or transcript sample, language, speaker names, accessibility requirements): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a privacy-safe transcript redaction plan. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for fidelity to spoken content, inclusion and privacy. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a privacy-safe transcript redaction plan — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 08: Show Notes & Podcast SEO
Write a direct-answer episode summary
Use this when you need to write a direct-answer episode summary for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a direct-answer episode summary. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a direct-answer episode summary. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a direct-answer episode summary — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create searchable episode titles
Use this when you need to create searchable episode titles for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create searchable episode titles. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create searchable episode titles. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create searchable episode titles — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft useful and non-clickbait show notes
Use this when you need to draft useful and non-clickbait show notes for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft useful and non-clickbait show notes. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft useful and non-clickbait show notes. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft useful and non-clickbait show notes — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Extract verified key takeaways
Use this when you need to extract verified key takeaways for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: extract verified key takeaways. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: extract verified key takeaways. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Extract verified key takeaways — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Generate chapter descriptions
Use this when you need to generate chapter descriptions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: generate chapter descriptions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: generate chapter descriptions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Generate chapter descriptions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a linked source bibliography
Use this when you need to build a linked source bibliography for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a linked source bibliography. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a linked source bibliography. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a linked source bibliography — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create search-intent-aligned FAQs
Use this when you need to create search-intent-aligned faqs for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create search-intent-aligned faqs. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create search-intent-aligned faqs. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create search-intent-aligned FAQs — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft accessible episode metadata
Use this when you need to draft accessible episode metadata for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft accessible episode metadata. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft accessible episode metadata. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft accessible episode metadata — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan internal links across episodes
Use this when you need to plan internal links across episodes for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan internal links across episodes. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan internal links across episodes. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan internal links across episodes — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Audit show notes for unsupported claims
Use this when you need to audit show notes for unsupported claims for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: audit show notes for unsupported claims. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (episode notes, target search intent, source links, audience): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: audit show notes for unsupported claims. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for discoverability without fabricated claims or keyword stuffing. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Audit show notes for unsupported claims — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 09: Clips & Social Promotion
Select meaningful short-form highlights
Use this when you need to select meaningful short-form highlights for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: select meaningful short-form highlights. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: select meaningful short-form highlights. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Select meaningful short-form highlights — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a vertical clip storyboard
Use this when you need to create a vertical clip storyboard for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a vertical clip storyboard. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a vertical clip storyboard. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a vertical clip storyboard — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft three platform-specific captions
Use this when you need to draft three platform-specific captions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft three platform-specific captions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft three platform-specific captions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft three platform-specific captions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write accurate quote cards
Use this when you need to write accurate quote cards for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write accurate quote cards. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write accurate quote cards. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write accurate quote cards — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a teaser trailer outline
Use this when you need to create a teaser trailer outline for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a teaser trailer outline. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a teaser trailer outline. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a teaser trailer outline — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan an episode launch content calendar
Use this when you need to plan an episode launch content calendar for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan an episode launch content calendar. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan an episode launch content calendar. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan an episode launch content calendar — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design an audiogram creative brief
Use this when you need to design an audiogram creative brief for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design an audiogram creative brief. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design an audiogram creative brief. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design an audiogram creative brief — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write an email launch announcement
Use this when you need to write an email launch announcement for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write an email launch announcement. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write an email launch announcement. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write an email launch announcement — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Repurpose a segment into a newsletter
Use this when you need to repurpose a segment into a newsletter for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: repurpose a segment into a newsletter. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: repurpose a segment into a newsletter. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Repurpose a segment into a newsletter — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Check clips for misleading context
Use this when you need to check clips for misleading context for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: check clips for misleading context. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (approved episode excerpts, target platform, desired audience action): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: check clips for misleading context. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for context preservation, brand consistency and platform fit. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Check clips for misleading context — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 10: Publishing & Distribution
Prepare RSS feed metadata checklist
Use this when you need to prepare rss feed metadata checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare rss feed metadata checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare rss feed metadata checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare RSS feed metadata checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a podcast publishing SOP
Use this when you need to create a podcast publishing sop for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a podcast publishing sop. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a podcast publishing sop. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a podcast publishing SOP — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan episode release scheduling
Use this when you need to plan episode release scheduling for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan episode release scheduling. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan episode release scheduling. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan episode release scheduling — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design an asset upload checklist
Use this when you need to design an asset upload checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design an asset upload checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design an asset upload checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design an asset upload checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Prepare episode artwork specifications
Use this when you need to prepare episode artwork specifications for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare episode artwork specifications. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare episode artwork specifications. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare episode artwork specifications — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a distribution channel matrix
Use this when you need to write a distribution channel matrix for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a distribution channel matrix. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a distribution channel matrix. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a distribution channel matrix — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a change log for episode updates
Use this when you need to create a change log for episode updates for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a change log for episode updates. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a change log for episode updates. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a change log for episode updates — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft an episode correction policy
Use this when you need to draft an episode correction policy for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft an episode correction policy. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft an episode correction policy. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft an episode correction policy — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan backup and archival procedures
Use this when you need to plan backup and archival procedures for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan backup and archival procedures. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan backup and archival procedures. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan backup and archival procedures — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a preflight publication QA checklist
Use this when you need to build a preflight publication qa checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a preflight publication qa checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (hosting platform, publishing schedule, artwork and audio specs): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a preflight publication qa checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metadata completeness, correct files and rollback readiness. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a preflight publication QA checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 11: Analytics & Sustainable Growth
Define a responsible KPI dashboard
Use this when you need to define a responsible kpi dashboard for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: define a responsible kpi dashboard. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: define a responsible kpi dashboard. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Define a responsible KPI dashboard — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Interpret episode retention patterns
Use this when you need to interpret episode retention patterns for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: interpret episode retention patterns. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: interpret episode retention patterns. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Interpret episode retention patterns — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Compare episode themes fairly
Use this when you need to compare episode themes fairly for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: compare episode themes fairly. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: compare episode themes fairly. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Compare episode themes fairly — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design a listener feedback survey
Use this when you need to design a listener feedback survey for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design a listener feedback survey. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design a listener feedback survey. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design a listener feedback survey — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a qualitative review coding rubric
Use this when you need to create a qualitative review coding rubric for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a qualitative review coding rubric. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a qualitative review coding rubric. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a qualitative review coding rubric — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Plan an ethical growth experiment
Use this when you need to plan an ethical growth experiment for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: plan an ethical growth experiment. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: plan an ethical growth experiment. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Plan an ethical growth experiment — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Evaluate promotional channel performance
Use this when you need to evaluate promotional channel performance for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: evaluate promotional channel performance. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: evaluate promotional channel performance. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Evaluate promotional channel performance — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Write a monthly performance report
Use this when you need to write a monthly performance report for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a monthly performance report. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a monthly performance report. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a monthly performance report — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Identify content gaps from audience questions
Use this when you need to identify content gaps from audience questions for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: identify content gaps from audience questions. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: identify content gaps from audience questions. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Identify content gaps from audience questions — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a data-informed next-season plan
Use this when you need to build a data-informed next-season plan for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a data-informed next-season plan. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (available performance metrics, reporting period, audience goals): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a data-informed next-season plan. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for metric definitions, caveats and decisions supported by evidence. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a data-informed next-season plan — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Module 12: Client Delivery & Remote Portfolio
Write a podcast client discovery questionnaire
Use this when you need to write a podcast client discovery questionnaire for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: write a podcast client discovery questionnaire. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: write a podcast client discovery questionnaire. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Write a podcast client discovery questionnaire — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Define a production scope of work
Use this when you need to define a production scope of work for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: define a production scope of work. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: define a production scope of work. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Define a production scope of work — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Estimate an episode production timeline
Use this when you need to estimate an episode production timeline for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: estimate an episode production timeline. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: estimate an episode production timeline. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Estimate an episode production timeline — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a revision and approval workflow
Use this when you need to build a revision and approval workflow for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a revision and approval workflow. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a revision and approval workflow. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a revision and approval workflow — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a deliverables handoff checklist
Use this when you need to create a deliverables handoff checklist for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a deliverables handoff checklist. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a deliverables handoff checklist. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a deliverables handoff checklist — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Draft a professional project status update
Use this when you need to draft a professional project status update for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: draft a professional project status update. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: draft a professional project status update. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Draft a professional project status update — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Build a rights and licensing review
Use this when you need to build a rights and licensing review for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: build a rights and licensing review. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: build a rights and licensing review. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Build a rights and licensing review — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Create a sample podcast portfolio case study
Use this when you need to create a sample podcast portfolio case study for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: create a sample podcast portfolio case study. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: create a sample podcast portfolio case study. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Create a sample podcast portfolio case study — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Design a remote producer skills assessment
Use this when you need to design a remote producer skills assessment for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: design a remote producer skills assessment. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: design a remote producer skills assessment. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Design a remote producer skills assessment — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Prepare a client-facing quality assurance report
Use this when you need to prepare a client-facing quality assurance report for a real podcast project. Replace all bracketed fields before copying.
View full prompt & input template
You are a professional podcast producer and AI audio production specialist. Your task: prepare a client-facing quality assurance report. PROJECT INPUTS - Show or client: [SHOW / CLIENT] - Relevant context (client brief, budget, approval process, delivery dates): [PASTE CONTEXT] - Intended listener and language: [AUDIENCE / LANGUAGE] - Format, duration and platform: [FORMAT / DURATION / PLATFORM] - Constraints, tools, budget and deadline: [CONSTRAINTS] - Approved facts, assets and references: [PASTE VERIFIED INFORMATION OR WRITE NONE] INSTRUCTIONS 1. Restate the objective and distinguish supplied facts from assumptions. Ask up to three critical questions only if essential; otherwise state reasonable assumptions explicitly. 2. Produce a specific, actionable deliverable focused on: prepare a client-facing quality assurance report. Avoid generic podcast advice. 3. Include a concrete workflow, an example adapted to the provided inputs, and a compact checklist for clear scope, permissions, QA and client sign-off. 4. Flag dependencies, production tradeoffs and any items requiring listening, human review, consent or source verification. Never claim to have listened to audio or checked a live source unless actually provided and analyzed. 5. For quotations, attribution, guest statements and statistics, rely only on verified input. Do not invent guests, downloads, ratings, links or transcripts. OUTPUT FORMAT A. Objective and assumptions B. Prepare a client-facing quality assurance report — finished deliverable C. Step-by-step implementation or example D. Review checklist and acceptance criteria E. Open questions and next actions.
Portfolio exercise: Produce a sample podcast episode
Choose a public-domain or original topic and create a 7–12 minute sample episode. Deliver the episode brief, verified source sheet, run of show, original recording, human-reviewed transcript, accessible show notes, two context-preserving social clips, production log and final QA checklist. Explain your role, tools and revision decisions, and label the work as a practice project.
Frequently asked questions
Are these WordPress shortcodes?
No. POD-001 to POD-120 are unique prompt reference IDs for finding and sharing a template, not executable WordPress shortcodes.
Can I use the prompts with different AI tools?
Yes. Paste a prompt into a suitable assistant and replace the placeholders. Audio-related tasks still require actual audio-capable software or uploaded material.
Can AI publish or verify my episode automatically?
No. Verify audio, source attribution, guest consent, rights, export settings and platform requirements before publishing.
How does the search work?
It filters all 120 cards instantly by keyword, shortcode, title and prompt body; the module dropdown narrows the results further.
