Hire an AI story ad workflow test planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A story ad test plan with the lead problem and four stories
• A handoff card for each AI step and a card for each claim
• Run rules for saving, retrying and resuming
• A blind old-versus-new score out of 100, with failures and cost per usable ad

How it does the job well

• Clarify the purpose, audience and limits, such as length, format and deadline, first.
• Use the user's materials and voice. Ask for samples when tone matters.
• Be specific and concrete. Cut what does not serve the purpose.
• Say what you are unsure of and where to check it.

Mistakes it avoids

• Generic output that ignores the user's details.
• Inventing facts, quotes or sources.
• Long answers when a short one was asked for.

What a good result looks like

An example, not your task: You changed how AI makes your ads and want proof before you switch.

• Story ad test plan. The lead problem, the narrator, four stories and where the click goes.
• Handoff cards. A card for each claim with full wording and limits, and a card for each AI step.
• Run rules. How to save results, retry a failed step, resume a run and keep to budget.
• Old versus new score. Pass rates, blind picks judged twice, failures, cost per usable ad and a decision.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Plans the story ad test. Uses the story ad test planner to sort customer words into problems and plan four stories on the lead problem.
• Plans the handoffs. Uses the handoff planner to lock claims as whole cards and write what each step needs and must never lose.
• Waits for both runs. You run the old chain and the new chain on the same briefs and save every image ad.
• Scores old against new. Uses the old versus new scorer to freeze the before set, build matched pairs and judge blind, twice, with the order swapped.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id ad-ai-setup-test only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/ad-ai-setup-test/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Customer reviews, copied as written
• Your product facts
• The buyer brief both setups work from
• The image ads your old setup made, saved before you change it
• The image ads your new setup makes from the same briefs
• Your persona and landing page (optional)

Tools and access

• Any good chat AI: Sorting and counting reviews works well in any current chat AI, as long as all the reviews fit in one chat.
• Meta Ad Library: Shows which stories rivals already run, free and without an account, so the aim is based on fact.
• Claude Code: Can run the chain as files and code, save every step's request and reply, and do the counts in code.
• Claude: Follows long handoff cards closely and returns work in the fixed shape you ask for.
• Claude: Follows a long judging brief closely. Still judge each pair twice in swapped order, since any judge can favour the first answer it sees.
• Google Sheets: Holds the pairs, both rounds of picks and the counts, so anyone can check the sums.

Functions and deliverables

• Story ad workflow test planner: Plan an old-versus-new story ad test, define what each AI step receives, then compare saved outputs and costs.
  • A story ad test plan with the lead problem and four stories
  • A handoff card for each AI step and a card for each claim
  • Run rules for saving, retrying and resuming
  • A blind old-versus-new score out of 100, with failures and cost per usable ad
• Story ad test planner: Plan a story ad before you write it. Paste your facts and reviews to get a fit verdict, an honest narrator and four story tests.
  • A fit verdict, and a table of problems with counts and strength
  • The lead problem, with why people switch, in buyers' exact words and review numbers
  • The narrator, the page the click opens, and a four-row test plan
  • What a person must check, how to read results, and every gap in one list
  • Any check the sheet still missed, one line each
• AI creative workflow handoff planner: List the steps in your creative AI workflow. Get clear instructions for passing facts and results between them, with claim limits kept intact.
  • Claim cards, each with its full wording, limits and source
  • A handoff card for each step (needs, may use, returns, never lose)
  • A bundle order (stable part first, then the part that changes) and run rules
  • A list of shortfalls and trade-offs
  • Any of its own checks the plan still misses, each named
• Ad prompt comparison reviewer: Compare old and new ad prompts with a blind test. Paste both sets of ads. Get a keep-or-switch decision and a score out of 100.
  • A pass-or-fail result for every ad, with outright failures listed for each side
  • A blind pick for each pair, judged twice with the order swapped, and the reasons
  • Wins, ties and losses checked against the wins-needed table, plus cost per usable ad
  • A one-paragraph decision on whether to switch
  • A win score out of 100 (the new version's share of decided pairs) and each side's pass rate
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• You changed how AI makes your ads and want proof before you switch.
• Your AI steps drop a fact or invent one.
• You pay for AI by use and want to know the cost per usable ad.

Limits to check before starting

• You have not changed your ads or AI setup yet: write the brief first with the Buyer brief writer.
• You only want to check one ad before it goes live: use the Pre-launch ad checker.
• You want to plan what to test with real ad spend: use the Ad test brief writer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Have your inputs ready. It works step by step and saves each result.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/ad-ai-setup-test for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.