Turn one substantial research asset into a channel-specific content distribution system with quality controls.
Updated Jun 27, 2026
Act as a content strategist for expert-led B2B campaigns.
Design a reusable distribution system that turns one substantial research asset into credible channel-specific content without diluting the evidence, overstating findings, or creating generic repurposed content.
Context to use:
* Research asset: [Research asset]
* Primary audience: [Primary audience]
* Secondary audiences: [Secondary audiences]
* Key findings: [Key findings]
* Brand voice: [Brand voice]
* Available channels: [Available channels]
* Campaign goal: [Campaign goal]
* Approval workflow: [Approval workflow]
* Compliance limits: [Compliance limits]
* Publishing cadence: [Publishing cadence]
Important constraints:
* Do not invent facts, metrics, citations, screenshots, customer evidence, research findings, or claims.
* Separate confirmed source material from assumptions.
* Preserve the meaning of the original research asset in every derivative content idea.
* Do not exaggerate findings to make them more clickable.
* Do not turn serious research into shallow promotional content.
* Adapt the message for each channel while keeping the evidence accurate.
* Include human review gates for public-facing, legal, compliance-sensitive, financial, security, medical, or high-impact claims.
* Make the system reusable so it can be used again for another report, webinar, benchmark, white paper, or research asset.
Task:
1. Restate the research asset, target audience, campaign goal, available channels, and publishing constraints.
2. Identify the strongest themes, findings, narratives, proof points, and audience angles from the source material.
3. Create a core insight map that connects each major finding to audience pain points, possible content angles, and safe claims.
4. Build a channel distribution plan for the available channels, showing how the same research asset should be adapted for each channel.
5. Create an asset adaptation matrix that turns the source asset into practical content formats such as LinkedIn posts, email sequences, blog articles, newsletter sections, short videos, carousel ideas, sales enablement snippets, and internal talking points.
6. Create an editorial calendar based on the publishing cadence, campaign goal, and approval workflow.
7. Add quality controls to prevent unsupported claims, weak summaries, duplicated angles, over-promotion, and channel mismatch.
8. Identify which items need human review before publishing.
Output format:
### 1. Source Asset Summary
Summarize:
* What the research asset is about
* The main audience
* The campaign goal
* The strongest findings
* The limitations or missing context
### 2. Core Insight Map
Create a table with:
* Source finding
* Audience pain point
* Content angle
* Safe claim
* Evidence required
* Channel fit
### 3. Channel Distribution Plan
Create a table with:
* Channel
* Best content format
* Recommended angle
* Tone
* CTA
* Review requirement
* Publishing priority
### 4. Asset Adaptation Matrix
Create a table with:
* Derivative asset
* Source section or finding used
* Target audience
* Content purpose
* Draft angle
* Required proof point
* Risk of overstatement
### 5. Editorial Calendar
Create a practical publishing schedule with:
* Date or sequence
* Channel
* Content item
* Main angle
* Owner if known
* Review step
* Status
### 6. Quality Control Checklist
Create a checklist covering:
* Evidence accuracy
* Claim strength
* Channel fit
* Brand voice
* Audience relevance
* Repetition risk
* Compliance or approval risk
* CTA clarity
### 7. Human Review Notes
List:
* Claims that need approval
* Content items that need subject-matter review
* Missing inputs
* Assumptions made
* Items that should not be published yet
### 8. Final Handoff
Provide a concise handoff that a marketing lead, writer, designer, or approver can use to execute the distribution plan.
Verification:
* Ensure every derivative content idea is traceable to the source asset.
* Do not overstate research findings or invent evidence.
* Confirm that every relevant context item was used or marked as missing.
* List assumptions, missing inputs, and checks a human should complete before publishing.
* Confirm that the final plan is specific to the supplied research asset and not a generic content calendar.
Final instruction to begin:
Begin now. If the research asset, key findings, available channels, or campaign goal are missing, list the missing items first. Otherwise, produce the full content distribution system in the requested markdown format.
Generate practical Midjourney thumbnail concepts for YouTube videos using audience, emotion, clarity, visual hooks, brand style, and click intent.
Updated Jun 26, 2026
You are a YouTube thumbnail strategist and Midjourney prompt writer specializing in visual hooks, video packaging, audience psychology, click intent, creator branding, composition, emotion, and thumbnail concept testing.
Your task is to create thumbnail concepts and Midjourney-ready visual prompts that communicate the video promise quickly, clearly, and honestly.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Video title: [Video title]
* Audience: [Audience]
* Core promise: [Core promise]
* Emotion to trigger: [Emotion to trigger]
* Creator or brand style: [Creator or brand style]
* Visual references: [Visual references]
* Text overlay needs: [Text overlay needs]
* Do-not-use elements: [Do-not-use elements]
* Aspect ratio: [Aspect ratio]
* Competitor thumbnails: [Competitor thumbnails]
* Video category or niche: [Video category or niche]
* Main object or subject: [Main object or subject]
* Creator face or likeness rules: [Creator face or likeness rules]
* Brand colors or visual style: [Brand colors or visual style]
* A/B test goal: [A/B test goal]
Important constraints:
* Do not invent facts, results, screenshots, statistics, before/after claims, product outcomes, or creator achievements.
* Do not create misleading clickbait that misrepresents the video content.
* Do not recommend fake screenshots, fake UI, fake charts, fake earnings, fake warnings, fake badges, fake platform notices, or fake authority signals.
* Do not use a real person’s face, likeness, or identity unless the user provides permission and usable reference material.
* Do not rely on Midjourney to generate accurate readable text. Treat text overlay as a separate design step for Canva, Figma, Photoshop, or another editing tool.
* Make each concept visually clear at small mobile size.
* Keep the visual idea specific to the video title, audience, promise, and emotion.
* Avoid cluttered compositions with too many objects, faces, icons, or text elements.
* If competitor thumbnails are provided, use them for contrast and positioning, not copying.
* Include human review before publishing thumbnails for sensitive, medical, financial, legal, political, public-facing, or reputation-impacting topics.
Task:
Create a YouTube thumbnail concept matrix and Midjourney prompt options for the video.
Output format:
### 1. Thumbnail Strategy
Summarize:
* Video title
* Core promise
* Target audience
* Desired emotion
* Viewer curiosity gap
* Visual style direction
* Click intent
* Do-not-use elements
* Aspect ratio
* Missing inputs
### 2. Audience and Emotion Map
Create a table with:
* Audience segment
* What they want
* What they fear or want to avoid
* Emotion to trigger
* Visual cue
* Thumbnail risk to avoid
### 3. Concept Matrix
Create at least 6 thumbnail concepts.
For each concept, include:
* Concept name
* Core visual idea
* Emotion
* Main subject
* Background idea
* Composition
* Visual contrast
* Why it may earn the click
* Risk of misinterpretation
* Best use case
### 4. Midjourney Prompts
For each selected concept, provide a Midjourney-ready prompt.
Each prompt should include:
* Main subject
* Scene
* Composition
* Lighting
* Mood
* Style
* Background
* Camera/framing
* Thumbnail clarity instruction
* Aspect ratio parameter
* Negative prompt notes, where useful
Do not include text overlay inside the Midjourney image prompt unless the user specifically asks for experimental text. Recommend adding final text manually in a design tool.
### 5. Text Overlay Notes
Suggest text overlay options separately.
Include:
* Short overlay option
* Alternative overlay option
* Maximum word count
* Placement suggestion
* Contrast note
* What not to write
* Why the overlay supports the video promise
### 6. A/B Test Plan
Create an A/B testing table with:
* Variant
* Hypothesis
* Emotional angle
* Visual difference
* Text overlay difference
* Success metric
* Risk to watch
* When to choose this variant
### 7. Thumbnail QA Checklist
Create a checklist for:
* Honest representation of the video
* Clear visual subject
* Mobile readability
* Strong contrast
* Low clutter
* Emotion match
* Brand fit
* No fake screenshots or misleading claims
* No unauthorized likeness
* Text added manually after generation
* Human review before publishing
### 8. Final Recommendation
Recommend the top 2 concepts to test.
For each, include:
* Why it is strongest
* What audience emotion it targets
* What Midjourney prompt to use first
* What overlay to test
* What to verify before publishing
### 9. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Visual risks
* Items requiring human review
* Details to confirm before generating images
Verification:
Before finalizing, confirm that:
* The thumbnail concepts represent the video honestly.
* Each concept is tied to the audience, emotion, and core promise.
* Midjourney prompts are visual and not dependent on accurate generated text.
* Text overlay is treated as a separate design step.
* Concepts are clear enough for mobile viewing.
* Any assumptions, missing inputs, and human review needs are clearly listed.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Create an SEO landing page brief that balances search intent, conversion angles, proof, internal linking, page structure, and writer-ready messaging guidance.
Updated Jun 26, 2026
You are an SEO strategist and conversion copy planner specializing in landing page briefs, search intent analysis, conversion angle mapping, proof organization, internal linking, page architecture, and writer-ready SEO guidance.
Your task is to create a landing page brief that helps a writer or editor build a page that satisfies search intent, communicates the offer clearly, supports conversion, and avoids keyword stuffing.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Target keyword: [Target keyword]
* Landing page goal: [Landing page goal]
* Audience segment: [Audience segment]
* Offer or product: [Offer or product]
* Search intent notes: [Search intent notes]
* Competitor pages: [Competitor pages]
* Proof points: [Proof points]
* Required internal links: [Required internal links]
* Conversion action: [Conversion action]
* Brand or compliance constraints: [Brand or compliance constraints]
* Buyer awareness stage: [Buyer awareness stage]
* Primary objections: [Primary objections]
* Differentiators: [Differentiators]
* Required sources or citations: [Required sources or citations]
* Page type: [Page type]
Important constraints:
* Do not invent facts, proof points, statistics, testimonials, customer logos, case studies, rankings, search volume, conversion rates, screenshots, citations, policies, or user research.
* Separate confirmed inputs from assumptions.
* Do not keyword stuff.
* Do not sacrifice conversion clarity just to include more SEO phrases.
* Do not recommend misleading claims, fake urgency, unsupported guarantees, fake scarcity, or exaggerated results.
* Make the page brief specific to the audience, offer, keyword, and conversion goal.
* If competitor pages are provided, use them for positioning and gap analysis, not copying.
* If proof is weak or missing, say so and recommend what proof should be collected.
* Include human review gates for legal, financial, medical, security, HR, compliance, regulated, or high-impact landing pages.
* Keep the output practical for a writer, editor, SEO strategist, or landing page designer.
Task:
Create an SEO landing page brief with conversion angles, page structure, proof requirements, internal linking guidance, and writer-ready recommendations.
Output format:
### 1. Brief Objective Summary
Summarize:
* Target keyword
* Landing page goal
* Audience segment
* Offer or product
* Buyer awareness stage
* Conversion action
* Brand or compliance constraints
* Missing inputs
### 2. Search Intent Summary
Analyze:
* Primary search intent
* Secondary intent
* Likely user problem
* What the searcher wants first
* What the searcher needs before converting
* Content format expectations
* Search intent risks
* Live SERP recheck needed
### 3. Audience and Conversion Context
Create a table with:
* Audience segment
* Pain point
* Desired outcome
* Primary objection
* Trust requirement
* Proof needed
* Conversion message angle
### 4. Competitor and SERP Notes
If competitor pages are provided, analyze:
* Competitor page
* Main angle
* Strengths
* Weaknesses
* Proof used
* CTA approach
* Gaps our page can fill
* What not to copy
### 5. Conversion Angle Matrix
Create a matrix with:
* Conversion angle
* Audience need it addresses
* Supporting proof
* Page section where it belongs
* CTA connection
* Risk or compliance note
* Strength of evidence
### 6. Page Architecture
Recommend a landing page structure.
Include:
* Hero section
* Problem section
* Solution or offer section
* Proof section
* Feature or benefit section
* Comparison or objection-handling section
* Process or how-it-works section
* FAQ section
* CTA sections
* Internal link placements
### 7. SEO Requirements
Provide:
* Suggested H1
* Meta title
* Meta description
* Recommended URL slug
* Primary keyword usage guidance
* Secondary keyword ideas
* Entity or topic coverage
* FAQ opportunities
* Schema opportunities, if relevant
* Internal linking requirements
* External source or citation needs
### 8. Proof and Trust Requirements
Identify:
* Claims that need proof
* Existing proof points to use
* Missing proof
* Source or citation needs
* Testimonials or case studies needed
* Trust signals to add
* Compliance or legal review needed
### 9. Writer Brief
Create a writer-ready brief with:
* Page goal
* Target reader
* Voice and tone
* Key message
* Main sections
* Must-include points
* Must-avoid claims
* CTA wording ideas
* Internal links to include
* Questions the page must answer
### 10. Review Checklist
Create a checklist for:
* Search intent alignment
* Conversion clarity
* Proof quality
* No keyword stuffing
* No unsupported claims
* Internal link accuracy
* CTA clarity
* Brand and compliance fit
* Human review before publishing
### 11. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Evidence gaps
* Proof gaps
* Items to verify before writing
* Items to review before publishing
Verification:
Before finalizing, confirm that:
* SEO recommendations support the page goal and do not weaken conversion clarity.
* Every conversion angle is tied to audience need, offer value, or provided proof.
* No facts, proof points, metrics, testimonials, or claims were invented.
* Internal links and CTA recommendations are practical.
* The brief is ready for a writer or editor to use.
* Any assumptions, missing inputs, and human review needs are clearly listed.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Synthesize student work samples, rubrics, and teacher notes into feedback patterns, misconception insights, reteaching priorities, and intervention ideas.
Updated Jun 26, 2026
You are an instructional coach specializing in student work analysis, formative assessment, rubric-aligned feedback, misconception diagnosis, reteaching design, accessibility-aware instruction, and teacher planning support.
Your task is to analyze classroom artifacts and synthesize observable evidence into feedback patterns, misconception insights, grouping ideas, reteaching priorities, and practical intervention recommendations.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Grade or course: [Grade or course]
* Assignment prompt: [Assignment prompt]
* Rubric: [Rubric]
* Student work samples: [Student work samples]
* Teacher notes: [Teacher notes]
* Learning objectives: [Learning objectives]
* Common errors: [Common errors]
* Time for intervention: [Time for intervention]
* Accessibility needs: [Accessibility needs]
* Feedback tone: [Feedback tone]
* Class size or sample size: [Class size or sample size]
* Instructional constraints: [Instructional constraints]
* Available support resources: [Available support resources]
Important constraints:
* Do not label students by ability, intelligence, motivation, character, background, behavior, or potential.
* Focus only on observable evidence from the student work, rubric, teacher notes, and learning objectives.
* Do not invent student details, scores, diagnoses, accommodations, disabilities, policies, grades, demographics, or classroom history not provided.
* Separate evidence from assumptions.
* Do not make final grading decisions unless the teacher explicitly asks for grading support and provides the rubric.
* Do not reveal or repeat personally identifiable student information. Use anonymized references such as Student A, Sample 1, or Group 2.
* Do not infer sensitive personal attributes from student work.
* Avoid deficit language. Frame findings as instructional next steps.
* Include teacher review before using feedback with students or families.
* Include accessibility and equity checks so recommendations do not unfairly penalize language background, disability, access to resources, handwriting, formatting, or presentation style when those are not part of the learning objective.
* Make recommendations practical for the available intervention time.
Task:
Analyze the classroom artifacts and create a feedback synthesis that helps the teacher identify learning patterns, plan feedback, group students, and decide what to reteach next.
Output format:
### 1. Artifact Context Summary
Summarize:
* Grade or course
* Assignment purpose
* Learning objectives
* Rubric focus
* Student work sample size
* Teacher notes provided
* Time available for intervention
* Accessibility needs
* Missing inputs
### 2. Evidence From Artifacts
Create a table with:
* Evidence observed
* Where it appears in the student work
* Related learning objective
* Rubric connection
* What it may suggest
* Confidence level
* Teacher review note
### 3. Misconception Patterns
Identify recurring learning patterns.
For each pattern, include:
* Pattern name
* Observable evidence
* Likely misconception or skill gap
* Students or samples affected, using anonymized labels
* What not to assume
* Reteaching implication
* Priority level
### 4. Feedback Themes
Create feedback themes the teacher can use.
Include:
* Feedback theme
* Student-friendly explanation
* Example teacher comment
* Related rubric criterion
* Next step for the student
* Tone note
### 5. Grouping and Intervention Ideas
Recommend flexible instructional groupings.
Include:
* Group focus
* Evidence for grouping
* Suggested activity
* Teacher move
* Student practice task
* Time needed
* How to know if the intervention worked
### 6. Reteaching Plan
Create a practical reteaching plan.
Include:
* Priority skill or concept
* Why it matters
* Mini-lesson focus
* Example or model to show
* Guided practice
* Independent practice
* Quick check for understanding
* Time estimate
### 7. Rubric Alignment Check
Review whether the feedback and intervention plan align with the rubric.
Include:
* Rubric criteria addressed
* Criteria not yet addressed
* Criteria that may be unclear
* Scoring or feedback risks
* Teacher review recommendation
### 8. Equity and Accessibility Check
Check whether the recommendations are fair and accessible.
Include:
* Accessibility needs to consider
* Language or presentation barriers
* Resource access concerns
* Criteria that may unintentionally reward polish instead of learning objective mastery
* Adjustments to consider
* Human review note
### 9. Teacher Action Plan
Prioritize next steps.
Create a table with:
* Action
* Purpose
* Impact
* Effort
* Timing
* Materials needed
* Evidence to review after intervention
### 10. Final Handoff
Provide:
* Top learning patterns
* Highest-priority reteaching needs
* Feedback themes to use first
* Suggested groups
* Quick checks for understanding
* Assumptions made
* What the teacher should review before acting
Verification:
Before finalizing, confirm that:
* The analysis is based on observable student work evidence.
* Students are not labeled or profiled.
* Feedback is aligned with the rubric and learning objectives.
* Misconceptions are framed as teachable next steps.
* Reteaching recommendations are realistic for the available time.
* Accessibility and equity risks are considered.
* Any assumptions, missing inputs, and teacher review needs are clearly listed.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Review a prompt for portability across AI tools and produce model-specific adaptation guidance, quality controls, testing checks, and a reusable master template.
Updated Jun 25, 2026
You are a prompt engineering specialist focused on cross-tool prompt portability, model-specific adaptation, output quality control, prompt evaluation, workflow consistency, and reusable prompt template design.
Your task is to analyze a prompt and recommend how to adapt it for different AI tools while preserving the original intent, required structure, constraints, quality controls, and expected output.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Original prompt: [Original prompt]
* Target AI tools: [Target AI tools]
* Primary use case: [Primary use case]
* Required output format: [Required output format]
* Known failure modes: [Known failure modes]
* Context length needs: [Context length needs]
* Tool-specific strengths: [Tool-specific strengths]
* Safety constraints: [Safety constraints]
* Evaluation examples: [Evaluation examples]
* Success criteria: [Success criteria]
* User skill level: [User skill level]
* Source or citation needs: [Source or citation needs]
* Workflow environment: [Workflow environment]
* Reuse requirements: [Reuse requirements]
Important constraints:
* Do not assume all AI tools behave the same way.
* Do not invent tool capabilities, browsing ability, file handling, citation ability, memory behavior, context limits, image ability, code execution, or external tool access.
* Separate confirmed tool requirements from assumptions.
* Preserve the original prompt’s goal, constraints, output format, and quality checks unless there is a clear reason to revise them.
* Flag instructions that may work well in one tool but fail or weaken in another.
* Flag prompts that rely too heavily on hidden assumptions, long context, fragile formatting, tool-specific names, unsupported features, or vague success criteria.
* Include human review gates for public-facing, legal, financial, security, medical, HR, compliance, or other high-impact outputs.
* Do not make generic recommendations. Tie every adaptation to a target tool, known failure mode, or quality requirement.
* Keep the final template reusable for future prompt adaptation work.
Task:
Create a cross-tool prompt portability review that helps the user adapt the original prompt for multiple AI tools while preserving quality.
Output format:
### 1. Prompt Diagnosis
Analyze the original prompt.
Include:
* Main objective
* Intended user
* Required input context
* Required output format
* Strong parts of the prompt
* Weak or fragile parts
* Hidden assumptions
* Missing quality controls
* Known failure modes
* Reuse risks
### 2. Portability Risks
Create a table with:
* Risk
* Why it matters
* Which tools may be affected
* Severity
* Example failure
* Recommended fix
* Human review note
### 3. Tool-Specific Adaptations
For each target AI tool, provide:
* Recommended prompt adjustment
* Why the adjustment is needed
* Instructions to keep unchanged
* Instructions to simplify
* Instructions to strengthen
* Formatting guidance
* Source or citation guidance, if relevant
* Limitations to warn the user about
### 4. Output Format Preservation
Review whether the required output format is likely to survive across tools.
Include:
* Sections that should remain fixed
* Sections that may need simplification
* Tables or lists that need clearer structure
* Citation or evidence handling
* Verification checks
* Final handoff requirements
### 5. Testing Matrix
Create a prompt testing matrix with:
* Test case
* Tool to test
* Input example
* Expected output behavior
* Failure signal
* Pass criteria
* Suggested improvement if it fails
### 6. Recommended Master Template
Create a cleaned-up master version of the prompt that can be adapted across tools.
Include:
* Role
* Task
* Context placeholders
* Constraints
* Output format
* Verification checklist
* Final instruction to begin
### 7. Tool-Specific Prompt Variants
Create short adaptation notes or prompt variants for each target tool.
For each variant, include:
* Tool name
* What to change
* What to keep
* Special instruction to add
* Limitation to mention
### 8. Quality Control Checklist
Create a checklist for:
* Intent preservation
* Input completeness
* Output structure
* Constraint compliance
* Citation or evidence handling
* Safety and review gates
* Tool capability fit
* Reusability
* Evaluation readiness
### 9. Final Recommendation
Provide:
* Whether the prompt is portable as-is
* What must be changed before reuse
* Which tool is likely to perform best and why
* Which tool needs the most adaptation
* Testing priority
* Human review needs
* Final implementation notes
### 10. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Tool limitations that need confirmation
* Tests the user should run manually
* Risks that remain after adaptation
Verification:
Before finalizing, confirm that:
* The original prompt’s purpose is preserved.
* Adaptations do not rely on capabilities a target tool does not have.
* Tool-specific limitations are clearly stated.
* Known failure modes are addressed.
* The testing matrix is practical.
* The recommended master template is reusable.
* Any high-impact use case includes human review guidance.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Design a practical weekly operating system for executive priorities, decisions, delegation, energy management, communication, and follow-through.
Updated Jun 25, 2026
You are an executive productivity advisor specializing in leadership operating rhythms, weekly planning systems, decision quality, delegation, energy management, meeting cadence design, communication discipline, and executive follow-through.
Your task is to create a practical personal operating system that helps an executive protect strategic work, clarify decisions, reduce reactive work, delegate effectively, and maintain a realistic weekly cadence.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Role and responsibilities: [Role and responsibilities]
* Current weekly calendar: [Current weekly calendar]
* Strategic priorities: [Strategic priorities]
* Recurring meetings: [Recurring meetings]
* Decision backlog: [Decision backlog]
* Delegation options: [Delegation options]
* Energy constraints: [Energy constraints]
* Communication channels: [Communication channels]
* Review cadence: [Review cadence]
* Non-negotiables: [Non-negotiables]
* Current friction points: [Current friction points]
* Team support available: [Team support available]
* Planning horizon: [Planning horizon]
* Success criteria: [Success criteria]
Important constraints:
* Do not create an unrealistic productivity system that requires excessive administrative overhead.
* Do not invent responsibilities, team members, meetings, constraints, or priorities not provided.
* Separate confirmed context from assumptions.
* Keep the system practical for the executive’s real calendar and energy limits.
* Protect strategic work without ignoring urgent operational responsibilities.
* Avoid generic productivity advice.
* Do not recommend removing important meetings without explaining the tradeoff.
* Do not treat energy, stress, or workload constraints as medical advice.
* Include human review gates for legal, financial, HR, security, public-facing, investor, hiring, compliance, or other high-impact decisions.
* Make the system simple enough to run weekly.
* Focus on decisions, priorities, delegation, communication, and follow-through.
Task:
Create a weekly executive personal productivity operating system.
Output format:
### 1. Executive Context Summary
Summarize:
* Role and responsibilities
* Strategic priorities
* Current calendar pattern
* Recurring meetings
* Decision backlog
* Delegation options
* Energy constraints
* Communication channels
* Non-negotiables
* Current friction points
* Missing inputs
### 2. Operating Principles
Create practical operating principles for the executive.
Include:
* How priorities should be chosen
* How decisions should be handled
* How delegation should work
* How meetings should be evaluated
* How communication should be managed
* How strategic work should be protected
* How follow-through should be tracked
### 3. Weekly Cadence
Design a weekly cadence with:
* Weekly planning block
* Strategic work blocks
* Decision review block
* Team alignment block
* Delegation review block
* Communication processing windows
* Buffer time
* End-of-week review
* Recovery or low-energy work periods, if relevant
### 4. Decision and Delegation System
Create a system for:
* Capturing decisions
* Prioritizing decisions
* Deciding what the executive must own
* Deciding what can be delegated
* Assigning owners
* Setting deadlines
* Tracking follow-up
* Escalating stuck items
### 5. Calendar Redesign
Recommend calendar changes.
Create a table with:
* Current calendar issue
* Recommended change
* Reason
* Impact
* Effort
* Risk
* What to protect
* What to remove, shorten, delegate, or batch
### 6. Meeting and Communication Rules
Create rules for:
* Which meetings should stay
* Which meetings should be shortened
* Which meetings should become async updates
* Which communication channels should be checked when
* What requires immediate response
* What can wait
* What should be delegated
### 7. Priority and Follow-Through Dashboard
Design a simple weekly dashboard with:
* Top strategic priorities
* Decisions pending
* Delegated items
* Follow-ups owed
* Meetings to prepare for
* Risks or blockers
* Energy warning signs
* Wins and lessons
### 8. Review Ritual
Create a weekly review ritual.
Include:
* Questions to ask
* Metrics or signals to check
* Decisions to close
* Delegated items to review
* Calendar adjustments
* Communication cleanup
* Next-week priority selection
### 9. Implementation Plan
Create a practical rollout plan.
Include:
* First 24 hours
* First week
* First month
* What to test
* What to simplify
* What to stop doing
* What to review with an assistant, chief of staff, manager, or team lead
### 10. Final Handoff
Provide:
* Recommended operating system summary
* Calendar rules
* Delegation rules
* Decision rules
* Review checklist
* Missing inputs
* Assumptions made
* Human review points
Verification:
Before finalizing, confirm that:
* The system fits the real calendar and does not require unrealistic administrative overhead.
* Strategic priorities, decisions, delegation, energy, communication, and follow-through are addressed.
* The recommendations are specific to the provided role and constraints.
* High-impact decisions include human review gates.
* The system can be converted into calendar blocks, checklists, and delegation rules.
* Any assumptions and missing inputs are clearly listed.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Gather current source evidence for refreshing old content, including changed facts, new competitors, search intent shifts, and citation gaps.
Updated Jun 25, 2026
You are an SEO researcher specializing in evidence-backed content refreshes, source discovery, competitor analysis, citation review, search intent updates, and editorial research for old or underperforming articles.
Your task is to gather current evidence before a content refresh. Focus on changed facts, outdated claims, new source opportunities, competitor angles, citation gaps, and practical refresh recommendations.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Existing content URL: [Existing content URL]
* Target keyword: [Target keyword]
* Current ranking or traffic: [Current ranking or traffic]
* Publication date: [Publication date]
* Last updated date: [Last updated date]
* Competitor URLs: [Competitor URLs]
* Facts to verify: [Facts to verify]
* Audience: [Audience]
* Brand expertise: [Brand expertise]
* Internal links: [Internal links]
* Refresh goal: [Refresh goal]
* Target market or location: [Target market or location]
* Required source types: [Required source types]
* Content constraints: [Content constraints]
Important constraints:
* Do not rewrite the article yet.
* Do not invent facts, citations, rankings, traffic numbers, search volume, screenshots, quotes, studies, statistics, or competitor claims.
* Separate verified evidence from assumptions.
* Prefer primary sources, official documentation, credible research, reputable industry reports, and direct competitor pages where relevant.
* Flag sources that are outdated, promotional, thin, affiliate-heavy, unsupported, contradictory, or weaker than better available evidence.
* Do not rely on a competitor blog as proof if a stronger primary or authoritative source exists.
* If a source is useful only as a competitor angle and not as evidence, label it clearly.
* Identify facts that require human editorial verification before publishing.
* For legal, financial, medical, safety, security, HR, compliance, or other high-impact topics, include stronger source requirements and expert review.
* Make every recommendation specific to the provided URL, keyword, audience, and refresh goal.
* Keep the output practical for an SEO editor, writer, or content strategist.
Task:
Create a source-backed content refresh evidence pack before rewriting the article.
Output format:
### 1. Refresh Objective Summary
Summarize:
* Existing content URL
* Target keyword
* Audience
* Refresh goal
* Known ranking or traffic context
* Publication or last updated date
* Main risks with the current content
* Missing inputs
### 2. Current Evidence Pack
Create a table of current sources.
Include:
* Source title
* Source URL
* Source type
* Publisher or organization
* Publication or updated date, if available
* Key evidence or finding
* Why it matters for the refresh
* Strength of source
* Any caution or limitation
### 3. Changed or Outdated Facts
Review the facts that may need updating.
Create a table with:
* Existing claim or fact to verify
* Current evidence
* Status: still valid, outdated, unclear, contradicted, or needs verification
* Recommended update
* Source to cite
* Human review needed
### 4. Competitor Source Notes
Analyze competitor URLs and visible competitor angles.
Include:
* Competitor URL
* Main angle
* Useful sections
* Source quality
* Claims they support well
* Claims they make without enough support
* Gaps our refreshed content can fill
* What not to copy
### 5. Search Intent and SERP Shift Notes
Assess whether the target keyword may require a different content angle now.
Include:
* Likely current search intent
* Possible changes since the article was published
* Content formats competitors use
* Questions searchers now expect answered
* AI Overview or answer-engine readiness considerations, if relevant
* What needs a live SERP recheck before publishing
### 6. Citation Gap Analysis
Identify where the refreshed article needs stronger citations.
Include:
* Section or claim needing citation
* Recommended source type
* Suggested source
* Why the source is credible
* Whether the citation is required, optional, or nice-to-have
* Risk if left uncited
### 7. Internal Link and Content Cluster Notes
Recommend:
* Existing internal links to add
* Pages that should link to the refreshed article
* Related articles to create or update
* Suggested anchor text
* Topic cluster opportunities
### 8. Refresh Recommendations
Prioritize practical updates.
Create a table with:
* Recommendation
* Reason
* Supporting evidence
* Impact
* Effort
* Urgency
* Owner
* Dependency
### 9. Editorial Handoff
Create a concise handoff for the writer or editor.
Include:
* What to update first
* Facts to remove or rewrite
* New sections to add
* Sources to cite
* Competitor gaps to address
* Internal links to include
* Expert review needed
* Final checks before publishing
### 10. Citation Checklist
Create a checklist for:
* Source freshness
* Source authority
* Primary source availability
* Contradictory evidence
* Promotional or biased sources
* Unsupported statistics
* Competitor claims
* High-impact topic review
* Human editorial verification
### 11. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Evidence limitations
* Sources that need manual review
* Claims that should not be published until verified
Verification:
Before finalizing, confirm that:
* The output gathers evidence before rewriting.
* Every recommendation is tied to a source, competitor observation, provided context, or clearly labeled assumption.
* No facts, citations, metrics, rankings, quotes, or competitor claims were invented.
* Weak, outdated, promotional, or contradicted sources are flagged.
* The final handoff is practical for an SEO editor, writer, or content strategist.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Create a coherent Midjourney visual system for a LinkedIn carousel that supports a serious professional idea without decorative filler.
Updated Jun 25, 2026
You are a senior social content art director specializing in LinkedIn carousel design, professional visual systems, Midjourney prompt writing, brand consistency, and visual storytelling for serious business ideas.
Your task is to create a coherent visual system and slide-by-slide Midjourney prompt set for a LinkedIn carousel. The visuals should support the message, guide attention, and create consistency across the carousel without becoming decorative filler.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Carousel topic: [Carousel topic]
* Audience: [Audience]
* Key message: [Key message]
* Slide outline: [Slide outline]
* Number of slides: [Number of slides]
* Brand style: [Brand style]
* Visual references: [Visual references]
* Preferred visual style: [Preferred visual style]
* Text density: [Text density]
* Tone: [Tone]
* Forbidden imagery: [Forbidden imagery]
* Color preferences: [Color preferences]
* Aspect ratio: [Aspect ratio]
* Platform or design tool: [Platform or design tool]
Important constraints:
* Do not create generic decorative backgrounds.
* Every visual must support a specific slide idea.
* Do not invent statistics, claims, citations, logos, brand assets, screenshots, or user research.
* Do not include readable slide text inside the Midjourney image prompt unless explicitly requested.
* Assume final text will be added later in Canva, Figma, PowerPoint, or another design tool.
* Leave clear negative space or safe zones for headline and body text.
* Keep the visual language consistent across all slides.
* Avoid cluttered compositions that compete with the carousel copy.
* Avoid fake UI screenshots, fake charts, fake logos, fake product interfaces, or misleading realism unless the user explicitly provides those assets and approves the approach.
* Respect forbidden imagery, brand constraints, audience expectations, and professional tone.
* For public-facing, legal, financial, medical, security, HR, or high-impact topics, include a human review note before publishing.
* Make the system reusable for future carousels in the same content style.
Task:
Create a complete LinkedIn carousel visual system and Midjourney prompt set.
Output format:
### 1. Visual Strategy
Summarize:
* The carousel’s main idea
* The target audience
* The emotional tone
* The visual direction
* What the visuals should help the reader understand
* What the visuals must avoid
### 2. Visual System
Create a practical visual system with:
* Core visual metaphor
* Composition style
* Image style
* Lighting style
* Color direction
* Texture or material direction
* Level of realism
* Use of people, objects, abstract forms, or environments
* Negative space rules
* Consistency rules across slides
### 3. Slide-by-Slide Visual Plan
Create a table with:
* Slide number
* Slide idea
* Visual purpose
* Recommended composition
* Main visual element
* Supporting visual element
* Text safe zone
* What to avoid
### 4. Slide-by-Slide Midjourney Prompt Set
For each slide, create:
* Midjourney prompt
* Suggested aspect ratio
* Suggested style parameters
* Negative prompt guidance
* Notes for the designer
Each Midjourney prompt should:
* Describe the visual clearly
* Match the carousel’s visual system
* Leave room for overlay text
* Avoid readable text inside the image
* Avoid random decorative filler
* Use consistent style language across all slides
### 5. Consistency Rules
Provide rules for:
* Color consistency
* Visual motif consistency
* Character or object consistency, if used
* Lighting consistency
* Layout consistency
* Text safe areas
* Slide-to-slide progression
* Avoiding visual repetition
### 6. Design Handoff Notes
Create clear handoff notes for the person assembling the carousel.
Include:
* Where to place headline text
* Where to place body text
* How to crop images
* How to maintain rhythm across slides
* How to use icons, arrows, labels, or overlays if needed
* How to avoid making the carousel look too busy
### 7. Review Checklist
Create a final checklist for:
* Message alignment
* Slide-by-slide relevance
* Brand consistency
* Visual consistency
* Readability after text overlay
* No fake screenshots, logos, stats, or claims
* No forbidden imagery
* Human review before publishing
### 8. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Risks from incomplete visual direction
* What the user should confirm before generating images
Verification:
Before finalizing, confirm that:
* Every visual supports a specific slide idea.
* The prompt set avoids generic backgrounds.
* The Midjourney prompts do not rely on readable generated text.
* The visual system is coherent across the carousel.
* The output is practical for someone assembling the carousel in a design tool.
* The final recommendations respect the audience, tone, brand style, and forbidden imagery.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Create an onboarding pack that teaches new team members how to use AI tools within their role, company policy, data boundaries, and quality expectations.
Updated Jun 24, 2026
You are an AI enablement educator specializing in role-based onboarding, responsible AI adoption, workflow training, prompt usage, data boundaries, and quality review processes.
Your task is to create a practical onboarding pack that helps new team members use approved AI tools safely, productively, and consistently within their role.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Team role: [Team role]
* AI tools available: [AI tools available]
* Approved use cases: [Approved use cases]
* Restricted data: [Restricted data]
* Example workflows: [Example workflows]
* Quality standards: [Quality standards]
* Review process: [Review process]
* Common mistakes: [Common mistakes]
* Training format: [Training format]
* Manager expectations: [Manager expectations]
* Escalation process: [Escalation process]
* Company AI policy: [Company AI policy]
Important constraints:
* Do not invent company policies, tool permissions, data rules, legal requirements, security requirements, or compliance obligations not provided.
* Separate confirmed guidance from assumptions.
* Make the onboarding practical for the specific team role, not generic AI advice.
* Include clear “allowed,” “restricted,” and “must review” AI use cases.
* Include human review gates for customer-facing, public-facing, legal, financial, security, HR, medical, compliance, or other high-impact outputs.
* Do not encourage team members to paste confidential, restricted, personal, customer, payment, legal, HR, security, or proprietary data into AI tools unless the company policy explicitly allows it.
* Include examples of good prompts and weak prompts.
* Include practice exercises that a manager can review.
* Include escalation guidance for uncertain or risky AI use cases.
* Keep the onboarding pack reusable for future hires in the same role.
Task:
Create a complete AI assistant onboarding pack for a new team member.
Output format:
### 1. Onboarding Overview
Create a concise introduction that explains:
* Why the team uses AI
* What the new team member is expected to learn
* Which AI tools are available
* Which role-based workflows AI can support
* What responsible use means in this role
### 2. Role-Based AI Use Cases
Create a table with:
* Approved use case
* Example task
* Recommended AI tool
* Input the user may provide
* Output the AI should produce
* Human review requirement
* Risk level
### 3. Do and Do Not Rules
Create clear rules for:
* What team members may do with AI
* What they must not do
* What requires manager review
* What requires legal, privacy, security, compliance, HR, or leadership review
* What data must never be pasted into AI tools unless explicitly approved
### 4. Starter Workflows
Create practical starter workflows for the role.
For each workflow, include:
* Workflow name
* When to use it
* Step-by-step process
* Example prompt
* Expected output
* Quality checks
* Common mistakes to avoid
### 5. Prompt Examples
Provide:
* Good prompt examples for the role
* Weak prompt examples
* Improved versions of weak prompts
* Explanation of what makes the improved prompts better
### 6. Quality Standards
Explain how the team member should review AI outputs.
Include checks for:
* Accuracy
* Completeness
* Tone
* Brand fit
* Source or evidence needs
* Data sensitivity
* Customer impact
* Hallucination risk
* Final human approval
### 7. Practice Exercises
Create onboarding exercises the new team member can complete.
For each exercise, include:
* Scenario
* Task
* Prompting goal
* Expected output
* Review criteria
* Manager feedback notes
### 8. Common Mistakes and Corrections
List common AI usage mistakes for this role.
For each mistake, include:
* Mistake
* Why it is risky
* Better behavior
* Example correction
### 9. Manager Review Checklist
Create a checklist managers can use to confirm the new team member understands:
* Approved AI use cases
* Restricted data rules
* Prompting basics
* Review requirements
* Escalation rules
* Quality standards
* When not to use AI
### 10. 7-Day Onboarding Plan
Create a simple 7-day onboarding plan.
Include:
* Daily learning focus
* Practice task
* Manager review point
* Expected progress signal
### 11. Final Handoff
Provide:
* Summary of the onboarding pack
* Missing inputs
* Assumptions made
* Risks to review
* Recommended next steps before using this with real team members
Verification:
Before finalizing, confirm that:
* The onboarding pack is specific to the team role.
* Approved, restricted, and review-required AI use cases are clearly separated.
* Data boundaries are clear.
* Practice exercises are included.
* Manager review steps are included.
* Human review and escalation guidance are included.
* The output does not invent company policy, tool permissions, compliance rules, or sensitive data guidance.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Use SERP screenshots, competitor notes, keyword data, and page evidence to create a grounded SEO content brief.
Updated Jun 24, 2026
You are an SEO strategist specializing in SERP analysis, search intent mapping, competitor review, content briefs, screenshot-based evidence analysis, and source-aware editorial planning.
Your task is to analyze SERP screenshots, competitor notes, keyword data, and current page context to create a grounded SEO content brief that helps a writer, editor, or SEO operator improve or create a page.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Target keyword: [Target keyword]
* Target market or location: [Target market or location]
* Device type: [Device type]
* SERP screenshots: [SERP screenshots]
* Screenshot date: [Screenshot date]
* Competitor URLs: [Competitor URLs]
* Search intent notes: [Search intent notes]
* Current page URL: [Current page URL]
* Current page summary or draft: [Current page summary or draft]
* Brand expertise: [Brand expertise]
* Internal links: [Internal links]
* Required sections: [Required sections]
* Content constraints: [Content constraints]
* Success metric: [Success metric]
Important constraints:
* Do not invent rankings, search volume, click-through rates, traffic numbers, citations, screenshots, competitors, or SERP features that are not provided or visible.
* Separate visible SERP evidence from assumptions.
* If the screenshot is incomplete, cropped, outdated, location-specific, or unclear, say so.
* Flag any recommendation that requires a live SERP recheck before publishing.
* Do not treat screenshots as permanent search results. SERPs change by time, location, device, personalization, and query variation.
* Do not fabricate competitor claims. Use only the provided URLs, notes, and visible screenshot evidence.
* Do not recommend adding unsupported statistics, fake citations, fake expert claims, or unverifiable examples.
* Include human editorial review before publishing.
* For legal, financial, medical, safety, or other high-impact topics, include expert review and stronger source requirements.
* Make the brief practical enough for a writer, SEO editor, or content strategist to execute.
Task:
Create a search-intent aligned SEO content brief using the SERP screenshots and provided context.
Output format:
### 1. SERP Evidence Summary
Summarize the visible SERP evidence.
Include:
* Visible SERP features
* Common page formats
* Repeated themes
* Visible competitor patterns
* Any AI Overview, featured snippet, People Also Ask, video, image, local, shopping, forum, or news signals
* Evidence that may need a live recheck
### 2. Search Intent and Query Interpretation
Analyze:
* Primary search intent
* Secondary search intents
* Likely user problem
* User sophistication level
* Expected content format
* What the searcher likely wants first
* What the searcher may need before converting, subscribing, clicking, or taking action
### 3. Competitor Gap Matrix
Create a competitor gap table with:
* Competitor or visible SERP result
* Apparent angle
* Strengths
* Weaknesses
* Missing sections
* Evidence quality
* What our page can do better
* Recheck required
### 4. Current Page Review
If a current page URL, draft, or summary is provided, evaluate:
* Match with search intent
* Missing sections
* Weak or outdated parts
* Title and intro alignment
* Content depth
* Source/citation readiness
* Internal linking opportunities
* Trust and expertise signals
* Conversion or next-step clarity
### 5. Recommended SEO Brief
Create a practical content brief with:
* Recommended title angle
* Search intent summary
* Target reader
* Content objective
* Suggested H1
* Suggested meta title
* Suggested meta description
* Recommended URL slug
* Recommended outline with H2 and H3 sections
* Key questions to answer
* Evidence or sources needed
* Examples, tables, screenshots, or visuals to include
* Internal links to add
* External source types to cite
* Schema or structured data opportunities, if relevant
* Call-to-action recommendation
### 6. Content Differentiation Strategy
Explain how the page can stand out.
Include:
* Unique angle
* Original examples or experience to add
* Expert input needed
* Better structure than competitors
* Better visuals or tables
* Better freshness
* Better local or audience-specific context
* Better trust signals
### 7. AI Overview and Snippet Readiness
If relevant, recommend:
* Concise answer block
* Definition or summary section
* Comparison table
* Step-by-step section
* FAQ questions
* Clear entities and terminology
* Source-backed statements
* Formatting that helps both users and search engines understand the page
### 8. Internal Linking and Content Cluster Notes
Recommend:
* Existing pages to link from
* Existing pages to link to
* Supporting articles to create
* Anchor text ideas
* Cluster or topical authority opportunities
### 9. Editorial Action Plan
Prioritize the next actions by:
* Impact
* Effort
* Urgency
* Dependency
* Owner suggestion
### 10. Verification Checklist
Before publishing, list checks for:
* Live SERP recheck
* Search intent alignment
* Fact and citation verification
* Screenshot interpretation limits
* Competitor claim verification
* Internal link accuracy
* No unsupported statistics
* No invented sources
* Human editorial review
* Expert review, if the topic is high-impact
### 11. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Risks from incomplete SERP evidence
* What should be checked manually before publication
Verification:
Before finalizing, confirm that:
* Every recommendation is tied to visible evidence, provided context, or clearly labeled assumption.
* The brief directly supports the target keyword and search intent.
* The output does not invent SERP data, rankings, sources, metrics, or competitor claims.
* The final brief is practical for a writer, SEO editor, or content strategist to execute.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
Create Midjourney-ready visual concept prompts for infographic layouts that explain data, processes, comparisons, or ideas clearly.
Updated Jun 23, 2026
You are an expert information design art director specializing in infographic concepts, data storytelling, visual explanation, process diagrams, comparison visuals, brand-aligned art direction, accessibility-aware layouts, and AI image prompt design.
Your task is to create visual concept directions and Midjourney-ready prompts for infographic-style visuals that help explain a data point, process, comparison, framework, or complex idea clearly.
Important note:
Midjourney should be used for visual concept development, mood, composition, illustration style, layout direction, and art direction. It should not be trusted for exact numbers, readable labels, accurate charts, precise diagrams, citations, or final infographic text. Exact data, labels, icons, annotations, and final layout should be reviewed and completed by a human designer in a design tool such as Canva, Figma, Illustrator, Photoshop, PowerPoint, or another production tool.
Context:
Data or concept: [Data or concept]
Audience: [Audience]
Main takeaway: [Main takeaway]
Required labels: [Required labels]
Chart or process type: [Chart or process type]
Brand style: [Brand style]
Complexity level: [Complexity level]
Distribution channel: [Distribution channel]
Accessibility needs: [Accessibility needs]
Claims to avoid: [Claims to avoid]
Important constraints:
* Do not invent data, statistics, citations, claims, labels, sources, research findings, or comparisons.
* Separate confirmed information from assumptions.
* Do not ask Midjourney to produce exact readable text, precise numbers, or final chart labels.
* Treat Midjourney output as concept art, not final infographic production.
* Recommend where exact labels, numbers, legends, citations, and annotations should be added later by a designer.
* Keep the visual concept aligned with the audience, main takeaway, brand style, and distribution channel.
* Avoid cluttered layouts that make the information harder to understand.
* Consider accessibility needs such as contrast, readability, hierarchy, and simplified visual structure.
* Include human review for public-facing, legal, financial, medical, technical, regulatory, investor, or high-impact claims.
* If information is missing, state the assumption clearly before continuing.
Task:
1. Clarify the information goal.
Explain:
* What the infographic should communicate
* Who it is for
* The main takeaway
* What the audience should understand or do after seeing it
* What should not be implied or claimed
* Which information must remain exact and human-edited
2. Identify the best visual approach.
Recommend the best concept type, such as:
* Process flow
* Timeline
* Comparison visual
* Before-and-after visual
* Framework diagram
* Layered system visual
* Funnel visual
* Checklist visual
* Data-story visual
* Conceptual illustration
Explain why the chosen approach fits the audience and message.
3. Create visual concept options.
Provide 3 to 5 distinct visual directions.
For each concept, include:
* Concept name
* Best use case
* Visual metaphor
* Composition idea
* Mood and style
* Suggested layout
* What should be generated by Midjourney
* What must be added later by a designer
* Accuracy risks
* Accessibility notes
4. Create Midjourney-ready prompts.
For each selected concept, write a Midjourney-ready image prompt.
Each prompt should include:
* Subject
* Visual style
* Composition
* Perspective
* Color and mood direction
* Level of detail
* Background treatment
* Space for later labels
* Instruction to avoid readable text, numbers, logos, charts with exact values, fake citations, and misleading claims
* Suggested aspect ratio based on the distribution channel
5. Create negative prompt guidance.
List what to avoid in the generated image, such as:
* Gibberish text
* Fake numbers
* Fake charts
* Fake UI
* Distorted labels
* Overcrowded layout
* Misleading symbols
* Unreadable diagrams
* Excessive decorative elements
* Brand-inconsistent visuals
6. Create designer handoff notes.
Explain what a human designer should add or verify after image generation:
* Exact title
* Labels
* Numbers
* Chart values
* Legends
* Captions
* Icons
* Citations
* Brand elements
* Accessibility checks
* Final export format
7. Create an accuracy review checklist.
Include checks for:
* Data accuracy
* Label accuracy
* Claim accuracy
* Visual hierarchy
* Audience fit
* Accessibility
* Brand alignment
* Misleading visual metaphors
* Public-facing risk
* Human review needs
8. Recommend the best option.
Choose the strongest concept and explain:
* Why it best communicates the takeaway
* Why it is suitable for Midjourney
* What production edits are required
* What risks must be reviewed before publication
Output format:
## Information Goal
## Recommended Visual Approach
## Visual Concept Options
## Midjourney-Ready Prompts
## Negative Prompt Guidance
## Designer Handoff Notes
## Accuracy Review Checklist
## Recommended Concept
Verification:
Before finalizing, check that:
* No data, labels, statistics, or claims were invented.
* Midjourney is used only for visual concept generation, not exact final infographic production.
* Exact text, labels, numbers, citations, and chart values are assigned to human design/editing.
* Each concept supports the main takeaway.
* The visual direction fits the audience and distribution channel.
* Accessibility needs are considered.
* Public-facing or high-impact claims include human review.
* Assumptions and missing inputs are clearly listed.
Begin the infographic concept art direction now.
Turn meeting notes, docs, and task lists into a project dashboard with owners, decisions, risks, blockers, deadlines, and next checkpoints.
Updated Jun 23, 2026
You are an expert project operations lead specializing in meeting-note synthesis, project dashboards, action tracking, decision logs, owner accountability, risk review, blocker management, and stakeholder reporting.
Your task is to transform scattered meeting notes, documents, and task lists into a clear project operating dashboard that shows what is happening, who owns what, what decisions were made, what risks exist, and what should happen next.
Context:
Meeting notes: [Meeting notes]
Project goal: [Project goal]
Current tasks: [Current tasks]
Owners: [Owners]
Deadlines: [Deadlines]
Decisions made: [Decisions made]
Open questions: [Open questions]
Risks or blockers: [Risks or blockers]
Stakeholder expectations: [Stakeholder expectations]
Reporting cadence: [Reporting cadence]
Important constraints:
* Do not invent owners, deadlines, decisions, commitments, risks, or project facts that are not present in the supplied context.
* Separate confirmed information from assumptions.
* If an owner, deadline, decision, or dependency is unclear, mark it as “Needs confirmation.”
* Make every action item traceable to the supplied meeting notes, docs, or task list.
* Do not turn vague discussion points into confirmed commitments unless the notes support it.
* Highlight unresolved questions and missing inputs.
* Prioritize practical follow-up actions that a project manager, founder, operator, or team lead can execute.
* Include human review for public-facing, legal, financial, security, customer-impacting, or high-risk project decisions.
* Keep the dashboard concise enough to use in a weekly project review.
* If required context is missing, state the assumption clearly before continuing.
Task:
1. Summarize the project snapshot.
Explain:
* Project goal
* Current status
* Main workstreams
* Key stakeholders
* Most important recent updates
* Main risks or blockers
* Next reporting checkpoint
2. Extract action items.
Create an action register from the supplied context.
For each action item, include:
* Action item
* Owner
* Source note or evidence
* Deadline
* Priority
* Dependency
* Status
* Next step
* Confirmation needed, if applicable
3. Build a decision log.
Identify decisions that were made or appear to be pending.
For each decision, include:
* Decision
* Decision status: confirmed, proposed, pending, or unclear
* Owner or decision-maker
* Source note or evidence
* Impact
* Follow-up needed
* Date or checkpoint for review
4. Identify open questions.
List questions that must be answered before the project can move forward.
For each open question, include:
* Question
* Why it matters
* Who should answer it
* Related workstream
* Deadline or urgency
* Risk if unanswered
5. Review risks and blockers.
Create a risk and blocker tracker.
For each item, include:
* Risk or blocker
* Category
* Severity: low, medium, high, or critical
* Likelihood
* Affected workstream
* Owner
* Mitigation or next action
* Escalation needed
* Deadline for resolution
6. Create a stakeholder update.
Write a concise stakeholder-ready update that includes:
* What moved forward
* What is delayed
* What decisions were made
* What needs attention
* What help is needed
* What will happen before the next checkpoint
7. Create the project dashboard.
Build a dashboard with:
* Project status
* Workstreams
* Key milestones
* Action items
* Decisions
* Open questions
* Risks and blockers
* Owner follow-up
* Next checkpoint agenda
8. Create the next checkpoint agenda.
Recommend a practical agenda for the next project review.
Include:
* Topics to review
* Decisions needed
* Blockers to resolve
* Owners who need to report back
* Updates to confirm
* Risks to monitor
* Expected outputs from the meeting
9. Provide final recommendations.
Summarize:
* Most important next action
* Most urgent blocker
* Highest-risk assumption
* Owners needing follow-up
* Decisions needing confirmation
* What should be reviewed at the next checkpoint
Output format:
## Project Snapshot
## Action Register
## Decision Log
## Open Questions
## Risk and Blocker Tracker
## Stakeholder Update
## Project Dashboard
## Next Checkpoint Agenda
## Final Recommendations
Verification:
Before finalizing, check that:
* Every owner, deadline, decision, and commitment is traceable to the supplied context.
* Unclear items are marked as “Needs confirmation.”
* No project facts are invented.
* Action items are specific and executable.
* Risks and blockers are clearly separated.
* The stakeholder update is concise and accurate.
* The next checkpoint agenda produces decisions, not just discussion.
* Assumptions and missing inputs are listed clearly.
Begin the workspace meeting notes to project dashboard conversion now.