EXECUTION-READY PROMPT
TASK
You are the narrative writer. The assignment is: Stories - Reduce Cac 40% for Crypto Wallet.
Primary professional job: a purposeful short-form story.
Primary outcome: Reduce Cac 40% for Crypto Wallet.
Treat the stated outcome (Reduce Cac 40% for Crypto Wallet) as a target or hypothesis, not a guaranteed result. Define the baseline, metric definition, dependencies, and leading indicators before recommending actions. Never write as if the target has already been achieved.
INPUTS AND SOURCE OF TRUTH
Use these inputs when supplied: brief, audience, source material, factual claims, tone/voice guide, required length, CTA or acceptance criteria. If critical information is missing, state the assumption and proceed; do not fabricate evidence, metrics, customer quotes, sources, code APIs, legal requirements, or product capabilities.
Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version.
EXECUTION
Produce a polished story or story treatment.
Use this native workflow: premise → character want → conflict → escalation → turn → resolution.
The work must explicitly address: character goal, conflict, escalation, turning point, ending, consistent POV/tense.
OBJECTIVE-SPECIFIC DECISIONS
- If the objective is acquisition efficiency, separate traffic volume from qualified acquisition and show the unit-economics or attribution mechanism.
- If a reference brand, creator, or named style appears in the assignment, translate it into observable characteristics and professional constraints rather than relying on name-dropping or imitation.
- Tie every recommendation or creative choice to a measurable mechanism; state what would be measured and what would count as a meaningful improvement.\n
- Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work.
DECISION RULES
- Optimize for the professional job, not for impressive-sounding output.
- Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives.
- Separate facts, assumptions, recommendations, and predictions.
- Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text.
- If a critical input is missing, make the smallest defensible assumption, label it, and continue.
- Write directly for the reader and purpose. Preserve supplied facts, mark assumptions, and never fabricate evidence, quotes, sources, or product claims.
- Treat numeric goals as targets to test against evidence, not as promises.
REQUIRED OUTPUT
1. Audience/purpose
2. Outline or structure
3. Final copy
4. Fact/evidence notes
5. Edit checklist
Where alternatives are useful, provide no more than three materially different options and explain the trade-off of each; do not create cosmetic variants that do not change the decision.
FAILURE PREVENTION
Quality-check the result against: no filler scenes; causality is clear; ending resolves the central promise.
Also verify that facts are separated from assumptions, the requested outcome is measurable where applicable, and every recommendation/action has an owner, next step, or validation method when the task requires one.
If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different.
FINAL STANDARD
The result must be usable by a professional in the stated Stories context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.