You are a market researcher.
Analyze the notes below and identify:
- recurring pains
- desired outcomes
- current workarounds
- buying objections
- phrases customers use repeatedly
Return a summary plus a ranked opportunity table.

Create 4 positioning angles for {{offer_name}}.
Audience: {{audience}}
Problem solved: {{problem}}
Proof available: {{proof}}
Constraints: no buzzwords, no competitor references.
Return angle, headline, promise, proof hook, risk of sounding generic.

Build a landing page outline for {{offer_name}}.
Include hero, problem, solution, proof, objections, CTA.
Audience: {{audience}}
Goal: {{goal}}
Tone: {{tone}}
Do not write filler transitions.

Generate 10 distinct ad hooks for {{product}}.
Audience: {{audience}}
Channels: {{channels}}
Return a table with emotional trigger, opening line, visual concept, proof cue, likely objection.

Using the notes below, create a newsletter issue.
Return 3 subject lines, one intro, 3 section headings, and a closing takeaway.
Keep my voice: {{voice_notes}}.
Do not invent examples.

Turn the notes below into an executive summary for {{audience}}.
Return:
- one-paragraph overview
- top findings
- impact
- recommendation
- what not to prioritize yet
Tone: crisp and evidence-first.

Write a short prospecting email for {{service}}.
Prospect type: {{prospect_type}}
Observed issue: {{observed_issue}}
Goal: book a discovery call.
Constraints: under 140 words, no fake flattery, no generic opener.

Prepare me for a discovery call.
Based on the notes below, return likely pains, likely objections, 5 diagnostic questions, deal risks, and a strong closing summary.

Create a standard operating procedure from the notes below.
Audience: new hire with zero context.
Include purpose, tools, step-by-step process, failure points, escalation rules, final checklist.

Environment: {{environment}}
Observed behavior: {{observed_behavior}}
Error: {{error_message}}
Expected behavior: {{expected_behavior}}
Return root cause, smallest patch, tests, and any deployment or migration notes.

Review the code below for correctness, readability, edge cases, performance, and security.
Return issues ranked by severity, then a minimal revised version, then tests that would catch the worst issue.

Extract the fields below from the source text.
If a field is absent, return null.
Do not infer unsupported values.
Schema:
{{schema}}
Source text:
{{source_text}}

<documents>
  <document id="1"><source>{{source_1}}</source><document_content>{{doc_1}}</document_content></document>
  <document id="2"><source>{{source_2}}</source><document_content>{{doc_2}}</document_content></document>
</documents>
<task>
First quote the most relevant evidence.
Then summarize the key findings.
Then identify contradictions or open questions.
</task>

Break the goal below into a prompt chain.
Goal: {{goal}}
Constraints: {{constraints}}
Return:
- stage name
- input to that stage
- output from that stage
- quality check for that stage

Score the draft asset below from 1-10 on clarity, proof, objection handling, tone, CTA strength, and distinctiveness.
Then rewrite only the weakest section.

Analyze this meeting transcript.
Return:
- decisions made
- unresolved questions
- assigned owners
- deadlines
- risks or blockers
If ownership is unclear, say unassigned.

Design a practical curriculum for {{audience}}.
Goal: {{goal}}
Constraints: {{constraints}}
For each module include outcome, lesson concept, exercise, checklist, and common mistake.

Review the prompt below.
Identify missing context, vague goals, hidden assumptions, weak output definitions, and missing checks.
Then rewrite it using the 7-part Prompt Spine.