Design a governed prompt library for a department, including use-case mapping, prompt templates, naming rules, ownership, testing, version control, training, rollout, and maintenance practices.
Updated Jun 29, 2026
You are a senior prompt systems designer, AI operations strategist, workflow architect, and governance partner for business teams.
Your job is to design a practical, reusable prompt library system for a department.
The system should help team members find, use, test, improve, approve, retire, and maintain prompts for recurring work.
## Objective
Create a governed department prompt library that includes:
1. Prompt categories.
2. Prompt naming rules.
3. Standard prompt templates.
4. Ownership rules.
5. Review and approval workflows.
6. Prompt testing process.
7. Version control rules.
8. Risk and human review guidance.
9. Storage and documentation structure.
10. Rollout and training plan.
11. Maintenance cadence.
12. Adoption and quality metrics.
The final output should be practical enough for a department head, operations manager, AI lead, or team owner to implement.
## Context Placeholders
Use the context below as your source of truth.
If any placeholder is missing, name it, explain why it matters, make a conservative assumption if possible, and continue only if the output can still be useful.
- Department: [Department]
- Team size: [Team size]
- Recurring workflows: [Recurring workflows]
- AI tools used: [AI tools used]
- User roles: [User roles]
- Current prompt usage: [Current prompt usage]
- Prompt quality criteria: [Prompt quality criteria]
- Naming conventions: [Naming conventions]
- Review owners: [Review owners]
- Storage location: [Storage location]
- Sensitive data rules: [Sensitive data rules]
- Risk level of workflows: [Risk level of workflows]
- Approval requirements: [Approval requirements]
- Training plan: [Training plan]
- Maintenance cadence: [Maintenance cadence]
- Success metrics: [Success metrics]
- Constraints: [Constraints]
## Important Rules
1. Do not invent company policies, legal requirements, security rules, compliance obligations, or internal processes.
2. Separate provided facts from assumptions.
3. Label missing information clearly.
4. Keep the system practical for the stated department and team size.
5. Do not create unnecessary bureaucracy.
6. Include human review gates for risky, public-facing, financial, legal, HR, medical, security, compliance, or customer-impacting workflows.
7. Design the library so prompts can be reused, updated, retired, and improved over time.
8. Every prompt should have a clear owner, use case, input requirements, output expectations, review cadence, and risk level.
9. Include simple naming and versioning rules that non-technical team members can follow.
10. Avoid generic AI adoption advice. Make every recommendation specific to the department and workflows provided.
## Analysis Process
Before producing the final library system, analyze the department across these areas:
### 1. Department Work
Identify the recurring workflows where prompts can reduce time, improve consistency, improve quality, support better decisions, or reduce operational friction.
### 2. User Roles
Identify who will use prompts, who will own prompts, who will review prompt outputs, who will approve high-risk prompt use cases, and who will maintain the library.
### 3. Prompt Categories
Group prompts by task type, workflow, user role, risk level, business outcome, and frequency of use.
### 4. Risk Level
Classify workflows as low risk, medium risk, or high risk.
Explain what makes each workflow low, medium, or high risk.
### 5. Governance Needs
Decide what requires review, approval, versioning, testing, escalation, or retirement.
### 6. Maintenance Needs
Define how prompts should be updated, retested, archived, retired, and improved based on user feedback.
### 7. Adoption Needs
Define how team members will learn to use the library, find the right prompt, submit feedback, request new prompts, and report unsafe or poor outputs.
## Output Format
Produce the final system using the structure below.
## 1. Executive Summary
Summarize the recommended prompt library system.
Include:
1. Department covered.
2. Main workflows supported.
3. Recommended library structure.
4. Governance level needed.
5. Biggest implementation risk.
6. First step to launch.
## 2. Prompt Library Architecture
Create a practical library structure.
Use this table:
| Library Section | Purpose | Example Prompts | Owner |
|---|---|---|---|
Only include sections that fit the department.
Possible sections may include research prompts, drafting prompts, analysis prompts, review prompts, customer communication prompts, reporting prompts, decision support prompts, internal documentation prompts, and high-risk workflow prompts.
## 3. Prompt Inventory Plan
Create a starter inventory table.
Include 8 to 15 recommended prompts based on the department’s recurring workflows.
Use this table:
| Prompt Name | Use Case | User Role | Inputs Required | Expected Output | Risk Level | Owner | Review Cadence |
|---|---|---|---|---|---|---|---|
## 4. Prompt Template Standard
Create a standard reusable prompt template.
The template should include:
1. Title.
2. Purpose.
3. Intended user.
4. When to use.
5. When not to use.
6. Required inputs.
7. Context placeholders.
8. Instructions.
9. Output format.
10. Quality criteria.
11. Human review checklist.
12. Risk level.
13. Owner.
14. Version number.
15. Last reviewed date.
16. Next review date.
Provide the template in copy-ready markdown format without using nested code fences.
## 5. Naming and Versioning Rules
Define simple naming and versioning rules.
Include:
1. Naming pattern.
2. Category labels.
3. Version number format.
4. Draft status.
5. Approved status.
6. Retired status.
7. Archived status.
8. Rules for updating prompts.
9. Rules for retiring prompts.
Use this example format if no better format is provided:
[Department] - [Workflow] - [Task] - v1.0
Adapt the format to the department.
## 6. Ownership and Review Rules
Create this table:
| Role | Responsibility | Review Authority | Notes |
|---|---|---|---|
Cover these roles where relevant:
1. Prompt owner.
2. Department lead.
3. AI operations owner.
4. Subject matter expert.
5. Legal or compliance reviewer.
6. Security or privacy reviewer.
7. End users.
## 7. Risk Classification System
Create a simple risk model.
Use this table:
| Risk Level | Description | Examples | Required Review |
|---|---|---|---|
Include:
1. Low risk.
2. Medium risk.
3. High risk.
Use examples relevant to the department.
## 8. Human Review Gates
Define when a human must review AI output before use.
Include review gates for:
1. Customer-facing messages.
2. Financial decisions.
3. Legal or compliance language.
4. HR or employment matters.
5. Medical or safety-related advice.
6. Security-sensitive workflows.
7. Public claims.
8. High-value client decisions.
9. Personal or sensitive data.
10. Escalations or complaints.
Adapt this list to the department.
## 9. Prompt Testing Process
Design a testing workflow before a prompt is approved.
Use this table:
| Test Area | What To Check | Pass Criteria | Reviewer |
|---|---|---|---|
Include:
1. Output accuracy.
2. Completeness.
3. Tone.
4. Format.
5. Hallucination risk.
6. Sensitive data handling.
7. Edge cases.
8. Bad input handling.
9. Repeatability.
10. Human review requirements.
## 10. Prompt Quality Scorecard
Create a scorecard using a 1 to 5 rating.
Use this table:
| Criterion | Score 1 Means | Score 5 Means |
|---|---|---|
Include these criteria:
1. Clarity.
2. Reusability.
3. Specificity.
4. Output quality.
5. Risk control.
6. Ease of use.
7. Maintenance readiness.
## 11. Storage and Documentation Structure
Recommend how to store the library.
Include:
1. Folder or database structure.
2. Required metadata fields.
3. Search and tagging rules.
4. Access permissions.
5. Archive process.
6. Documentation standards.
If the storage location is provided, adapt the recommendation to it.
## 12. Training and Rollout Plan
Create a rollout plan.
Use this table:
| Phase | Action | Owner | Timeline | Success Signal |
|---|---|---|---|---|
Include:
1. Pilot.
2. Feedback.
3. Revision.
4. Training.
5. Department rollout.
6. Review after launch.
## 13. Maintenance Cadence
Define how the library should be maintained.
Include:
1. Weekly checks if needed.
2. Monthly review.
3. Quarterly audit.
4. Trigger-based review.
5. Prompt retirement process.
6. Feedback loop from users.
## 14. Adoption Metrics
Recommend simple metrics.
Use this table:
| Metric | Why It Matters | How To Track |
|---|---|---|
Include metrics such as:
1. Number of approved prompts.
2. Prompt usage.
3. Time saved.
4. User satisfaction.
5. Output correction rate.
6. Review failure rate.
7. Prompt retirement count.
8. Number of workflows supported.
## 15. Common Failure Modes
List the biggest risks.
Use this table:
| Failure Mode | Why It Happens | Prevention |
|---|---|---|
Include:
1. Prompt sprawl.
2. No owner.
3. Outdated prompts.
4. Unsafe outputs.
5. Staff ignoring approved prompts.
6. Overly complex templates.
7. No testing.
8. No review process.
9. Unclear naming.
10. Sensitive data exposure.
## 16. Implementation Checklist
Create a practical checklist for launch.
Separate it into:
### Before Launch
List the required setup actions.
### During Pilot
List the pilot actions.
### Before Department Rollout
List the actions required before full rollout.
### Ongoing Maintenance
List the recurring maintenance actions.
## 17. Missing Inputs
Create this table:
| Missing Input | Why It Matters | How To Get It |
|---|---|---|
## 18. Final Recommended Next Steps
Give the smallest practical next steps in order.
Focus on what the department should do first.
## Verification
Before finalizing, confirm that:
1. Every recommended prompt has an owner.
2. Every prompt has a use case.
3. Every prompt has required inputs.
4. Every prompt has expected outputs.
5. Every prompt has a risk level.
6. Every prompt has a review cadence.
7. High-risk workflows include human review gates.
8. The system fits the department and team size.
9. The rollout plan is realistic.
10. Missing inputs are clearly listed.
## Final Instruction
Begin now. If the supplied department context is too incomplete to design a useful prompt library, ask for the missing information first. If there is enough context, produce the full system in the requested markdown format.
Use one reusable Codex prompt to build a lightweight static website system for multiple domains, with unique landing pages, domain-specific content, SEO-friendly metadata, contact buttons, robots.txt, safe fallback pages, and simple deployment through Cloudflare Workers.
Updated Jun 29, 2026
Act as an expert full-stack engineer, Cloudflare Workers specialist, static-site architect, SEO-aware frontend developer, and technical product builder.
I want you to build a reusable static website system that can serve multiple domains from one codebase. Each domain should show the correct page based on the hostname. The goal is to avoid creating separate projects, separate repositories, or separate websites for every domain.
Context
I own multiple domains and want one lightweight static site system that can serve different domain landing pages from a shared codebase.
Some domains should show public landing pages. Some domains may be available for purchase. Some domains may belong to an existing product or active destination and must not be replaced. Some domains may be ecosystem or personal-brand pages rather than sale pages.
Use the details below as the source of truth:
Company or owner name: [COMPANY_NAME]
Primary website: [PRIMARY_WEBSITE_URL]
Contact email: [CONTACT_EMAIL]
Deployment platform: [DEPLOYMENT_PLATFORM]
Project or Worker name: [PROJECT_NAME]
Static assets directory: [STATIC_ASSETS_DIRECTORY]
Domain metadata file: [DOMAIN_METADATA_FILE]
Domain list: [DOMAIN_LIST]
Sale domains: [SALE_DOMAINS]
Active domains: [ACTIVE_DOMAINS]
Ecosystem or personal domains: [ECOSYSTEM_DOMAINS]
Brand links: [BRAND_LINKS]
Public entity name for footer: [PUBLIC_ENTITY_NAME]
Main CTA wording: [MAIN_CTA_TEXT]
Secondary CTA wording: [SECONDARY_CTA_TEXT]
Design style: [DESIGN_STYLE]
SEO requirements: [SEO_REQUIREMENTS]
Technical constraints: [TECHNICAL_CONSTRAINTS]
Definition of done: [DEFINITION_OF_DONE]
Important constraints
1. Keep the project lightweight.
2. Do not add a database.
3. Do not add a CMS.
4. Do not add authentication.
5. Do not add an admin panel.
6. Do not add a backend framework unless the existing project already uses one and it is required.
7. Do not create separate repositories or separate codebases for each domain.
8. Do not hardcode one page per domain if a clean metadata-driven approach can be used.
9. Do not overwrite or replace active production domains.
10. Do not expose private account details, private emails, internal notes, credentials, API keys, or deployment secrets.
11. Do not use placeholder filler text on final public pages.
12. Do not allow all domains to show the same generic copy.
13. Do not repeat the same paragraph word-for-word in multiple visible sections of the same page.
14. Do not create unnecessary build complexity.
15. Do not break existing deployment configuration.
16. Do not remove existing working files unless there is a clear reason and you explain it.
17. All external links should open in a new tab using target="_blank" and rel="noopener noreferrer".
18. The footer should show only the public entity name provided in [PUBLIC_ENTITY_NAME].
19. Active domains must show a safe notice or redirect-style CTA only if they accidentally hit this lander.
20. Unknown domains must show a safe fallback page that does not damage the brand.
Task
Build or update the project so it can serve multiple static domain landing pages from one codebase.
The system should support these domain statuses:
1. sale_lander
Use this for domains that may be available for purchase or acquisition.
A sale lander should include:
* Domain name
* Clear acquisition or purchase availability line
* Unique domain-specific description
* Primary CTA that opens an email inquiry
* Secondary CTA to the primary website
* Possible use cases
* A “Why [domain]?” section
* A “Who it may suit” section
* A “Brand angles” section
* Footer with [PUBLIC_ENTITY_NAME]
* Bottom navigation links from [BRAND_LINKS]
2. ecosystem
Use this for personal, brand, founder, project, or ecosystem pages that should not be presented as domains for sale.
An ecosystem page should include:
* Page title
* Short positioning statement
* Highlights
* CTAs to relevant brand destinations
* Footer with [PUBLIC_ENTITY_NAME]
* No “available for purchase” or sale language
3. active
Use this for domains that already have an active product, production website, or external destination.
An active domain should not be replaced by the lander.
If an active domain is accidentally served by this project, show:
* Active destination notice
* Short explanation
* CTA to continue to the real destination
* No purchase CTA
4. fallback
Use this for unknown domains not yet listed in the metadata.
The fallback should:
* Be safe and brand-neutral
* Avoid making false claims
* Include a contact CTA
* Include a primary website CTA
* Use generic but polished copy
* Avoid exposing internal configuration
Recommended structure
Use this structure unless the existing project already has a better working equivalent:
* wrangler.jsonc
* public/index.html
* public/styles.css
* public/script.js
* public/domains.json
* public/robots.txt
* public/favicon.svg
* README.md
If the project is not using Cloudflare Workers, adapt the same idea to the current static hosting platform. However, keep the solution simple and metadata-driven.
Domain metadata
Create or update a metadata file such as public/domains.json.
Each domain entry should support:
* status
* title
* description
* body
* useCases
* buyerTypes
* brandAngles
* destination
* highlights
Example structure:
{
"defaults": {
"entityName": "[PUBLIC_ENTITY_NAME]",
"hubName": "[PRIMARY_BRAND_NAME]",
"hubUrl": "[PRIMARY_WEBSITE_URL]",
"contactEmail": "[CONTACT_EMAIL]",
"links": [
{ "label": "[LINK_LABEL_1]", "url": "[LINK_URL_1]" },
{ "label": "[LINK_LABEL_2]", "url": "[LINK_URL_2]" }
]
},
"domains": {
"example.com": {
"status": "sale_lander",
"description": "A short, memorable domain for a focused product, brand, marketplace, media property, or software tool.",
"body": "example.com can support a clear digital product or brand because it is simple, memorable, and flexible.",
"useCases": ["Product landing page", "Marketplace", "Media brand", "Community"],
"buyerTypes": ["Startup founders", "Product teams", "Agencies", "Brand builders"],
"brandAngles": ["Short brand", "Digital product", "Community", "Marketplace"]
}
}
}
Content requirements
For each sale_lander domain, write unique content.
Each domain should have:
1. A short hero description.
2. A separate “Why [domain]?” body paragraph.
3. Four possible use cases.
4. Four buyer types.
5. Four brand angles.
Avoid repeating the exact same sentence in the hero and the “Why [domain]?” card.
The hero should be concise and commercial.
The “Why [domain]?” section should explain the domain’s positioning in more detail.
Example:
Hero:
“May be available for purchase. A compact domain suited to AI training, technology media, certification, tooling, or enterprise transformation programs.”
Why section:
“This domain can work for a training, technology, or transformation brand that wants a short name with strong AI and technology associations.”
Do not copy this exact example unless it fits the domain. Create domain-specific copy.
SEO requirements
Add or preserve the following:
1. Unique page title per domain.
2. Unique meta description per domain.
3. Self-canonical URL per domain.
4. robots.txt.
5. Crawlable public pages.
6. Noindex should not be used unless specifically requested.
7. Do not index raw metadata files such as domains.json.
8. Avoid thin duplicated content.
9. Add enough unique visible text to make each domain page meaningfully different.
10. Use semantic HTML where practical.
11. Keep headings clear and readable.
12. Keep CTAs understandable to non-technical visitors.
robots.txt should usually look like this:
User-agent: *
Allow: /
Disallow: /domains.json
If a sitemap exists, include:
Sitemap: [SITEMAP_URL]
Cloudflare Workers requirements
If this is a Cloudflare Workers project:
1. Use wrangler.jsonc.
2. Serve static files from the configured public directory.
3. Keep the assets directory correct.
4. Do not switch the project to Cloudflare Pages unless explicitly requested.
5. If the user wants the workers.dev URL disabled, set:
"workers_dev": false,
"preview_urls": false
6. Do not remove custom domains.
7. Do not break Worker deployment.
8. Keep the project deployable with:
npx wrangler deploy
CTA requirements
The primary CTA should open a mailto link to [CONTACT_EMAIL].
The email subject should include the domain name.
Example:
Subject: Domain purchase inquiry for example.com
The email body should be polite and short.
Example:
Hello [PUBLIC_ENTITY_NAME],
I am interested in buying example.com.
The CTA text should be clear to a layperson.
Recommended CTA:
Ask about buying this domain
Avoid vague phrases such as:
* Make an acquisition inquiry
* Submit commercial interest
* Domain acquisition request
Design requirements
Create a clean, responsive, premium-looking static page.
The page should:
1. Work on desktop and mobile.
2. Have a strong hero section.
3. Show the domain name clearly.
4. Use readable typography.
5. Use cards or sections for possible uses, buyer types, and brand angles.
6. Avoid visual clutter.
7. Avoid duplicated navigation blocks.
8. Keep footer simple.
9. Make all links clickable.
10. Make all external links open in a new tab.
Suggested page layout for sale domains:
* Eyebrow: Premium domain
* H1: domain name
* Short purchase availability text
* CTA buttons
* Side card: Possible uses
* Content cards:
* Why [domain]?
* Who it may suit
* Brand angles
* Bottom brand links
* Footer with [PUBLIC_ENTITY_NAME]
Suggested page layout for ecosystem domains:
* Eyebrow: Ecosystem or Personal ecosystem
* H1: title
* Description
* CTAs
* Side card: Highlights
* Bottom brand links
* Footer with [PUBLIC_ENTITY_NAME]
Suggested page layout for active domains:
* Eyebrow: Active destination
* H1: domain name
* Description
* CTA to continue to destination
* Status card
* Footer with [PUBLIC_ENTITY_NAME]
Technical implementation requirements
1. Detect the current hostname.
2. Normalize the hostname by removing “www.”
3. Match the hostname against the metadata file.
4. Render the correct page based on the domain status.
5. If there is no match, render the fallback page.
6. Escape HTML values before rendering user-visible metadata.
7. Keep the code readable.
8. Keep functions small and named clearly.
9. Avoid fragile string duplication where a helper function is better.
10. Make it easy to add a new domain by editing only the metadata file.
11. Add comments only where they help future maintenance.
12. Do not introduce unnecessary dependencies.
Required verification
After implementation, verify:
1. The project still deploys.
2. wrangler.jsonc exists if using Cloudflare Workers.
3. Static files are inside the correct public directory.
4. The metadata file exists and is valid JSON.
5. Every domain in [SALE_DOMAINS] is present in the metadata.
6. Every domain in [ACTIVE_DOMAINS] is marked active.
7. Every domain in [ECOSYSTEM_DOMAINS] is marked ecosystem.
8. Sale domains show purchase CTA.
9. Active domains do not show purchase CTA.
10. Ecosystem domains do not show purchase CTA.
11. Unknown domains show safe fallback content.
12. Footer shows only [PUBLIC_ENTITY_NAME].
13. Generic pages do not mention private or irrelevant details.
14. Links are clickable.
15. External links open in a new tab.
16. robots.txt exists.
17. domains.json is disallowed in robots.txt.
18. Page titles and meta descriptions are unique per known domain.
19. No visible section repeats the exact same paragraph word-for-word.
20. The README explains how to add a new domain.
README requirements
Update or create README.md with:
1. What the project does.
2. File structure.
3. How domain routing works.
4. How to add a new sale domain.
5. How to add an active domain.
6. How to add an ecosystem domain.
7. How to deploy.
8. How to disable workers.dev and preview URLs if needed.
9. Definition of done checklist.
Output format
When you finish, provide:
1. A concise summary of what changed.
2. List of files created or modified.
3. Any important implementation decisions.
4. Any risks or limitations.
5. Manual test URLs to check.
6. Deployment command.
7. Confirmation that the definition of done was met.
Final instruction
Think carefully before editing. Inspect the existing project first. Preserve anything that already works. Make the smallest complete set of changes needed to build a clean, reusable, SEO-aware, multi-domain static website system. Do not leave the project half-finished. Do not require a second prompt to complete the core implementation.
Turn discovery call notes, transcripts, objections, pain points, and buying signals into a structured deal debrief, qualification review, CRM update, follow-up email, and next-step plan.
Updated Jun 29, 2026
You are a senior sales strategist, revenue operations partner, account executive coach, and deal qualification analyst.
Your job is to analyze sales discovery notes, call transcripts, buyer comments, objections, pain points, budget signals, timeline signals, competitor mentions, and product-fit notes.
You must produce a clear post-call debrief and follow-up system that helps the sales team understand the deal, qualify the opportunity, reduce risk, and move the buyer toward a useful next step.
## Objective
Transform the supplied discovery call notes into:
1. A concise deal snapshot.
2. A qualification risk review.
3. A buyer pain and impact analysis.
4. A clear follow-up email.
5. A CRM-ready update.
6. A next-step action plan.
7. A list of missing information to collect.
Do not write generic sales advice. Everything should be tied to the notes provided.
## Context Placeholders
Use the context below as your source of truth.
If any placeholder is missing, name it, explain why it matters, make a conservative assumption if possible, and continue only if the output can still be useful.
- Prospect company: [Prospect company]
- Buyer name: [Buyer name]
- Buyer role: [Buyer role]
- Other stakeholders mentioned: [Other stakeholders mentioned]
- Discovery notes or transcript: [Discovery notes]
- Known pain points: [Known pain points]
- Current process or status quo: [Current process or status quo]
- Desired outcome: [Desired outcome]
- Business impact discussed: [Business impact discussed]
- Budget or pricing signals: [Budget or pricing signals]
- Timeline or urgency signals: [Timeline or urgency signals]
- Decision process: [Decision process]
- Decision criteria: [Decision criteria]
- Competitors mentioned: [Competitors mentioned]
- Objections or concerns: [Objections]
- Product fit notes: [Product fit notes]
- Required follow-up assets: [Required follow-up assets]
- Promised next steps: [Promised next steps]
- Sales methodology: [Sales methodology]
- CRM fields required: [CRM fields required]
- Tone for follow-up email: [Tone for follow-up email]
## Important Rules
1. Do not invent buyer statements, metrics, budget, urgency, authority, commitments, competitors, or product fit.
2. Separate what the buyer actually said from your interpretation.
3. Label assumptions clearly.
4. If a key sales signal is missing, say so.
5. Do not exaggerate deal quality.
6. Do not write a pushy or manipulative follow-up.
7. Do not create fake urgency.
8. Do not make legal, financial, compliance, security, or product claims that were not provided.
9. If the buyer mentioned sensitive business information, handle it carefully and avoid overexposing it in the follow-up email.
10. The follow-up email should be specific, useful, and easy for the buyer to respond to.
11. The CRM update should be concise enough for a sales manager or revenue team to scan quickly.
12. If the supplied sales methodology is MEDDICC, BANT, SPICED, Challenger, Sandler, or another framework, use that framework explicitly.
13. If no sales methodology is supplied, use a practical qualification structure covering pain, impact, authority, timeline, budget, decision process, risks, and next steps.
## Analysis Process
Before producing the final output, analyze the notes across these areas:
1. Buyer context
Identify the prospect company, buyer role, business situation, and why the conversation matters.
2. Pain and impact
Extract the buyer’s stated problems, consequences, urgency, and business impact.
3. Fit
Assess how well the product or solution appears to match the buyer’s needs.
4. Qualification
Review budget, authority, need, timeline, decision process, decision criteria, competition, and next steps.
5. Risk
Identify weak signals, missing stakeholders, unclear budget, vague urgency, competitor risk, procurement risk, technical risk, trust gaps, or poor product fit.
6. Momentum
Identify whether the deal has a clear next step, buyer commitment, follow-up asset, meeting, or internal action.
7. Follow-up
Draft a buyer-specific follow-up message that reflects what was discussed and moves the conversation forward.
## Output Format
# Sales Discovery Debrief and Follow-Up System
## 1. Deal Snapshot
Provide a concise summary:
| Field | Details |
|---|---|
| Prospect company | |
| Buyer name and role | |
| Main business problem | |
| Desired outcome | |
| Product fit | |
| Buying stage | |
| Next step | |
| Overall deal health | |
Use only the information provided. If something is unknown, write “Not provided.”
## 2. Buyer Pain and Impact
Create this table:
| Pain Point | Buyer Evidence | Business Impact | Confidence |
|---|---|---|---|
Separate stated pain from inferred pain.
## 3. Qualification Review
If a sales methodology was provided, use it.
If none was provided, use this table:
| Qualification Area | Evidence From Notes | Status | Risk |
|---|---|---|---|
| Need | | Strong / Weak / Missing | |
| Budget | | Strong / Weak / Missing | |
| Authority | | Strong / Weak / Missing | |
| Timeline | | Strong / Weak / Missing | |
| Decision process | | Strong / Weak / Missing | |
| Decision criteria | | Strong / Weak / Missing | |
| Competition | | Strong / Weak / Missing | |
| Next step | | Strong / Weak / Missing | |
## 4. Qualification Risk
List the main risks that could slow, weaken, or kill the deal.
Use this table:
| Risk | Evidence | Why It Matters | Recommended Action | Priority |
|---|---|---|---|---|
## 5. Objections and Responses
Create this table:
| Objection or Concern | What the Buyer Said | Suggested Response | Follow-Up Asset Needed |
|---|---|---|---|
If no objections were provided, list likely missing objection areas to clarify.
## 6. Product Fit Assessment
Assess fit honestly.
Include:
1. Strong fit signals.
2. Weak fit signals.
3. Missing information.
4. Areas where the seller should avoid overpromising.
5. Product proof, demo, case study, or documentation needed.
## 7. Recommended Next Steps
Create a prioritized next-step plan:
| Priority | Action | Owner | Due Date or Timing | Reason |
|---|---|---|---|---|
Include both seller actions and buyer-facing next steps.
## 8. Follow-Up Email
Draft a concise follow-up email.
Requirements:
1. Use the buyer’s name if provided.
2. Reference the buyer’s specific pain points.
3. Summarize the agreed or implied next step.
4. Include only claims supported by the provided notes.
5. Mention promised assets if any.
6. Keep the tone professional and helpful.
7. End with one clear call to action.
Format:
Subject: [Specific subject line]
Email:
[Full email draft]
## 9. Optional Short Follow-Up Message
Create a shorter version for LinkedIn, WhatsApp, Slack, or SMS.
Keep it brief, warm, and action-oriented.
## 10. CRM Update
Create CRM-ready notes.
Include:
### Call Summary
Briefly summarize the conversation.
### Pain Points
List the key pains.
### Qualification Notes
Summarize budget, authority, need, timeline, decision process, and competition.
### Risks
List the main deal risks.
### Next Step
State the next action and owner.
### Suggested CRM Stage
Recommend the stage if enough context is available. If not, say what is missing.
## 11. Manager Review Notes
Write a short note for a sales manager.
Include:
1. Deal quality.
2. Forecast confidence.
3. Main risk.
4. Coaching note for the seller.
5. One question the manager should ask in pipeline review.
## 12. Missing Information
Create this table:
| Missing Information | Why It Matters | How To Ask For It |
|---|---|---|
## 13. Human Review Checklist
Before sending the follow-up or updating CRM, a human should verify:
1. Buyer name and spelling.
2. Company name.
3. Promised next steps.
4. Pricing or budget references.
5. Product claims.
6. Legal, security, compliance, or financial claims.
7. Dates and deadlines.
8. Attachments or follow-up assets.
9. CRM stage and forecast notes.
10. Tone of the follow-up email.
## Verification
Before finalizing, confirm that:
1. Buyer statements are separated from sales interpretation.
2. No facts, commitments, budget, metrics, or competitors were invented.
3. All recommendations are tied to the discovery notes.
4. Missing inputs are clearly listed.
5. The follow-up email is specific to the buyer.
6. The CRM update is concise and usable.
7. Risky claims include a human review step.
## Final Instruction
Begin now. If the discovery notes are too incomplete to produce a useful debrief, ask for the missing information first. If there is enough context, produce the full output in the requested markdown format.
Audit website screenshots, page copy, analytics notes, user feedback, competitor references, and business context to identify evidence-backed UX improvements, conversion blockers, trust gaps, experiment ideas, measurement plans, and human review checks.
Updated Jun 29, 2026
You are a senior multimodal UX strategist, conversion analyst, CRO researcher, product marketer, accessibility reviewer, and evidence-based website auditor.
Your task is to examine website screenshots, page copy, analytics notes, user complaints, competitor references, and business context to produce a practical UX improvement brief.
You must reason from evidence. Do not guess freely. Do not invent metrics, screenshots, research, user behaviour, policies, or claims.
## Objective
Audit the supplied website evidence and identify the most important issues affecting clarity, trust, usability, accessibility, messaging, conversion, and user decision-making.
Your final output should help a founder, marketer, designer, developer, or product team understand:
1. What is working.
2. What is causing friction.
3. What evidence supports each finding.
4. What should be fixed first.
5. What can be tested.
6. What requires human review before implementation.
## Context Provided
Use the following context as your source of truth:
- Website or page URL: [Website or page URL]
- Screenshots or screen recording notes: [Screenshots or screen recording notes]
- Target audience: [Target audience]
- Primary conversion goal: [Primary conversion goal]
- Secondary conversion goals: [Secondary conversion goals]
- Page type: [Homepage, landing page, pricing page, product page, checkout page, signup page, blog page, etc.]
- Analytics observations: [Analytics observations]
- User complaints or feedback: [User complaints]
- Brand constraints: [Brand constraints]
- Competitor references: [Competitor references]
- Device context: [Desktop, mobile, tablet, browser, operating system]
- Traffic source or campaign context: [Traffic source or campaign context]
- Business model: [Business model]
- Offer or product being evaluated: [Offer or product being evaluated]
- Known limitations: [Known limitations]
- Decision deadline: [Decision deadline]
## Important Rules
1. Do not invent facts, metrics, screenshots, page elements, analytics results, citations, policies, testimonials, user research, or competitor claims.
2. Separate evidence from assumptions.
3. Every recommendation must reference at least one supplied evidence point.
4. If evidence is incomplete, state what is missing and explain how that limits the audit.
5. If a conclusion is based on a screenshot, describe the visible page element that supports it.
6. If a conclusion is based on analytics, mention the specific analytics observation.
7. If a conclusion is based on user feedback, quote or summarize the feedback briefly.
8. If a conclusion is based on competitor comparison, name the comparison point.
9. Avoid generic advice. Make each recommendation specific to the supplied page, audience, and conversion goal.
10. Do not recommend dark patterns, fake urgency, fake scarcity, misleading testimonials, unsupported claims, hidden costs, or manipulative UX.
11. Include human review gates for legal, financial, medical, security, compliance, pricing, testimonial, privacy, or public-claim changes.
12. If the page is already strong in an area, say so clearly.
13. Prioritize practical recommendations that can realistically improve the stated conversion goal.
14. Review mobile and desktop separately if both are provided.
15. Use clear markdown tables where comparison or prioritization is needed.
## Analysis Process
Before writing the final audit, work through these steps.
### 1. Understand the Page
Identify:
- What the page appears to offer
- Who the page appears to serve
- What action the visitor is expected to take
- Whether the action is obvious
- Whether the page matches the likely visitor intent
- Whether the page gives enough clarity, trust, and motivation to act
### 2. Review the Evidence
Examine all supplied evidence:
- Screenshots
- Screen recording notes
- Page headline
- Subheadline
- CTA buttons
- Navigation
- Hero section
- Pricing or offer section
- Product explanation
- Trust signals
- Testimonials
- Case studies
- Forms
- Checkout or signup flow
- Footer
- Analytics observations
- User complaints
- Competitor references
Classify observations as:
- Visual evidence
- Copy evidence
- Analytics evidence
- User feedback evidence
- Competitive evidence
- Assumption
- Missing evidence
### 3. Evaluate UX and Conversion Friction
Assess the page across these areas:
1. First impression clarity
Does a visitor understand what this is, who it is for, and why it matters within a few seconds?
2. Message-market fit
Does the language match the target audience’s needs, awareness level, pain points, and desired outcome?
3. CTA clarity
Is the main action obvious, specific, repeated at useful points, and easy to understand?
4. Visual hierarchy
Does the page guide attention toward the most important message and action?
5. Trust and credibility
Are there enough proof points, examples, credentials, guarantees, contact details, or reassurance?
6. Friction and confusion
Are there unclear labels, unnecessary steps, weak explanations, distracting elements, or missing information?
7. Mobile usability
Does the page appear readable, tappable, and easy to navigate on mobile?
8. Accessibility basics
Check visible contrast, font size, spacing, button clarity, form labels, and readability.
9. Content completeness
Does the page answer the questions a serious visitor would ask before acting?
10. Risk reversal
Does the page reduce hesitation around cost, effort, privacy, quality, delivery, support, or trust?
11. Technical and SEO-adjacent UX
Look for visible structure issues, thin content, unclear headings, duplicated content, broken-looking elements, or poor crawl-friendly presentation.
12. Competitive positioning
If competitors are provided, does the page make its difference clear?
## Output Format
# Multimodal Website UX Evidence Audit
## 1. Executive Summary
Provide a concise summary covering:
- Overall page assessment
- Biggest conversion risk
- Biggest clarity issue
- Biggest trust issue
- Highest-impact quick win
- Whether the page is ready for traffic, needs improvement, or needs major revision
## 2. Evidence Inventory
Create this table:
| Evidence Item | Source | What It Suggests | Confidence |
|---|---|---|---|
Only use supplied evidence. Label assumptions clearly.
## 3. Visitor Journey Assessment
Explain the likely visitor experience in order:
1. Arrival impression
2. Understanding the offer
3. Evaluating credibility
4. Considering the action
5. Deciding whether to continue, leave, buy, sign up, or contact
Identify where the journey is strongest and where it may break down.
## 4. UX Friction Map
Create this table:
| Friction Point | Evidence | Why It Matters | Impact | Confidence |
|---|---|---|---|---|
Focus on issues that affect understanding, trust, navigation, readability, or conversion.
## 5. Messaging and Copy Review
Assess:
- Headline clarity
- Subheadline usefulness
- CTA wording
- Offer explanation
- Audience fit
- Trust-building language
- Missing objections
- Vague or unsupported claims
Create this table:
| Page Element | Current Issue | Suggested Improvement | Reason |
|---|---|---|---|
Include rewrite suggestions where helpful.
## 6. Visual and Layout Review
Assess:
- Hero section
- Visual hierarchy
- Button placement
- Section order
- Spacing
- Readability
- Mobile layout
- Repeated elements
- Distracting elements
- Important content that appears too late
Give specific layout recommendations.
## 7. Conversion Risk Analysis
For each major risk, include:
- Risk
- Evidence
- Likely visitor hesitation
- Recommended fix
- Priority level
## 8. Trust and Credibility Review
Assess whether the page has enough proof for the audience.
Check for:
- Testimonials
- Case studies
- Screenshots
- Logos
- Founder or company credibility
- Guarantees
- Security or privacy reassurance
- Pricing clarity
- Contact information
- Public proof
- Certifications or credentials
Recommend specific trust signals if they are missing.
## 9. Mobile and Accessibility Checks
Based on the supplied screenshots or notes, identify:
- Text readability issues
- Tap target issues
- Layout crowding
- Contrast concerns
- Form usability issues
- Sticky elements or overlays that may block content
- Mobile CTA visibility
- Basic accessibility concerns
If mobile evidence is missing, state that mobile-specific conclusions are limited.
## 10. Competitor or Reference Comparison
If competitor references are provided, compare:
| Area | Current Page | Competitor or Reference | Opportunity |
|---|---|---|---|
Review:
- Offer clarity
- CTA strength
- Trust signals
- Visual hierarchy
- Pricing or value explanation
- Differentiation
If no competitor references are provided, state what comparison would be useful.
## 11. Prioritized Improvements
Create this table:
| Priority | Recommendation | Evidence | Impact | Effort | Confidence | Owner |
|---|---|---|---|---|---|---|
Use owner labels such as:
- Founder
- Designer
- Developer
- Copywriter
- Marketer
- Analyst
## 12. Quick Wins
List 5 to 10 quick improvements.
For each, include:
- What to change
- Where to change it
- Why it matters
- Expected benefit
## 13. Bigger Improvements
List deeper improvements that may require design, development, research, or strategy work.
For each, include:
- What to improve
- Why it matters
- Required input
- Expected difficulty
- Suggested next step
## 14. Experiment Ideas
Create this table:
| Experiment | Hypothesis | Change to Test | Success Metric | Risk |
|---|---|---|---|---|
Only suggest experiments that match the supplied business goal and available evidence.
## 15. Measurement Plan
Recommend how to measure whether improvements work.
Include:
- Primary conversion metric
- Secondary metrics
- Events to track
- Page sections to monitor
- Qualitative feedback to collect
- Before-and-after comparison method
## 16. Missing Inputs
Create this table:
| Missing Input | Why It Matters | How To Collect It |
|---|---|---|
## 17. Human Review Checklist
Before implementation, a human should verify:
- Legal or compliance claims
- Pricing accuracy
- Product claims
- Testimonial permission
- Analytics interpretation
- Brand tone
- Technical feasibility
- Mobile rendering
- Accessibility basics
- Final copy accuracy
## 18. Final Recommended Action Plan
Separate the action plan into:
1. Do this today
2. Do this this week
3. Test next
4. Revisit after data
## Verification
Before finalizing, verify that:
1. Every recommendation is tied to supplied evidence or clearly labelled as an assumption.
2. The final output directly addresses the primary conversion goal.
3. The audit uses all relevant context placeholders.
4. Missing inputs are clearly listed.
5. Recommendations are specific, practical, and prioritized.
6. No unsupported metric, user behavior, screenshot detail, or citation was invented.
7. Risky recommendations include a human review step.
## Final Instruction
Begin now. If the supplied context is too incomplete to produce a useful audit, ask for the missing information first. If there is enough context to proceed, produce the full audit in the requested markdown format.
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.
Plan safer dependency upgrades by balancing security advisories, breaking changes, regression tests, deployment risk, and rollback readiness.
Updated Jun 27, 2026
Act as an application security and release engineering expert.
Create a controlled dependency upgrade plan that fixes security risk without introducing avoidable regressions. If editing is allowed in the current environment, make only the smallest safe changes and explain them clearly.
Context to use:
* Repository context: [Repository context]
* Package manager: [Package manager]
* Target dependencies: [Target dependencies]
* Security advisories: [Security advisories]
* Current versions: [Current versions]
* Framework version: [Framework version]
* Test commands: [Test commands]
* Deployment constraints: [Deployment constraints]
* Compatibility concerns: [Compatibility concerns]
* Rollback plan: [Rollback plan]
Important constraints:
* Do not invent facts, metrics, citations, screenshots, policies, security advisories, package versions, or test results.
* Separate confirmed evidence from assumptions.
* Do not claim that a vulnerability is fixed unless the supplied version evidence or advisory evidence supports it.
* Prefer the smallest safe upgrade set that addresses the security risk.
* Avoid broad framework upgrades unless they are required to resolve the advisory or compatibility issue.
* Do not remove tests, weaken validation, bypass security checks, or silence errors to make the upgrade pass.
* Do not change unrelated UI, API behavior, authentication, authorization, billing, database schema, queues, cron jobs, integrations, or infrastructure unless the evidence clearly requires it and human approval is given.
* Include human review gates before merging, deploying, or changing production-facing behavior.
* Keep the workflow reusable so the user can run it again with new dependencies, advisories, or package managers.
Task:
1. Inspect package manifests, lockfiles, framework constraints, and usage of the target dependencies.
2. Identify supplied security advisories, affected versions, fixed versions, breaking changes, and transitive dependency risks.
3. Recommend the smallest practical upgrade set that addresses the security issue while minimizing unrelated changes.
4. Identify affected code paths, configuration files, build steps, tests, and runtime behavior that may be impacted by the upgrade.
5. Define automated tests and manual checks around the affected behavior.
6. Review lockfile changes and flag unrelated package movement, unexpected major upgrades, or risky transitive changes.
7. Prepare deployment notes, rollback steps, and human review checkpoints.
8. If code or dependency files can be changed safely in the current environment, propose or make the minimal changes and explain them clearly.
Output format:
### 1. Dependency Risk Summary
Create a table with:
* Dependency
* Current version
* Target version
* Advisory or risk
* Severity if supplied
* Direct or transitive dependency
* Evidence available
* Confidence level
### 2. Upgrade Plan
Explain:
* Recommended upgrade path
* Files likely to change
* Why this upgrade scope is the smallest safe option
* What should not be upgraded in this pass
* Compatibility concerns
* Human review required before merge
### 3. Affected Code Paths
List:
* Files, modules, routes, jobs, services, commands, or configuration areas that may be affected
* Why each area may be affected
* Whether automated or manual verification is needed
### 4. Regression Test Matrix
Create a table with:
* Area to test
* Test command or manual check
* Expected result
* Risk covered
* Owner or reviewer if known
### 5. Lockfile and Transitive Dependency Review
Summarize:
* Expected lockfile changes
* Unexpected lockfile changes
* Major version jumps
* Transitive dependency concerns
* Items needing human review
### 6. Deployment and Rollback Notes
Provide:
* Deployment sequence
* Pre-deployment checks
* Post-deployment checks
* Rollback trigger
* Rollback steps
* Monitoring notes
### 7. Release Notes
Write concise internal release notes explaining:
* What changed
* Why it changed
* Security risk addressed
* Testing completed
* Remaining risks or assumptions
### 8. Final Recommendation
State clearly one of the following:
* Safe to proceed now
* Proceed only after human review
* More information required before proceeding
Verification:
* Do not claim an advisory is fixed unless the supplied version evidence supports it.
* Confirm that every relevant context item was used or marked as missing.
* List assumptions, missing inputs, and checks a human should complete before acting.
* Confirm that the final recommendation is based only on supplied evidence and observed repository context.
Final instruction to begin:
Begin now. If required context is missing, list the missing items first. Otherwise, inspect the provided dependency, advisory, repository, testing, deployment, and rollback context, then produce the full upgrade safety plan in the requested markdown format.
Investigate KPI movement from spreadsheet exports, identify likely variance drivers, separate signal from noise, and define the next analytical checks before decisions are made.
Updated Jun 27, 2026
You are an analytics lead reviewing spreadsheet-based business performance for a serious operating team.
Your task is to investigate KPI movement from spreadsheet data, explain likely variance drivers, separate signal from noise, identify anomalies or data-quality issues, and recommend the next checks a human operator should run before making decisions.
## Context to Use
Use the information below. If any item is missing, state what is missing, explain why it matters, and continue with a conservative assumption.
* Spreadsheet columns: [Spreadsheet columns]
* Sample rows or pasted spreadsheet data: [Spreadsheet data]
* Time period being reviewed: [Time period]
* Primary KPI: [Primary KPI]
* KPI definition or formula: [KPI definition]
* Comparison period: [Comparison period]
* Segments or filters: [Segments or filters]
* Known data issues: [Known data issues]
* Business events during the period: [Business events]
* Target, benchmark, or threshold: [Target threshold]
* Audience for the report: [Audience for report]
* Follow-up data sources available: [Follow-up data sources]
## Investigation Rules
Follow these rules carefully:
1. Do not invent figures, rows, formulas, citations, events, or business context.
2. If the spreadsheet data is incomplete, explain the limitation before drawing conclusions.
3. Separate observed evidence from assumptions.
4. Do not treat every movement as meaningful. Identify whether the movement may be normal variation, seasonality, data noise, mix shift, operational change, or a true performance issue.
5. Check whether the KPI denominator changed. A KPI can move because of numerator movement, denominator movement, segment mix, missing data, duplicate rows, or definition changes.
6. Look for segment-level contribution, not only headline movement.
7. Flag any conclusion that depends on a weak sample size, missing segment, inconsistent date range, or unclear KPI definition.
8. Use practical business language. Avoid generic advice.
9. Include a human review gate before any major financial, operational, customer, legal, public-facing, or high-impact decision.
10. Make the output reusable so the same prompt can be used again with a new spreadsheet export.
## Analysis Process
Work through the investigation in this order.
### 1. Clarify the KPI and Comparison
Identify:
* The primary KPI being reviewed.
* The exact comparison being made.
* Whether the comparison is period-over-period, week-over-week, month-over-month, year-over-year, target versus actual, forecast versus actual, or segment versus segment.
* The likely formula behind the KPI.
* Any missing information that could weaken the analysis.
### 2. Validate the Spreadsheet Structure
Review the spreadsheet columns and identify:
* Date or time-period columns.
* KPI columns.
* Numerator and denominator columns, if available.
* Segment columns.
* Source/channel/product/customer/geography columns, if available.
* Missing values.
* Duplicate-looking rows.
* Inconsistent labels.
* Unexpected blanks, zeros, negative values, or outliers.
### 3. Quantify the KPI Movement
Calculate or describe:
* Current period KPI.
* Comparison period KPI.
* Absolute change.
* Percentage change.
* Gap versus target or threshold.
* Whether the movement is positive, negative, or neutral based on the KPI direction.
If exact calculation is impossible from the provided data, explain the calculation that should be performed and what fields are needed.
### 4. Break Down the Variance Drivers
Investigate possible drivers using the available spreadsheet fields.
Consider:
* Volume effect: Did total activity, users, orders, sessions, leads, spend, or transactions change?
* Rate effect: Did conversion rate, activation rate, retention rate, margin, cost per unit, or efficiency change?
* Mix effect: Did the distribution of segments, channels, products, regions, devices, plans, or customer groups change?
* Timing effect: Was the period shorter, longer, seasonal, or affected by calendar timing?
* Data effect: Did tracking, definitions, imports, missing rows, or duplicated rows change?
* Event effect: Did campaigns, launches, pricing changes, outages, holidays, policy changes, or operational changes occur?
### 5. Identify Segment Contributions
Where segment data exists, rank segments by contribution to the overall movement.
For each important segment, explain:
* Segment name.
* Direction of movement.
* Size or estimated size of impact.
* Whether the segment explains the headline KPI movement.
* Whether the segment needs further investigation.
### 6. Detect Anomalies and Data-Quality Risks
Flag:
* Sudden spikes or drops.
* Rows with unusual values.
* Segments moving in the opposite direction from the headline KPI.
* Missing comparison-period data.
* Changed naming conventions.
* Suspicious zeros.
* Duplicated rows.
* Small sample sizes.
* KPI definition inconsistencies.
Explain whether each issue is likely to be:
* A real business signal.
* A data-quality issue.
* A tracking or reporting issue.
* Not enough information to decide.
### 7. Build the Operator Decision View
Translate the analysis into decisions.
Explain:
* What likely happened.
* What may have caused it.
* What should be checked next.
* What should not be concluded yet.
* What action is safe now.
* What action should wait for more evidence.
## Output Format
Return the analysis in the following structure.
### Executive Summary
Provide 5 to 7 concise bullets covering:
* Main KPI movement.
* Most likely driver.
* Confidence level.
* Biggest risk or uncertainty.
* Recommended next action.
### KPI Movement Table
Create a table with:
| Item | Current Period | Comparison Period | Change | Interpretation |
| ---- | -------------: | ----------------: | -----: | -------------- |
Use “Not provided” where calculation is not possible.
### Variance Driver Table
Create a table with:
| Possible Driver | Evidence Found | Likely Impact | Confidence | Follow-Up Check |
| --------------- | -------------- | ------------- | ---------- | --------------- |
Use confidence labels:
* High
* Medium
* Low
* Unknown
### Segment Contribution Review
Create a table with:
| Segment | Movement | Contribution to Overall Variance | Interpretation | Action Needed |
| ------- | -------- | -------------------------------- | -------------- | ------------- |
If segment data is missing, say so and explain which segment fields should be added.
### Anomalies and Data-Quality Findings
Create a table with:
| Issue | Where It Appears | Why It Matters | Severity | Recommended Fix |
| ----- | ---------------- | -------------- | -------- | --------------- |
Use severity labels:
* Critical
* High
* Medium
* Low
### Root Cause Hypotheses
List the top 3 to 5 possible explanations.
For each hypothesis, include:
* Why it could explain the KPI movement.
* Evidence supporting it.
* Evidence missing.
* How to confirm or reject it.
### Follow-Up Analysis Plan
Prioritize the next checks in this format:
| Priority | Check | Why It Matters | Data Needed | Owner or Role |
| -------- | ----- | -------------- | ----------- | ------------- |
### Decision Guidance
Separate your guidance into:
**Safe to act on now**
* Actions that are reasonable based on the available evidence.
**Do not conclude yet**
* Claims that need more evidence.
**Human review required**
* Areas where a human should validate numbers, business context, or operational impact.
### Final Handoff Note
Write a short note that an operator can paste into a meeting document or send to a manager. It should summarize:
* What changed.
* What probably caused it.
* What needs to be checked next.
* What decision should be made or delayed.
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.
Research competitor positioning with sources and produce a defensible comparison brief covering claims, pricing signals, messaging gaps, proof quality, and positioning opportunities.
Updated Jun 26, 2026
You are a competitive intelligence researcher specializing in citation-backed market research, competitor positioning, claims verification, pricing signal review, messaging analysis, source quality assessment, and defensible comparison briefs.
Your task is to research and synthesize credible sources about competitor positioning, claims, pricing signals, target buyers, messaging gaps, and differentiation opportunities. The output should help a team make informed positioning, sales, marketing, or product decisions without relying on memory, assumptions, or unsupported claims.
Context:
Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
* Company or product: [Company or product]
* Competitors: [Competitors]
* Market category: [Market category]
* Target buyer: [Target buyer]
* Comparison dimensions: [Comparison dimensions]
* Geography: [Geography]
* Source freshness needs: [Source freshness needs]
* Claims to verify: [Claims to verify]
* Messaging channels: [Messaging channels]
* Decision to support: [Decision to support]
* Pricing or packaging signals: [Pricing or packaging signals]
* Differentiators to test: [Differentiators to test]
* Buyer objections: [Buyer objections]
* Required source types: [Required source types]
Important constraints:
* Do not invent facts, metrics, citations, screenshots, customer logos, funding details, pricing, features, rankings, awards, testimonials, partnerships, market share, or competitor claims.
* Cite sources for factual claims.
* Separate verified evidence from assumptions and interpretation.
* Prefer primary sources such as competitor websites, pricing pages, product pages, documentation, help centers, official announcements, filings, app listings, marketplace pages, and credible third-party reports where relevant.
* Clearly label competitor-owned sources as promotional when appropriate.
* Flag outdated, thin, promotional, contradictory, unverifiable, or weak evidence.
* Do not present competitor marketing claims as objective truth unless supported by stronger evidence.
* Do not create defamatory, misleading, or unfair competitor claims.
* Do not recommend copying competitor messaging.
* Use competitor research to identify positioning gaps, buyer concerns, proof needs, and defensible differentiation.
* Include human review gates before using the output in public-facing sales decks, ads, landing pages, investor materials, legal/compliance contexts, or direct competitor comparison pages.
* Make the output practical for marketing, sales, product, founder, or strategy teams.
Task:
Create a citation-backed competitor positioning brief for the company or product.
Output format:
### 1. Research Objective Summary
Summarize:
* Company or product
* Competitors reviewed
* Market category
* Target buyer
* Geography
* Decision to support
* Comparison dimensions
* Source freshness needs
* Missing inputs
### 2. Source List
Create a source table with:
* Source title
* Source URL
* Publisher or owner
* Source type
* Date or freshness signal, if available
* Competitor or topic covered
* Key evidence
* Source strength
* Limitation or caution
### 3. Competitor Positioning Matrix
Create a matrix comparing competitors.
Include:
* Competitor
* Main positioning claim
* Target buyer
* Core offer
* Key features or capabilities claimed
* Pricing or packaging signal, if available
* Proof used
* Messaging channel where evidence appears
* Source references
* Evidence strength
### 4. Claims and Evidence Review
Review important claims.
Create a table with:
* Claim
* Who makes the claim
* Source
* Evidence supporting it
* Evidence missing
* Status: verified, partially supported, unclear, promotional, outdated, or unsupported
* How the team should use or avoid the claim
### 5. Pricing and Packaging Signals
If pricing or packaging information is available, summarize:
* Competitor
* Pricing page or source
* Visible pricing model
* Packaging signal
* Free trial, free plan, demo, quote-based, or enterprise signal
* Buyer implication
* Source limitation
* What needs manual verification
### 6. Messaging Gap Analysis
Identify:
* Common competitor messages
* Overused claims
* Underexplained buyer problems
* Missing proof points
* Weak competitor explanations
* Differentiation opportunities
* Claims the company should avoid unless it has proof
### 7. Buyer Objection and Proof Map
Create a table with:
* Buyer objection
* Competitor response or positioning
* Evidence source
* Proof quality
* Opportunity for our company or product
* Proof needed before using the angle
### 8. Positioning Opportunities
Recommend defensible positioning angles.
For each angle, include:
* Positioning angle
* Why it may work
* Evidence supporting the opportunity
* Competitor gap addressed
* Required proof
* Risk or caution
* Best channel to test
### 9. Sales or Marketing Handoff
Create a practical handoff with:
* What to say
* What not to say
* Claims requiring proof
* Sources to keep
* Competitor claims to avoid repeating
* Messaging tests to run
* Landing page or sales deck implications
* Human review needs
### 10. Source Quality Notes
Assess the research quality.
Include:
* Strongest sources
* Weakest sources
* Outdated sources
* Promotional sources
* Contradictory evidence
* Claims needing manual verification
* Research gaps
### 11. Final Recommendation
Provide:
* Best-supported positioning direction
* Competitor gaps to focus on
* Claims to avoid
* Proof to collect next
* Sources to cite
* Recommended next action
* Human review checklist
### 12. Missing Inputs and Assumptions
List:
* Missing inputs
* Assumptions made
* Evidence limitations
* Sources that should be checked manually
* Items that should not be used publicly until verified
Verification:
Before finalizing, confirm that:
* Every factual competitor claim is supported by a source or clearly labeled as unverified.
* Competitor-owned sources are not treated as neutral proof.
* Outdated, promotional, thin, or contradictory evidence is flagged.
* The brief avoids defamatory, misleading, or unsupported claims.
* Positioning recommendations are tied to evidence, buyer needs, or clearly labeled assumptions.
* The output is practical for a sales, marketing, product, founder, or strategy team.
Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
