Hire an AI early product idea test planner

Everything it can hand back

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

• A map of who pulls on the idea and where the pull has started to steer it
• A call to keep protecting, change the approach, change the lead or stop, with evidence and a date to look again
• A protection plan with who sees it, which questions are allowed, who pays and the hand-off date and test

How it does the job well

• Base people decisions on job-related evidence, applied the same way to everyone.
• Write in plain, respectful language the person affected could read.
• Keep personal data to what the task needs, and handle it privately.
• Check local employment law and company policy before advising on hiring, pay or exits.

Mistakes it avoids

• Biased wording in job ads, reviews or interview questions.
• Plans with no owner, timing or way to check progress.
• Treating a template as legal advice.

What a good result looks like

An example, not your task: A promising idea looks rough and someone wants to judge it as if it were finished.

• Step 1: Who pulls on the idea. A table of each group, what it wants, how it pulls and where it steers the idea.
• Step 2: Early or broken. A timeline, a test of how notes changed the idea, a read on team belief, then the call and a date to look again.
• Step 3: The plan that shields it. What is protected, who sees it, which questions are allowed, who pays and the date and test for the hand-off.
• Hand-back summary. Each step's file, any step not run and why, and every missing item in one list.

How the work is checked

• The idea is compared with its own earlier versions, not with finished work.
• The call is one of the four options and has a date and a "flips if" line.
• The belief of the people on the work is covered with evidence or a MISSING: line.
• Each protector and each group kept away has a reason about the idea's state.
• 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.

A second opinion

Before it hands back, your AI reviews the draft the way Ed Catmull and Mary Barra would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Maps the pull. Lists every group that needs something from the idea, what each wants, and where a schedule or target has started to decide what the idea becomes.
• Judges early or broken. Compares the idea with its own past, checks what changed after each round of notes and reads whether the team still believes.
• Makes the call. Picks keep protecting, change the approach, change the lead or stop, with a date and what would flip it.
• Writes the shield. Chooses protectors, limits questions to the stage, names who pays and answers each pressure group.
• Plans the hand-off. Sets the date and test for moving from protection to meeting the rest of the business.

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 protect-new-idea 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/protect-new-idea/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

• The idea, who leads it and how long it has run
• The groups that need output or approval from it
• Its rounds so far, with dates and what changed (strongly better)

Tools and access

• Any good chat AI: It reasons about people, rewards and plans in text, which any strong chat AI handles with this skill.
• A spreadsheet: Easier to try a new pay rule on past numbers and see what it would have paid.
• Any good chat AI: Weighing signs and making a reasoned call is text work any strong chat AI does well with this skill.
• A project log: Dated versions and review notes let it judge the trend.
• Any good chat AI: Writing a plan with clear reasons is text work any strong chat AI does well with this skill.
• A shared calendar: Review and hand-off dates belong where everyone can see them.

Functions and deliverables

• Early product idea test planner: Share your rough idea, progress and pressures. Get an incentive map, early-or-flawed assessment and a time-limited development plan.
  • A map of who pulls on the idea and where the pull has started to steer it
  • A call to keep protecting, change the approach, change the lead or stop, with evidence and a date to look again
  • A protection plan with who sees it, which questions are allowed, who pays and the hand-off date and test
• Incentive checker: Check your pay plan or deal with this incentive checker. See who is rewarded for what, where it pulls the wrong way, and get a fix.
  • A table of people, rewards and the behaviour each really encourages
  • Each mismatch with a concrete example
  • A fix that pays for the outcome you want, with a loophole check
  • A note on pay fairness and on which work is routine and which is thinking
• Early project progress reviewer: Review an unfinished project against its earlier versions. Get a proposed keep, change or stop decision, the evidence behind it and a review date.
  • A dated timeline, judged against the project's own earlier versions
  • A result for the notes test: what changed after each round
  • A read on whether the team still believes, or the one private question to ask each person
  • One of four calls: keep protecting, change the approach, change the lead or stop
  • The evidence, a date to look again and what would flip the call
• Early idea protection planner: Share the idea review and outside pressures. Set who sees it, what feedback fits, proposed funding and when wider review begins.
  • Who sees the idea now, who does not, and the reason for each
  • The only questions allowed at this stage, and the line to say to anyone who asks more
  • Time and money from a named payer, with a review date
  • A line for each pressure group
  • The hand-off date, test and first group to meet the idea
• 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
• Ed Catmull: Plan feedback or protect rough creative work using Ed Catmull’s recorded approach. Name the problem, keep the creator’s choice and find hidden issues.
  • Your problem worked on the way Ed Catmull would: their questions, their method, their push-back
  • The answer or the work, in Ed Catmull's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Mary Barra: Plan a crisis update using Mary Barra’s recorded approach. Start with affected people, state known facts and name owners for the work.
  • Your problem worked on the way Mary Barra would: their questions, their method, their push-back
  • The answer or the work, in Mary Barra's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• A promising idea looks rough and someone wants to judge it as if it were finished.
• Deadlines or sales targets are pulling a new project off course.
• You can't tell if a struggling project needs patience or a hard decision.

Limits to check before starting

• Your work is finished and ready to ship: use a standard project review with your team instead.
• You have a single task to check, not an idea under pressure: use the Advice credibility checker to test the advice you were given.
• The idea has no history and no people on it yet: write a short brief first, then come back once there is a first version to judge.

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".
• Give step 1 the idea and the groups around it. Give step 2 the version history if you have it.
• If the call is not keep protecting, step 3 still runs but says the plan only applies if you choose to carry on.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/protect-new-idea 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.