Best Claude Prompts: 90 Workflows Worth Copying

You are reviewing a contract, not providing legal advice. Read the attached contract and the requirements checklist. Use only the supplied documents.

<requirements>[PASTE REQUIREMENTS]</requirements>
<context>[TRANSACTION AND JURISDICTION]</context>

Create a table: requirement | relevant clause and page | status (met/partial/missing/unclear) | evidence quote (short) | business risk | question for counsel. Distinguish absent terms from terms you could not locate. Finish with the five highest-priority clarifications.

Compare the attached OLD and NEW policy versions. Treat each as a separate source. Build a change log with section reference, exact nature of change, who is affected, operational consequence and required action. Flag removed safeguards and ambiguous wording. Do not invent provisions. Finish with a one-page employee briefing and a list of unresolved questions.

Analyze the attached PDF files for this question: [QUESTION]. First inventory filenames, dates, authors and readable sections. Then produce: answer; evidence table with file/page references; conflicting findings; missing data; limitations; and recommended verification. Mark every unsupported inference as an inference. Do not use external facts unless I explicitly authorize research.

From the attached agreement, extract every obligation, notice period, deadline, deliverable and approval gate. Output columns: party | obligation | trigger | due date or calculation rule | clause/page | dependency | consequence | confidence. Keep dates relative where the contract uses relative dates. List clauses needing human interpretation.

Review the attached technical report for a nontechnical leadership audience. Preserve units and uncertainties. Produce a 150-word executive summary, a table of major findings with page references, operational risks, assumptions, data gaps and three decision options with trade-offs. Separate measurements from interpretations and recommendations.

Use only the attached manual and policy documents to draft 15 employee FAQs. For each answer provide the source filename and page/section. If the answer is not in the documents, write “Not specified in supplied sources.” Group questions by onboarding, daily use, troubleshooting and escalation.

<original_text>[PASTE TEXT]</original_text>
<audience>[WHO WILL READ IT]</audience>
<tone>clear, confident, respectful</tone>

Rewrite the text without changing facts, commitments, numbers, names or dates. Provide (1) the polished version, (2) a concise version, and (3) a change log of any meaningful editorial choices. Flag factual ambiguity instead of resolving it silently.

Write an executive decision brief for [DECISION].
<context>[BACKGROUND]</context>
<evidence>[FACTS AND LINKS]</evidence>

Use: decision requested; why now; options considered; cost/benefit table; risks and mitigations; recommendation; next 30 days. State assumptions explicitly. Do not manufacture numbers, endorsements or quotations.

Act as a developmental editor. First analyze the attached report's audience, argument, structure, evidence and repetition. Return a prioritized editorial plan only. Wait for my approval before rewriting. When approved, preserve factual claims and citations, improve headings and transitions, and supply a before/after change summary.

For [PRODUCT] targeting [AUDIENCE], create three substantially different landing-page concepts: outcome-led, problem-led and proof-led. For each include headline, subhead, value proposition, feature-to-benefit mapping, objection handling and CTA. Use only provided product claims. Do not invent testimonials, results or guarantees.

Transform the notes below into a helpful guide for [AUDIENCE].
<notes>[NOTES]</notes>

First identify gaps and unverifiable claims. Then write a structured guide with an answer-first opening, examples, step-by-step instructions, common mistakes and a short checklist. Mark any claims that require sourcing. Do not pretend to have tested tools or interviewed experts.

Read this draft as a rigorous editor. My intended voice is [VOICE]. Score clarity, accuracy, organization and reader usefulness from 1–5, with specific evidence. Identify the five highest-impact fixes. Suggest sentence-level changes only where needed; do not rewrite the whole piece unless I ask.

Review the uploaded repository or files. First identify which files you can actually access. Map the architecture, entry points, important modules, data flow, configuration and test strategy. Cite file paths and relevant functions. Flag unknown dependencies. Give me a safe local setup checklist and five questions to ask the maintainers. Do not claim to have executed the code.

I have this bug: [SYMPTOMS]. Environment: [VERSIONS]. Expected: [EXPECTED]. Actual: [ACTUAL]. Logs: [LOGS].

List hypotheses ranked by evidence, then propose the smallest diagnostic checks to distinguish them. Do not jump to a rewrite. Once the root cause is supported, propose a minimal patch, tests and rollback instructions. Clearly label unverified hypotheses.

Review this patch for correctness, security, backward compatibility, performance and maintainability. Cite file and line ranges where possible. Classify findings as blocker, important or suggestion. For each provide failure scenario, evidence and smallest fix. Also identify missing tests. If nothing serious is found, say so without inventing problems.

Analyze this module: [CODE OR ATTACHED FILE]. Goal: [DESIRED CHANGE]. Constraints: preserve public API, behavior and existing tests. Produce a dependency map, invariants, incremental refactor sequence, characterization tests and rollback plan. Do not implement until I approve step one.

Design an API for [USE CASE] with consumers [CLIENTS]. Produce resource model, endpoint table, request/response JSON examples, authentication and authorization rules, pagination, idempotency, errors, rate limits, versioning and observability. Include at least 12 edge cases and a contract-test checklist. Identify decisions requiring product input.

Threat-model [FEATURE] using this architecture: [ARCHITECTURE]. Identify assets, trust boundaries, actors, entry points and plausible abuse cases. Rank risks qualitatively with rationale. Recommend defensive controls and validation tests. Do not provide exploitation instructions. Note assumptions and missing diagrams.

Analyze the attached spreadsheet for [BUSINESS QUESTION]. Inventory sheets, columns, units and date ranges. Check duplicates, missing values, outliers and inconsistent definitions. Explain formulas before computing conclusions. Return key findings with exact cell or sheet references, limitations and recommended next analyses. Never fabricate data.

Evaluate these three claims: [CLAIMS]. Sources: [ATTACHED STUDIES OR LINKS]. For each identify study design, sample, measured outcome, limitations, possible confounders and strength of evidence. Separate what is established, plausible and unsupported. Include a comparison matrix and what new evidence would change the conclusion.

I must choose among [OPTIONS]. Criteria: [CRITERIA]. Constraints: [BUDGET/TIMELINE]. Ask me for missing critical weights before ranking. Then create a weighted decision matrix, sensitivity analysis, major risks and a recommendation that explains what would reverse it. Label every assumed score.

Act as a skeptical but fair investment committee. Review the attached proposal. Identify hidden assumptions, untested demand, operational dependencies, downside scenarios, unit economics gaps and execution risks. Provide 10 hard questions, the evidence required to answer each, and a revised go/no-go decision framework. Do not invent market data.

Analyze the interview transcripts provided. Remove personal identifiers from the summary. Create a theme map with frequency counts only where defensible, representative short quotes with transcript IDs, contradictory views and limitations. Separate participants' statements from your interpretation. Do not infer demographic traits.

For the hypothesis [HYPOTHESIS], design a test. Specify primary metric, guardrail metrics, target population, assignment, confounders, sample-size inputs, stop conditions, data quality checks and analysis plan. Do not invent statistical power or sample size without assumptions. Provide a pre-registration template.

Act as my project planning partner. Goal: [GOAL]. Deadline: [DATE]. Team and resources: [DETAILS]. Constraints: [DETAILS]. Build milestones, work breakdown, dependencies, owners (TBD where unknown), acceptance criteria, risk register and weekly review agenda. Highlight the critical path only if enough information is available.

From the supplied project documents, create a concise project brief with scope, non-goals, stakeholders, terminology, decisions, constraints, source-of-truth links, open questions and next actions. Mark unconfirmed items. Format it for reuse as context in future Claude conversations or Projects.

Using the supplied meeting notes and project documents, prepare for the next steering meeting. Summarize decisions made, actions due, blockers, unresolved trade-offs and decisions needed. For each action include owner and due date only if documented. Draft a 30-minute agenda and five targeted questions.

Build a testable acceptance checklist for [DELIVERABLE] from the attached specification. Each item needs requirement ID, verification method, expected evidence, responsible reviewer and pass/fail criteria. Identify requirements that are subjective or not testable. Do not silently add contractual requirements.

For [PROJECT], identify plausible schedule, cost, quality, safety, supplier and regulatory risks based on supplied facts. Create columns: risk | cause | impact | likelihood rationale | early-warning trigger | mitigation | contingency | owner TBD. Avoid numerical risk scores unless a scoring rubric is supplied.

Prepare a handover pack from these project files: [FILES]. Include delivered scope, configuration, operating instructions, known issues, open punch-list items, warranties or references if documented, training needs, contacts and sign-off checklist. Do not mark anything complete without evidence.

My research question is [QUESTION]. Break it into 5–8 answerable subquestions, then list evidence types and primary sources needed for each. Distinguish descriptive, causal and predictive questions. Create a search strategy, exclusion criteria, synthesis plan and explicit uncertainty log. Do not imply web research was performed unless tools are available.

Audit the draft and attached references. For each factual claim identify whether a cited source directly supports it, partially supports it, contradicts it or is missing. Quote only short relevant passages and provide page/section references where available. Flag stale sources and broken chains of attribution. Never invent a citation.

Synthesize the supplied studies on [TOPIC]. Group by methodology and findings, not by author alone. Compare effect direction, magnitude if reported, uncertainty, limitations and external validity. Identify disagreements and plausible explanations. End with evidence gaps and research priorities. Do not perform a meta-analysis without compatible data.

Review this article: [TEXT]. Extract each factual, numerical, comparative and time-sensitive claim. Create a verification ledger: claim | source needed | source supplied | status | risk if wrong | recommended revision. Label unsupported claims rather than searching or fabricating evidence without permission.

Map the strongest arguments for and against [QUESTION] using supplied source material. Steelman both positions, distinguish empirical claims from value judgments, identify shared premises, and explain where evidence is contested. Provide a neutral briefing and a list of facts that would help resolve disagreement.

I want to understand [TOPIC] at [LEVEL]. Time available: [HOURS]. Based on the supplied reading list, sequence materials from foundational to advanced, explain each source's role, define learning objectives and create comprehension questions. Mark gaps where a source has not been provided.

For [PRODUCT], design a microcopy system for onboarding, forms, errors, empty states and confirmation messages. Audience: [AUDIENCE]. Brand voice: [VOICE]. Include writing principles, do/don't examples, accessibility checks and a table of UI state → recommended copy → rationale. Do not promise capabilities the product lacks.

Review the attached UI screenshots for [USER TASK]. Evaluate hierarchy, clarity, navigation, form usability, mobile behavior and accessibility risks. Separate directly visible issues from hypotheses requiring user testing. Prioritize findings by impact and effort. Propose specific improvements and validation tasks.

Specify a reusable [COMPONENT] for web and mobile. Include purpose, variants, states, responsive behavior, keyboard interactions, screen-reader labels, error handling, content rules, tokens and acceptance criteria. Flag choices requiring design-system approval. Provide a handoff checklist for engineering.

Design a moderated usability test for [PRODUCT FEATURE]. Identify user segments, recruitment criteria, realistic tasks, neutral facilitator script, success measures, observation sheet and synthesis method. Avoid leading questions. Provide consent and privacy considerations without claiming legal compliance.

Analyze these anonymized user feedback notes: [NOTES]. Group by underlying user need, identify repeated friction, separate frequency from severity, and suggest candidate improvements. For each give evidence, confidence, expected outcome and validation experiment. Do not turn isolated comments into universal claims.

For [WEBSITE] serving [AUDIENCE], propose an information architecture based on the supplied content inventory. Create navigation, page purpose, unique search intent, internal-link pathways, page-level content requirements and mobile-first wireframe descriptions. Identify overlapping pages and consolidation candidates. Do not promise search rankings.

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Board pack evidence audit. Work from board papers, appendices and minutes supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a decision log, evidence map, and unresolved approval conditions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Supplier specification reconciliation. Work from two supplier datasheets and a purchasing specification supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a requirement-by-requirement compliance matrix with unit conversions flagged. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Insurance policy coverage comparison. Work from two policy documents and an incident scenario supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a coverage comparison with exclusions and questions for the insurer. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Meeting minutes to accountable action register. Work from minutes from three project meetings supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce an action register with owners, deadlines, dependencies and source references. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Regulatory consultation response. Work from a consultation paper and organizational feedback supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a clause-linked response that distinguishes facts, impacts and proposed wording. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>SOP contradiction detector. Work from a standard operating procedure and training manual supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a contradiction register with affected steps and safety implications. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Tender document completeness review. Work from a tender pack, annexures and submission checklist supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a missing-document and ambiguity checklist without invented compliance claims. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in documents who prioritizes traceable evidence over confident guesses.</role>
<task>Multi-report timeline reconstruction. Work from several incident reports with conflicting timestamps supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a sourced chronology with discrepancies and missing evidence. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Preserve voice across a newsletter series. Work from three past newsletters and a new topic outline supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a new edition plus a style-consistency checklist. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Turn interview transcripts into a case study. Work from an interview transcript and approved factual claims supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a customer story with quote approvals and a fact-check list. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Prepare a difficult stakeholder update. Work from a delayed project status and verified reasons supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a candid update with decisions needed and a revised milestone table. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Build a publication fact-check ledger. Work from a long-form draft and its source files supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a claim-by-claim verification ledger with unresolved citations. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Convert technical notes into an executive narrative. Work from engineering notes and verified performance data supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a decision-ready executive narrative preserving units and caveats. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Create a consistent documentation style guide. Work from five existing help-center articles supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a concise editorial style guide with before-and-after examples. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in writing who prioritizes traceable evidence over confident guesses.</role>
<task>Reconcile conflicting editorial feedback. Work from two reviewers comments on one article supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a prioritized change plan separating facts from stylistic preferences. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Trace a regression to a release. Work from a changelog, failing test and relevant source files supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a ranked regression hypothesis list and minimal verification plan. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Map database migration risks. Work from current and proposed database schemas supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a migration risk table, validation queries and rollback conditions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Review authentication flows defensively. Work from architecture diagrams and auth middleware code supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a defensive access-control checklist and missing tests. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Design property-based test cases. Work from a function contract and representative examples supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce invariants, generators, edge cases and test pseudocode. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Analyze CI failure patterns. Work from build logs from passing and failing runs supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a failure taxonomy with likely causes and reproduction checks. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Document an unfamiliar API. Work from api routes, types and integration tests supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce endpoint documentation with grounded examples and unknowns. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Plan a monolith extraction. Work from module dependencies and service-level requirements supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a staged extraction plan with observability and rollback gates. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in coding who prioritizes traceable evidence over confident guesses.</role>
<task>Review error handling across services. Work from service interfaces and logging conventions supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce an error taxonomy with propagation and alerting recommendations. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Audit KPI definition drift. Work from kpi definitions from two reporting periods supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a metric-definition change log and comparability warnings. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Analyze a supplier scorecard. Work from supplier performance data and evaluation criteria supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a scorecard with transparent weighting and missing-data caveats. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Reconcile survey themes with counts. Work from survey comments and numeric responses supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a coded-theme summary with illustrative evidence and sample limitations. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Find unsupported assumptions in a forecast. Work from forecast model assumptions and source notes supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce an assumption register and sensitivity-test plan. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Evaluate competing vendor proposals. Work from three proposals and mandatory requirements supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a traceable comparison table and unanswered vendor questions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Create an evidence-based incident review. Work from an incident chronology and witness statements supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a factual timeline, competing hypotheses and preventive actions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in analysis who prioritizes traceable evidence over confident guesses.</role>
<task>Review operational handover readiness. Work from punch list, test certificates and handover criteria supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a readiness matrix with outstanding blockers and ownership. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Create a gated implementation roadmap. Work from a project brief, resources and constraints supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a milestone plan with acceptance criteria and approval gates. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Build a dependency-aware launch checklist. Work from product release requirements and stakeholder roles supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a launch checklist with owners, prerequisites and rollback triggers. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Plan a cross-functional workshop. Work from workshop objectives and participant roles supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a timed agenda, exercises, outputs and decision log template. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Prepare a decision meeting pack. Work from three options, cost data and stakeholder concerns supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a pre-read, agenda and explicit decision questions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Translate strategy into quarterly outcomes. Work from strategy memo and baseline metrics supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce measurable outcomes, initiatives, dependencies and risks. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in planning who prioritizes traceable evidence over confident guesses.</role>
<task>Design a project lessons-learned process. Work from completed project records and retrospective notes supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a neutral retrospective with actions, owners and follow-up measures. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Construct a claim-evidence map. Work from a research question and supplied studies supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a claim-evidence matrix with counterevidence and limitations. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Compare methods across papers. Work from several academic papers and their appendices supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a methods comparison covering samples, measures and bias. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Write a literature gap memo. Work from a curated bibliography and abstracts supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a gap analysis distinguishing absent evidence from unexplored questions. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Audit citations in a draft. Work from a manuscript and referenced source documents supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a citation accuracy table with unsupported statements flagged. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Build a reproducible research protocol. Work from a research question and available data supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a preregistration-style plan with definitions and exclusion criteria. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in research who prioritizes traceable evidence over confident guesses.</role>
<task>Summarize disagreement between experts. Work from two expert reports and primary evidence supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a fair disagreement map and evidence needed to resolve it. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Audit a mobile onboarding flow. Work from screen descriptions, funnel data and user feedback supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a friction map with accessible design alternatives and experiments. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Create a design-system content inventory. Work from component screenshots and design guidelines supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a component naming and content consistency audit. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Evaluate form accessibility. Work from a form specification and error messages supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a keyboard, label, validation and recovery checklist. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Prioritize usability findings. Work from moderated usability notes and severity criteria supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a severity-ranked issue log with evidence and recommended tests. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Write inclusive empty and error states. Work from a product workflow and supported recovery actions supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce microcopy variants that explain what happened and what to do next. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>

<role>Act as a careful specialist in design who prioritizes traceable evidence over confident guesses.</role>
<task>Design a responsive content hierarchy. Work from a long article outline and mobile constraints supplied by me. My specific goal is [GOAL].</task>
<context>Audience: [AUDIENCE]. Constraints: [CONSTRAINTS]. Decision or use: [USE CASE].</context>
<method>First inventory the materials you can actually access. Identify gaps, ambiguous terms, dates and assumptions. Use a structured analysis appropriate to the task, link important findings to the supplied evidence, and keep facts separate from interpretations. If a necessary source is missing, request it rather than filling the gap with fabricated details.</method>
<deliverable>Produce a content-first responsive hierarchy with progressive disclosure. Include a concise executive summary, a source/evidence column where relevant, specific next actions, and a short list of items requiring human verification.</deliverable>
<quality_checks>Check names, numbers, dates, units, dependencies and contradictions. Never claim to have opened files, run code or verified facts unless you actually did.</quality_checks>