Expert prompt systems for professional work.

Act as a senior SEO strategist and information architect. Build a semantic topical map for [CORE TOPIC] for [AUDIENCE]. The site offers [SITE OFFER]. Existing relevant pages: [EXISTING PAGES]. First-party expertise or evidence we can contribute: [FIRST-PARTY EXPERTISE].

Start by defining the central reader problem, the decisions readers need to make, and the important entities, processes, attributes, alternatives, and risks connected to the topic. Group the coverage into a small number of coherent clusters. For every proposed page, provide its unique purpose, primary intent, audience stage, recommended format, essential questions, original evidence required, parent page, child pages, and natural internal-link relationships.

Identify pages that would overlap, compete, or add little value. Recommend which ideas to merge, exclude, or treat as sections instead of separate URLs. Finish with a prioritized publishing sequence that establishes a useful core before expanding the cluster. Do not invent keyword volume, ranking difficulty, trends, or live search results.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create an original-evidence content plan for [TOPIC] aimed at [AUDIENCE] and supporting [BUSINESS GOAL]. Available experience: [AVAILABLE EXPERIENCE]. Available data, examples, screenshots, interviews, or tests: [DATA OR EXAMPLES].

Separate what we know directly from what requires research. Propose five content assets that use our evidence to answer a meaningful reader question better than a generic summary could. For each asset, define the unique claim or lesson, the evidence needed, the practical deliverable for the reader, the best page format, the fact-checking requirements, and the internal pages that should support it.

Include a plan for obtaining missing first-party evidence through small tests, interviews, demonstrations, or analysis. Reject ideas that rely mainly on rewriting existing articles. Finish with a quality rubric covering originality, accuracy, completeness, transparency, usefulness, and maintenance.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Audit the following page about [PRIMARY TOPIC] for [TARGET READER]: [PAGE DRAFT]. Related site pages: [RELATED SITE PAGES]. Verified sources: [VERIFIED SOURCES].

Create a coverage table with the essential entities, concepts, processes, attributes, comparisons, risks, and reader questions. For each item, mark it as complete, partial, missing, unsupported, or better handled on another page. Explain why the item matters to the reader and where it belongs in the article.

Then identify vague language, repeated ideas, unexplained terminology, unsupported claims, forced keyword use, and sections that do not advance the reader's task. Recommend precise edits, useful internal links, and any tables, diagrams, examples, or checklists that would improve comprehension. Do not add concepts merely to increase word count.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a customer-insight analyst and marketing strategist. Turn [CUSTOMER EVIDENCE] into a campaign brief for [OFFER], aimed at [AUDIENCE], with the objective [CAMPAIGN GOAL] across [CHANNELS].

First code the evidence into recurring jobs, pains, desired outcomes, objections, triggers, decision criteria, and exact phrases. Show the evidence behind every theme and label weak or conflicting signals. Do not treat one memorable quote as a universal truth.

Build a concise brief containing the target situation, customer problem, value proposition, proof available, message hierarchy, objections to address, tone, channel adaptations, call to action, exclusions, and legal or factual claims requiring review. Finish with three campaign hypotheses and the smallest test that could validate each one.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a campaign message matrix for [OFFER] across [CHANNELS]. Audience segments: [AUDIENCE SEGMENTS]. Customer evidence: [CUSTOMER EVIDENCE]. Available proof: [PROOF].

For each segment, define the relevant situation, priority problem, desired outcome, main promise, supporting proof, likely objection, response, three hook angles, appropriate call to action, and claims that must not be made. Keep distinctions meaningful; do not create artificial segments that would receive the same message.

After the matrix, identify the strongest shared narrative and the differences that genuinely require separate creative. Propose a controlled test plan where one variable changes at a time, with a hypothesis and success signal for each test.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Review [CREATIVE] for [AUDIENCE], [OFFER], and [CHANNEL] against this campaign brief: [CAMPAIGN BRIEF].

Score and explain audience relevance, opening clarity, message hierarchy, value communication, credibility, evidence, differentiation, brand fit, platform-native execution, accessibility, call to action, and factual or legal risk. Quote only the smallest necessary fragment when identifying a problem.

Separate launch blockers, important improvements, and optional refinements. Rewrite only the weak parts, preserving what already works. Finish with a pre-launch checklist and three controlled variants that each test one clear hypothesis rather than changing everything at once.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a short-form video strategist. Build a hook matrix for [TOPIC OR OFFER] aimed at [AUDIENCE] on [PLATFORM], using only [EVIDENCE] and the brand voice [BRAND VOICE].

Create hooks across eight angles: immediate problem, surprising observation, useful mistake, demonstration, before-and-after process, open question, contrarian insight, and specific outcome. For each angle, provide two spoken openings, matching on-screen text, the visual action in the first shot, the promised payoff, and the proof required later in the video.

Reject deceptive curiosity gaps, unsupported guarantees, fake urgency, and hooks whose body cannot deliver the promise. Rank the best six hooks by relevance, credibility, visual potential, and ease of testing. Finish with a test matrix that changes only the opening while keeping the body and close stable.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create three short vertical-video scripts for [VIDEO GOAL], aimed at [AUDIENCE], communicating [KEY MESSAGE] with [PROOF]. Maximum length: [MAX LENGTH].

Each script must include: the first-frame visual, spoken hook, on-screen hook text, scene-by-scene body, demonstration or proof, captions, pattern changes, natural call to action, and an accessible version that still works with sound off. Make the three concepts structurally different rather than changing a few words.

Use a human, platform-native tone. Do not invent testimonials, performance figures, trends, or product capabilities. After the scripts, explain the hypothesis behind each concept, what must stay constant in an A/B test, and the retention or action signals to review.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as an art director and AI visual-production planner. Create a visual-content brief for [CAMPAIGN GOAL], [AUDIENCE], and [MESSAGE]. Brand rules: [BRAND RULES]. Required formats and placements: [FORMATS].

Define the communication objective, single focal idea, subject, environment, composition, camera perspective, lighting, color logic, texture, mood, brand cues, negative space, text-safe zones, accessibility needs, and elements to avoid. Provide a shot list with one hero concept and four useful variations.

Then produce a modular image-generation prompt template with clearly labeled variables rather than a tool-specific magic phrase. Add negative constraints, continuity rules for a series, human review questions, rights and likeness checks, factual-accuracy checks, and export requirements for every placement.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Critique [VISUAL OR DESCRIPTION] against [ORIGINAL BRIEF] for [AUDIENCE] in [PLACEMENT]. Brand rules: [BRAND RULES].

Evaluate first-glance message, focal hierarchy, composition, visual coherence, brand fit, platform fit, text-safe area, legibility, accessibility, realism, anatomy or object integrity, repeated patterns, unwanted artifacts, misleading implications, and rights or likeness risk.

Separate objective defects, brief mismatches, and subjective preferences. Prioritize the smallest changes with the largest impact. Return a revised generation or editing instruction that preserves successful elements, plus a final acceptance checklist for human approval.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Design a reusable prompt system for [RECURRING TASK], used by [USERS]. Typical inputs: [INPUTS]. Required output: [OUTPUT REQUIREMENTS]. Known failures: [KNOWN FAILURES].

Define the task contract: objective, user, source hierarchy, mandatory inputs, optional inputs, missing-information behavior, operating steps, decision rules, boundaries, output schema, examples, and acceptance criteria. Create the master prompt with clearly named variables and instructions that remain portable across ChatGPT, Claude, and Gemini.

Then create a five-case evaluation set covering normal use, incomplete input, conflicting evidence, an edge case, and an unsafe or out-of-scope request. Provide a scoring rubric, version label, change log template, owner, review trigger, and rollback rule. Do not optimize for one polished demonstration.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Design a governed prompt library for [TEAM] covering [USE CASES] across [TOOLS]. Risk levels: [RISK LEVELS]. Current prompts or storage: [CURRENT PROMPTS].

Define the record schema for each prompt: identifier, title, owner, purpose, intended users, model compatibility, required inputs, prompt text, examples, evaluation cases, limitations, approved data classes, status, version, last review, and change history. Propose roles and permissions for authors, reviewers, users, and administrators.

Create submission, test, approval, publication, monitoring, update, deprecation, and incident workflows. Include naming rules, duplicate detection, search tags, adoption metrics, failure reporting, and a 30-day pilot plan. Keep controls proportional to risk and avoid unnecessary bureaucracy.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create an evaluation suite for this prompt: [PROMPT]. Task: [TASK]. Definition of a good output: [GOOD OUTPUT]. Known failure modes: [FAILURE MODES]. Models or versions to compare: [MODELS].

Design at least twelve test cases covering typical inputs, missing context, noisy input, conflicting sources, boundary conditions, adversarial phrasing, format pressure, and out-of-scope requests. For each case, provide the input, expected behavior, prohibited behavior, critical assertions, and severity if it fails.

Build a scoring rubric for correctness, evidence use, instruction adherence, completeness, usefulness, uncertainty handling, safety, format, latency, and cost where available. Define pass thresholds, reviewer instructions, comparison rules, regression triggers, and how to document a prompt or model update.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Design a fair comparison of ChatGPT, Claude, and Gemini for [TASK]. Representative inputs: [REPRESENTATIVE INPUTS]. Constraints: [CONSTRAINTS]. Acceptance criteria: [ACCEPTANCE CRITERIA]. Verified cost and product data: [COST DATA].

Create an identical test harness: system instructions, task prompt, context, tools, permissions, output format, time limit, retry policy, and human-review process. Include easy, typical, difficult, incomplete, and edge-case tasks.

Define a weighted scorecard for acceptance rate, correctness, evidence handling, instruction following, consistency, editing time, latency, cost per accepted result, and severe-error risk. Explain how to handle nondeterminism and model updates. Finish with a decision table and routing policy, but do not recommend a winner until real results are supplied.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as an n8n solution architect. Design a production-minded workflow for [PROCESS] using [APPS AND APIS]. Input data: [INPUT DATA]. Allowed actions: [ALLOWED ACTIONS]. Risk level and approval requirements: [RISK LEVEL].

Return a node-by-node blueprint covering trigger, authentication, validation, normalization, deterministic routing, AI operation, prompt and context, structured output, confidence or validation checks, human approval, downstream action, persistence, notification, and completion. For every node, specify inputs, outputs, error path, retry behavior, idempotency need, and sensitive-data considerations.

Separate decisions that should be deterministic from judgments appropriate for AI. Add timeouts, rate-limit handling, cost controls, logging, test data, rollback, and a staged launch plan. Do not invent API fields or n8n node capabilities; mark documentation checks explicitly.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Perform a defensive failure-mode review of this n8n workflow: [WORKFLOW EXPORT OR DESCRIPTION]. Expected outcome: [EXPECTED OUTCOME]. Data classes: [DATA CLASSES]. External systems: [EXTERNAL SYSTEMS]. Current errors: [CURRENT ERRORS].

Trace the execution from trigger to final action. Identify invalid input, missing fields, item-linking or mapping mistakes, credential and permission issues, timeouts, rate limits, partial failures, duplicate execution, non-idempotent actions, model hallucination, malformed structured output, prompt injection exposure, unsafe tool calls, weak human approval, and silent data loss.

For each finding, state the evidence, likelihood, impact, detection signal, prevention, recovery, and test case. Prioritize launch blockers. Finish with an error-workflow design, observability checklist, retry and dead-letter policy, and a safe rollout sequence.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a defensive AI application security reviewer. Create a prompt-injection threat model for [AI APPLICATION]. Input sources: [INPUT SOURCES]. Data and secrets the system can access: [DATA AND SECRETS]. Connected tools and possible actions: [TOOLS AND ACTIONS]. User roles and permissions: [USER ROLES].

Draw the trust boundaries from each input source through retrieval, memory, model calls, output handling, tools, and final destinations. For every boundary, identify who controls the content, what the model can see, what action could follow, and the worst credible impact if untrusted text changes model behavior.

Create a risk register covering direct and indirect prompt injection, retrieved-content manipulation, memory contamination, tool-result injection, excessive permissions, cross-user data exposure, unsafe output rendering, unauthorized actions, and weak approval paths. For each risk, state prerequisites, affected asset, existing control, control gap, likelihood, impact, detection signal, owner, and defensive test.

Recommend layered controls: data minimization, source labeling, isolation, input screening, structured contracts, least-privilege tools, server-side authorization, parameter validation, output sanitization, human approval, monitoring, rate limits, incident response, and regression tests. Do not provide attack payloads or instructions for bypassing safeguards. State clearly which controls must be implemented outside the prompt.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Perform a defensive untrusted-context review for [WORKFLOW]. Untrusted content sources: [UNTRUSTED CONTENT SOURCES]. Intended model task: [MODEL TASK]. Available tools: [AVAILABLE TOOLS]. Output destinations: [OUTPUT DESTINATIONS].

Trace how each external source is fetched, parsed, stored, retrieved, labeled, placed in context, summarized, transformed, and passed to another model, tool, renderer, or person. Identify where content that should be treated as data could influence instructions, permissions, routing, tool parameters, or final output.

For each stage, assess source provenance, user authorization, data minimization, instruction-data separation, content isolation, schema validation, tool scope, destination allow-lists, output escaping, approval requirements, logging, privacy, and safe failure behavior. Mark controls as present, partial, missing, or not applicable and explain the evidence.

Produce a prioritized remediation plan and a regression suite covering normal content, conflicting sources, instruction-like external text, malformed input, unauthorized tool requests, unsafe rendered output, and persistent-context contamination. Do not generate bypass payloads. Treat prompt wording as one layer only and identify the application controls required for meaningful protection.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a senior SEO strategist, content architect, and subject-matter editor. Create a complete, evidence-led SEO content brief for the following page.

INPUTS
- Primary topic or query: [TARGET KEYWORD]
- Audience and level of knowledge: [AUDIENCE]
- Country, language, or market: [MARKET]
- Business objective and desired conversion: [BUSINESS GOAL]
- Product, service, or website context: [ADD CONTEXT]
- Existing pages that may overlap: [PASTE URLS OR TITLES]
- First-party evidence available: [CUSTOMER QUESTIONS, DATA, EXPERT NOTES]
- Verified SERP or competitor observations: [PASTE MANUAL RESEARCH OR WRITE NONE]

PHASE 1 — DIAGNOSIS
1. Restate the search problem in plain language.
2. Separate the likely primary intent, secondary intents, reader stage, and decision the visitor is trying to make.
3. Identify what must be manually validated in the live search results. Never pretend to have current SERP, ranking, traffic, or keyword-volume data.
4. Assess whether this should be a guide, comparison, landing page, glossary, tool, template, or another format. Explain the choice.
5. Define the page’s unique information gain: the original experience, data, framework, examples, tool, or point of view needed to make it better than a generic summary.

PHASE 2 — CONTENT SPECIFICATION
Return:
- Three accurate title-tag options with different angles
- A recommended H1 and concise meta description
- A one-sentence editorial promise
- A detailed H2/H3 outline in the order a reader needs it
- The purpose of every major section
- Questions each section must answer
- Entities, concepts, definitions, and comparisons to cover naturally
- Evidence required: first-party experience, expert input, examples, screenshots, data, sources, or demonstrations
- Claims that require verification or citation
- Recommended tables, checklists, diagrams, calculators, templates, or interactive elements
- What to exclude to avoid scope drift and keyword cannibalization

PHASE 3 — SITE INTEGRATION
Create an internal-link plan with:
- Relevant pages that should link to this page
- Pages this article should link to
- Natural anchor concepts
- Reader reason for each link
- Potential overlap, merge, redirect, or refresh decisions

PHASE 4 — TRUST AND CONVERSION
Define:
- Author expertise or review evidence the page should display
- Transparency notes and limitations
- A primary and secondary call to action matched to search intent
- Objections or anxieties to address before the CTA
- Accessibility and mobile-reading requirements

PHASE 5 — ACCEPTANCE CRITERIA
Finish with:
- A prioritized production checklist
- A fact-check checklist
- An originality and helpfulness checklist
- Five ways this page could fail
- The analytics events and Search Console signals to review after publication
- A 30/60/90-day refresh plan

Do not draft the full article. Do not invent live data. Clearly label every assumption, research gap, and item requiring human verification.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Analyze the following keyword list for [AUDIENCE] considering [OFFER]: [KEYWORD LIST]. Group terms by the underlying job the searcher is trying to complete, not only by shared words. For each group, identify likely intent, funnel stage, questions, appropriate page type, desired next action, and evidence needed. Flag keywords with mixed or uncertain intent. Do not claim live SERP knowledge; tell me which assumptions require manual SERP validation.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a topic-cluster plan around [CORE TOPIC] for [AUDIENCE], aligned with [BUSINESS PRIORITY]. Existing pages: [EXISTING PAGES]. Propose one pillar page and a limited set of supporting pages. For each page define its unique intent, audience question, scope, exclusions, primary next action, and links to and from the pillar. Identify overlap with existing pages and recommend merge, refresh, or new-page decisions. Avoid producing separate pages for trivial keyword variations.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as an information-architecture editor. Review this page inventory: [PAGE INVENTORY]. The priority page is [PRIORITY PAGE] and the site goal is [SITE GOAL]. Recommend internal links based on what a reader logically needs before or after each page. Return source page, destination page, reason for the link, suggested natural anchor concept, and ideal placement context. Flag orphan pages, circular journeys, and pages that should not be linked simply because they share a keyword.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Using this page summary [PAGE SUMMARY], primary query [PRIMARY QUERY], audience [AUDIENCE], and verified proof point [PROOF POINT], draft six distinct title-tag and meta-description pairs. Keep each pair accurate to the page. Vary the angle, not the factual claim. Explain the intent behind each option and flag any wording that would require stronger proof. Avoid fake urgency, vague superlatives, and repeating the same phrase mechanically.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Review this first-party customer evidence: [CUSTOMER EVIDENCE]. Compare it with the current content inventory: [CURRENT CONTENT] and the offer [OFFER]. Identify unanswered questions, repeated objections, misunderstood concepts, and decisions customers struggle to make. Turn only the strongest gaps into content opportunities. For each, define the reader need, recommended format, original evidence to include, business relevance, and how to avoid duplicating an existing page.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a landing-page brief for [SERVICE] in [LOCATION]. Verified local proof and operational details: [LOCAL PROOF]. Preferred contact method: [CONTACT METHOD]. Build sections that help a local customer evaluate availability, process, service area, proof, common questions, and next steps. Identify the exact local facts, photos, testimonials, or policies still needed. Do not invent landmarks, reviews, addresses, coverage, prices, or response times, and do not reuse generic copy with only the city changed.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Audit this existing page: [CURRENT PAGE]. Available performance data: [PERFORMANCE DATA]. Relevant business or product changes: [BUSINESS CHANGES]. Separate the review into accuracy, intent alignment, usefulness, originality, structure, internal links, and conversion path. Mark each section keep, update, remove, merge, or verify, with a reason. Propose a revised outline only after the diagnosis. Do not assume that adding more words will improve performance.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Synthesize an ideal-customer profile for [OFFER] in [MARKET] using only this evidence: [CUSTOMER EVIDENCE]. Organize the result into observed situation, current behavior, desired outcome, constraints, triggering events, decision criteria, objections, and language customers actually use. Label direct evidence, reasonable inference, and unknowns separately. End with five research questions that would reduce the most important uncertainty. Do not add demographic details unless the evidence supports them.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Develop positioning for [OFFER] aimed at [AUDIENCE] who face [PROBLEM]. Current alternatives: [ALTERNATIVES]. Verified proof: [PROOF]. Produce: category frame, audience, high-value problem, promise, reason to believe, meaningful difference, and what we deliberately do not claim. Then draft three positioning statements with different emphasis and explain the trade-off of each. Flag any claim that is not supported by the supplied proof.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a practical campaign strategist. Create a campaign plan for [OFFER] aimed at [AUDIENCE], with goal [GOAL], budget [BUDGET], and timeframe [TIMEFRAME]. Include the customer problem, credible campaign promise, three message pillars, channel choices with rationale, required assets, launch sequence, three experiments, success and guardrail metrics, risks, and assumptions. Prioritize a coherent campaign over a long list of channels.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Build a distribution plan for this core asset: [CORE ASSET]. Audience: [AUDIENCE]. Available channels: [AVAILABLE CHANNELS]. Goal: [GOAL]. For each recommended channel, define the audience context, adapted angle, native format, opening hook, call to action, timing, and success signal. Create a two-week sequence that reuses the underlying research without copying the same text everywhere. Exclude channels that do not fit and explain why.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Review this landing-page copy: [LANDING PAGE COPY]. Audience: [AUDIENCE]. Offer: [OFFER]. Desired action: [DESIRED ACTION]. Evaluate message clarity, relevance, differentiation, proof, objection handling, information order, friction, and call-to-action continuity. Quote only the smallest necessary fragments. Prioritize the five changes most likely to improve understanding. For each change explain the user problem, proposed revision direction, and evidence needed. Do not invent testimonials or performance claims.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Analyze this customer text: [CUSTOMER TEXT] to answer [RESEARCH QUESTION]. Identify recurring jobs, desired outcomes, frustrations, triggers, objections, decision criteria, and exact phrases worth preserving. For every theme, include supporting excerpts kept as short as possible and note contradictory evidence. Distinguish frequency in this sample from importance; do not generalize beyond the supplied material. End with message hypotheses to test, not final claims.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a marketing experiment backlog for goal [GOAL]. Current funnel: [CURRENT FUNNEL]. Key assumptions: [ASSUMPTIONS]. Constraints: [CONSTRAINTS]. For each experiment define the assumption, change, target segment, primary metric, guardrail metric, minimum useful observation window, effort, risk, and the decision the result will inform. Score impact, confidence, and effort transparently. Prioritize five tests and explain why they come first.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Facilitate a retrospective using the launch plan [LAUNCH PLAN], results [RESULTS], and team notes [TEAM NOTES]. Compare expected and actual outcomes. Separate execution factors, audience response, channel effects, timing, external factors, and data limitations. Identify what to repeat, stop, change, and investigate. For every lesson, cite the supplied evidence and rate confidence. Finish with owners, next experiments, and questions that the current data cannot answer.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create an article outline about [TOPIC] for [AUDIENCE], helping them make [READER DECISION]. Source notes: [SOURCE NOTES]. Propose a clear thesis and an opening that establishes relevance without hype. Build an H2/H3 outline where every section has a purpose, key claim, supporting evidence needed, practical example, and transition. Identify claims the sources do not yet support. End with a conclusion that helps the reader act rather than merely summarize.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Edit the draft below for [AUDIENCE] and purpose [PURPOSE]. Preserve all verified facts and these required terms: [TERMS TO KEEP]. Improve structure, sentence clarity, transitions, specificity, and concision. Remove repetition and replace unnecessary jargon, but do not flatten the author’s voice. Return the revised draft, followed by a short change log for any edit that could affect meaning. Flag ambiguous or unsupported statements instead of silently rewriting them as facts. Draft: [DRAFT]

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Draft a newsletter for [AUDIENCE] around [CORE IDEA], using only [SOURCE MATERIAL]. Structure it with a specific subject line, preview text, concise opening, one useful insight, a concrete example, practical takeaway, and [CALL TO ACTION]. Keep the tone direct and human. Avoid fake personal anecdotes, exaggerated claims, and generic motivational filler. Provide three subject-line options and explain the promise each makes.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a [DURATION] educational video script about [TOPIC] for [AUDIENCE] using [EVIDENCE]. Open with a concrete problem or surprising verified fact, not clickbait. Break the script into spoken lines, on-screen text, and visual direction. Explain one central idea with a practical example and one limitation or caveat. Finish with a useful next step. Estimate timing by section and remove anything that does not support the learning objective.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a case-study draft for [AUDIENCE] using project notes [PROJECT NOTES] and verified results [VERIFIED RESULTS]. Respect these confidentiality limits: [CONFIDENTIALITY LIMITS]. Structure the story as situation, constraints, diagnosis, approach, implementation, result, and lessons. Clearly separate measured outcomes, stakeholder observations, and interpretation. Do not invent quotes, numbers, timelines, or causation. Mark places where approval, evidence, or anonymization is still required.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Repurpose [SOURCE ASSET] for [AUDIENCE] across [CHANNELS], preserving [CORE MESSAGE]. First identify the strongest original insights and evidence. Then create a channel-native plan where each piece has a distinct purpose, angle, hook, format, and next action. Show which source section supports each piece. Avoid copying the same summary repeatedly, and flag any channel that does not fit the material.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a [TIME PERIOD] editorial calendar for [AUDIENCE] and goals [CONTENT GOALS] using idea backlog [IDEA BACKLOG] and capacity [CAPACITY]. Group ideas by reader need and journey stage. Prioritize by usefulness, evidence readiness, differentiation, business relevance, and effort. Return a schedule with working title, purpose, format, source owner, review owner, internal links, distribution plan, and update date. Reserve capacity for refreshing existing content.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Review this draft [DRAFT] against source list [SOURCE LIST] and standard [EDITORIAL STANDARD]. Extract factual claims and label each supported, partially supported, unsupported, time-sensitive, or opinion. Note the source that supports it and what still needs verification. Identify vague attribution, overstatement, internal contradiction, and passages that sound generic or derivative. Do not invent citations or confirm facts beyond the supplied sources. Return a prioritized human-review checklist.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

You are an operations coordinator. Convert [NOTES] into an action plan for [TEAM], considering [DEADLINE CONTEXT]. Separate confirmed decisions, proposed ideas, and unanswered questions. Return a concise summary followed by actions in priority order with suggested owner, due-date placeholder, dependency, completion evidence, and risk. Do not assign commitments that the notes do not support. Add a short list of clarifications needed before the plan is final.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a realistic weekly plan using priorities [PRIORITIES], fixed commitments [FIXED COMMITMENTS], available hours [AVAILABLE HOURS], and constraints [CONSTRAINTS]. Rank outcomes by importance and urgency. Estimate work blocks with buffers, identify what should be deferred, and protect time for deep work and administration. Return a day-by-day plan, a short not-doing list, risks to the schedule, and a recovery rule if one major task slips.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Draft a one-page decision memo for [DECISION]. Context: [CONTEXT]. Options: [OPTIONS]. Evidence: [EVIDENCE]. Include the decision owner, deadline, success criteria, constraints, option comparison, recommendation, rationale, key risks, dissenting view, and what would change the decision. Separate known facts from assumptions. Finish with immediate next actions and a date or condition for review.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a [DURATION] meeting agenda for [ATTENDEES] with goal [MEETING GOAL] and context [CONTEXT]. State the decisions or outputs required. Separate pre-read information from live discussion. For each agenda item include owner, purpose, timebox, preparation, and expected output. Add opening alignment, a parking-lot rule, decision capture, action assignment, and criteria for canceling the meeting if preparation is incomplete.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a concise project update for [AUDIENCE] covering [REPORTING PERIOD] from [PROJECT NOTES]. Structure it as overall status with evidence, outcomes completed, work in progress, blockers and impact, changes since the last update, risks, decisions needed with deadline, and next actions with owners. Do not turn every activity into progress. Flag missing metrics or unclear ownership rather than guessing.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Turn [PROCESS NOTES] into a standard operating procedure for [USER ROLE] using [TOOLS]. Include purpose, scope, prerequisites, roles, inputs, numbered steps, decision points, expected output, verification, exceptions, escalation path, records to retain, and revision owner. Highlight safety or operational risks: [RISKS]. Do not fill missing critical steps with guesses; mark them as questions for the process owner.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Prioritize [BACKLOG] against [GOALS] using criteria [CRITERIA] and capacity [CAPACITY]. Normalize every item into a clear outcome. Score impact, urgency, confidence, effort, risk, and dependency using a defined scale. Show the reasoning and missing evidence for each score. Return now, next, later, and decline groups, plus the trade-offs created by the proposed sequence. Do not treat a numerical score as certainty.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a handoff document for [NEW OWNER] by [HANDOFF DATE] using [PROJECT MATERIAL]. Include purpose, current state, stakeholders, key decisions and rationale, completed work, open work, next three actions, deadlines, dependencies, risks, known issues, recurring routines, required access without exposing credentials, file locations, and questions to ask. Mark information that may be outdated and identify the best source of truth.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as an experienced user researcher. Create a [DURATION] interview guide for [TARGET USER] about [PROBLEM AREA], answering [RESEARCH GOAL]. Start with context and recent behavior, then explore the current workflow, pain points, workarounds, consequences, triggering events, and decision criteria. Avoid leading questions and hypothetical feature pitching. Add neutral follow-up probes and explain what evidence each section is designed to uncover.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Synthesize [SOURCES] to answer [RESEARCH QUESTION] for decision [DECISION]. Create a source table with type, date, relevance, and limitations. Then summarize converging findings, disagreements, plausible explanations, evidence gaps, and practical implications. Distinguish direct evidence from inference. Do not invent citations or details not present in the sources. State what the evidence can support, what it cannot support, and the next evidence worth collecting.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Evaluate [SOURCE MATERIAL] as evidence for [CLAIM] in [USE CASE]. Assess authorship, expertise, publication context, methodology, sample, transparency, incentives, recency, relevance, and corroboration. Separate issues that reduce credibility from issues that merely limit applicability. Quote only short necessary fragments. Return a confidence assessment with reasons, what can safely be cited, what needs qualification, and stronger source types to seek.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Compare [OPTIONS] for [DECISION CONTEXT] using [CRITERIA] and evidence [EVIDENCE]. Define every criterion before scoring. For each option provide supported strengths, limitations, costs, risks, dependencies, and unknowns. Use the same evidence standard across options. Show how the recommendation changes when criterion weights or key assumptions change. If the evidence is insufficient, recommend a test rather than a false winner.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Design a survey for [TARGET POPULATION] to address [RESEARCH OBJECTIVE] and inform [DECISION], within [CONSTRAINTS]. Define constructs, sampling approach, screening, question order, response scales, analysis plan, and limitations. Draft concise neutral questions and explain what each measures. Check for leading wording, double-barreled questions, overlap, missing options, recall burden, and privacy concerns. Do not promise representativeness without a valid sampling plan.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a research plan for decision [DECISION]. Known evidence: [KNOWN EVIDENCE]. Knowledge gaps: [KNOWLEDGE GAPS]. Timeframe: [TIMEFRAME]. Rank gaps by decision impact and uncertainty. Recommend methods, participants or sources, recruitment or access needs, protocol, evidence quality criteria, synthesis approach, milestones, risks, and stopping conditions. Include a lean version and a more rigorous version, explaining what confidence each can provide.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Review [PLAN OR PROPOSAL] in context [CONTEXT] using [AVAILABLE EVIDENCE]. Extract assumptions about users, demand, behavior, operations, technology, timing, cost, regulation, and adoption. Rewrite each as a testable statement. For every assumption record supporting evidence, contradictory evidence, impact if false, uncertainty, owner, cheapest useful test, and decision deadline. Prioritize assumptions with high impact and weak evidence.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Using only [SOURCE SUMMARIES], create a concept map for [TOPIC] within [SCOPE]. Identify core concepts, competing definitions, relationships, mechanisms, methods, schools of thought, and unresolved questions. Link every observation to the relevant supplied source. Note where sources use the same term differently or disagree. Do not invent publications or citations. Finish with a reading sequence and gaps that require primary-source review.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Draft a short follow-up email to [PROSPECT] after a sales conversation. Use only [CALL NOTES]. Restate their priority and the effect of the current problem in neutral language, summarize the relevant part of our discussion, and confirm [NEXT STEP]. Use [TONE] tone and keep it under 140 words. Include one clear call to action. Do not invent urgency, budget, authority, pain, promises, or rapport that the notes do not show.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a [CALL DURATION] discovery plan for [OFFER] using account context [ACCOUNT CONTEXT] and known facts [KNOWN FACTS]. Define the call objective and opening. Build a short sequence of neutral questions about current process, trigger, impact, workarounds, stakeholders, decision criteria, constraints, timing, and desired outcome. Include follow-up probes, signals to listen for, questions to avoid, and a natural method for agreeing on a next step.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create an account plan for [OBJECTIVE] using [ACCOUNT INFORMATION] and [OFFER]. Separate verified account facts from assumptions. Map stakeholders by role, priority, influence, and relationship status without guessing personal motives. Summarize strategic context, current initiatives, possible fit, risks, competitors or alternatives, open questions, and value hypotheses to validate. Finish with a 30-day action sequence, owner, evidence goal, and exit criteria.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Help me respond to this objection: [OBJECTION]. Context: [CONTEXT]. Verified evidence: [VERIFIED EVIDENCE]. Limitations: [LIMITATIONS]. Produce a response sequence that acknowledges the concern, asks one clarifying question, reflects the answer, provides only relevant supported information, states limitations honestly, and proposes a low-pressure next step. Include versions for email and live conversation. Do not manufacture social proof or dismiss the concern.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a proposal outline using [DISCOVERY NOTES], [SOLUTION SCOPE], [COMMERCIAL TERMS], and [PROOF]. Structure it around the buyer’s stated context, desired outcomes, agreed requirements, proposed approach, deliverables, responsibilities, timeline, success measures, assumptions, exclusions, risks, proof, investment, and next decision. Quote buyer language sparingly where useful. Flag gaps or contradictions that must be resolved before drafting. Do not add claims or commitments not provided.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Convert [RAW NOTES] into CRM-ready information for fields [CRM FIELDS] at deal stage [DEAL STAGE]. Separate verified facts, prospect quotes, seller interpretation, and unknowns. Capture current situation, desired outcome, impact, stakeholders, decision process, timing, budget information if explicitly stated, alternatives, objections, commitments, risks, next action, owner, and due date. Do not infer authority, sentiment, or probability without evidence.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a [DEMO TIME] product-demo plan for [ATTENDEES] using [DISCOVERY EVIDENCE] and [PRODUCT CAPABILITIES]. Define the decision the demo should support. Map each buyer need to one scenario, capability, proof point, and confirmation question. Include opening alignment, realistic data setup, timeboxes, likely concerns, limitations to state, and next-step agreement. Remove capabilities that do not connect to verified buyer priorities.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Prepare a renewal review using [CUSTOMER DATA], original goals [ORIGINAL GOALS], current contract [CURRENT CONTRACT], and [STAKEHOLDER NOTES]. Summarize achieved outcomes with evidence, adoption patterns, unresolved goals, support issues, stakeholder changes, risks, and opportunities. Separate measured value from anecdotal value. Create a meeting agenda, questions, renewal options to discuss, and a joint success plan. Do not hide poor results or invent ROI.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a decision analyst. Evaluate [DECISION] in [CONTEXT] using [SUCCESS CRITERIA] and [CONSTRAINTS]. Restate the decision and question whether it is framed correctly. Identify assumptions, stakeholders, opportunity costs, dependencies, and second-order effects. Compare at least three realistic options using the same criteria. Include a pre-mortem, signals that would change the recommendation, and the smallest reversible experiment to run next. Label uncertainty clearly.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a SWOT for [ORGANIZATION OR PROJECT] pursuing [OBJECTIVE] over [TIME HORIZON], using only [EVIDENCE]. Keep strengths and weaknesses internal; opportunities and threats external. For each item provide evidence, strategic relevance, confidence, and implication. Remove generic statements that could describe any organization. Then identify the most important cross-combinations: use a strength, repair a weakness, capture an opportunity, and reduce a threat.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Develop three to four plausible scenarios for [DECISION AREA] over [TIME HORIZON] using [CRITICAL UNCERTAINTIES] and [KNOWN TRENDS]. Give each scenario a coherent causal logic, not just an optimistic or pessimistic label. For each, describe conditions, leading indicators, stakeholder effects, opportunities, risks, and strategic implications. Identify no-regret actions, options to preserve, and triggers for changing course. Do not assign unsupported probabilities.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Prioritize [INITIATIVES] against [STRATEGIC GOALS] under [CONSTRAINTS], using [EVIDENCE]. Define scoring criteria and weights before evaluation. Assess expected value, strategic fit, confidence, effort, time to learning, risk, dependencies, and reversibility. Show the reasoning and sensitivity to different weights. Return invest, test, sequence later, and stop groups. Explain the opportunity cost of the recommended portfolio.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Facilitate a pre-mortem for [PLAN] intended to achieve [OBJECTIVE], considering [CONSTRAINTS] and [TEAM CONTEXT]. Assume the plan failed and generate plausible causes across customer, strategy, execution, people, technology, finance, timing, and external factors. For each cause record likelihood range, impact, earliest observable signal, prevention, contingency, and owner. Prioritize the risks that are both consequential and actionable. Avoid dramatic but irrelevant possibilities.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Outline an operating model to deliver [STRATEGY] within [SCOPE], starting from [CURRENT STATE] and [CONSTRAINTS]. Define required capabilities, key value streams, roles, decision rights, handoffs, information flows, systems, governance rhythms, metrics, and escalation. Highlight gaps between current and target state. Propose a phased transition with assumptions, dependencies, and leading indicators. Avoid generic organization-chart recommendations.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Analyze [COMPETITOR EVIDENCE] in relation to [OUR STRATEGY] and [MARKET QUESTION]. Separate directly observed facts, reasonable interpretations, alternative explanations, and unknowns. Compare customer promise, target segment, route to market, capabilities, trade-offs, and visible moves only where evidence exists. Identify implications for our choices, but do not infer private financials, intent, or performance. Finish with questions and ethical evidence sources to investigate.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Turn [STRATEGIC DIRECTION] into a 90-day plan from [STARTING STATE], considering [TEAM CAPACITY] and [DEPENDENCIES]. Define three to five outcomes, success and guardrail metrics, key decisions, experiments, capability work, owners, dependencies, and risks. Sequence work into days 1–30, 31–60, and 61–90. Include weekly review questions, stop conditions, and what is explicitly out of scope.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Act as a pragmatic senior software reviewer. Review [CODE] for [GOAL] in [STACK] under [CONSTRAINTS]. Check correctness, security, performance, accessibility where relevant, maintainability, and tests. Prioritize findings by severity. For every finding quote only the smallest necessary fragment, explain the concrete impact, and propose a minimal fix. Separate confirmed issues from questions and preferences. Finish with missing tests and a concise ship/no-ship recommendation.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Help debug this issue. Expected behavior: [EXPECTED BEHAVIOR]. Actual behavior: [ACTUAL BEHAVIOR]. Relevant code: [CODE]. Logs or errors: [LOGS]. Recent changes: [RECENT CHANGES]. Restate the failure precisely, list the smallest set of plausible hypotheses ranked by evidence, and propose one discriminating test per hypothesis. Recommend the minimal fix only after identifying the most likely cause. Include regression tests and note missing information.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Turn [FEATURE IDEA] into an implementation-ready specification for [USERS] in [SYSTEM CONTEXT] under [CONSTRAINTS]. Include problem, user outcome, scope, non-goals, user flow, states, business rules, permissions, data inputs and outputs, errors, empty and loading states, edge cases, accessibility, analytics, security considerations, dependencies, rollout, and acceptance criteria in Given/When/Then form. List open questions instead of inventing requirements.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create a risk-based test plan for [FEATURE OR CODE] with expected behavior [EXPECTED BEHAVIOR] in [STACK]. Known risks: [KNOWN RISKS]. Identify critical paths, invariants, boundaries, invalid input, state transitions, concurrency where relevant, dependency failures, permissions, security, accessibility, and regression areas. Map each test to a risk and recommend unit, integration, end-to-end, or manual coverage. Include fixtures, mocks, and what not to over-test.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Plan an incremental refactor of [CODE] to address [PAIN POINTS] while preserving [BEHAVIOR TO PRESERVE] under [CONSTRAINTS]. Diagnose coupling, duplication, unclear responsibilities, and test gaps. Define target boundaries, characterization tests, small ordered steps, checkpoints, migration strategy, observability, and rollback. Explain trade-offs and avoid a full rewrite unless the evidence clearly justifies it.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Create API documentation from [API SPEC OR CODE] for [AUDIENCE]. Authentication: [AUTH METHOD]. Known limits: [KNOWN LIMITS]. Include purpose, base concepts, prerequisites, endpoint reference, parameters, request and response examples, status and error handling, pagination, idempotency, rate limits, security notes, versioning, and a minimal working quickstart. Do not invent endpoints or behavior. Mark ambiguities and missing examples for engineering review.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Perform a defensive security review of architecture [ARCHITECTURE] and code [CODE], handling data [DATA] for roles [USER ROLES]. Map assets, trust boundaries, entry points, authentication, authorization, validation, data storage, secrets handling, logging, dependencies, and abuse cases. Prioritize concrete findings by likelihood and impact, cite the relevant evidence, and propose mitigations plus verification tests. Do not provide exploit instructions; focus on prevention and secure design.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.

Draft an architecture decision record for [DECISION] in [CONTEXT]. Options: [OPTIONS]. Constraints: [CONSTRAINTS]. Evidence: [EVIDENCE]. Include status, decision date, owners, context, decision drivers, considered options, comparison, chosen option, rationale, positive and negative consequences, risks, implementation notes, rejected alternatives, and review triggers. Separate current facts from forecasts and list unresolved questions.

EXPERT EXECUTION PROTOCOL
1. Begin by restating the objective, intended audience, supplied evidence, constraints, and missing information.
2. Ask no more than three high-impact clarification questions when missing context would materially change the result. Otherwise continue with clearly labeled assumptions.
3. Work from the supplied facts. Do not invent research, statistics, quotations, customer evidence, rankings, citations, capabilities, or results.
4. Make the reasoning auditable: distinguish evidence, interpretation, recommendation, risk, and open question.
5. Produce a decision-ready deliverable, not generic advice. Prioritize the most valuable actions and explain the trade-offs.
6. Finish with:
   - Assumptions to validate
   - Risks and failure modes
   - Recommended next actions
   - Quality-control checklist

QUALITY STANDARD
The result must be specific enough for an experienced professional to use, concise enough to review, and honest about uncertainty. Reject vague filler, repeated ideas, unsupported superlatives, and fabricated facts.