Hire an AI business positioning roadmap planner

Everything it can hand back

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

• One position, a list of what you will not do and the activities that must fit
• Three to five customer problems, each with a result you can measure and an owner
• The plan rebuilt from the end date, with a score out of 100
• A list of ways it could fail and one change for each gap

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: You list what you offer and keep adding to it.

• Step 1 file: position. Better versus different, the chosen position, the price stance, the not-do list and the activities that must fit.
• Step 2 file: roadmap of results. Three to five customer problems, each with a result to measure, an owner and a review point.
• Step 3 file: backward check. The end goal, steps worked back from it, two cases, a second method, return paths and a score out of 100.
• Step 4 file: failure review. Ways the plan could fail, how well it covers each, risks that could end it, and one change per gap.
• 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.

A second opinion

Before it hands back, your AI reviews the draft the way Michael Porter and Charlie Munger would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Choose a position and what you will not do. Separates doing better from doing different, picks one position that fits the facts, writes at least four things you will not do and lists the activities that carry it.
• Rewrite the activities as a roadmap of results. Marks each item as a feature, a problem or a result, rewrites features as problems for named customers and gives each one a number and an owner, with review points in place of dates.
• Rebuild the roadmap from the end date. Starts at the end date and works back to this week, checks the answer a second way, tests small input changes, adds backup routes and scores the plan out of 100.
• List the ways it could fail and fix them. Lists what would guarantee failure, checks the plan against each item, marks risks that could end it and writes one change for each exposed gap.

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 set-your-position-and-turn-it-into-a-checked-roadmap 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/set-your-position-and-turn-it-into-a-checked-roadmap/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

• What you offer and who you serve
• Your main rivals (optional)
• Your end date and the result you want by then
• Your current feature or task list with dates (optional)

Tools and access

• Claude, ChatGPT or Gemini: Choosing a position and testing ideas against it is text work. No files, web access or paid tools needed.
• Any good chat AI: Sorting and rewriting a list is text work that any strong chat AI does with this skill.
• A spreadsheet: Holds the result numbers you track at each review point.
• Any good chat AI: Backward planning and a second-method check are text and arithmetic work any strong chat AI can do.
• A spreadsheet: Lets you rerun the small-changes table with your own numbers.
• Any good chat AI: Listing and testing failure modes is text reasoning that any strong chat AI handles with this skill.
• A spreadsheet: Handy for putting numbers on dependencies, cash and runway.

Functions and deliverables

• Business positioning roadmap planner: Share your offer, audience and planning limits. Get a position, trade-offs, measurable roadmap and a review of timing and failure risks.
  • One position, a list of what you will not do and the activities that must fit
  • Three to five customer problems, each with a result you can measure and an owner
  • The plan rebuilt from the end date, with a score out of 100
  • A list of ways it could fail and one change for each gap
• Strategy trade-off planner: Choose a business position that rivals cannot copy. Get a one-line position, a not-do list and a yes or no on every new idea.
  • A split of what makes you better from what makes you different
  • A position in one sentence, with who it is for
  • Whether it leads to a premium price or lower cost, and why
  • A not-do list, each line with what it gives up
  • A fit check of your activities and a yes or no on each new idea
• Product outcome roadmap planner: Turn a feature roadmap into outcomes. Paste your features and dates. Get three to five customer problems, each with a result you can measure.
  • Each item marked as a feature, a problem or a result
  • Three to five problems, each for a named customer
  • One measurable result per problem
  • Review points in place of dates, with the evidence each needs
• Backwards planning checker: Check your plan from the end date back. Paste your goal and plan to get a second-method check, a backup route and a score out of 100.
  • The plan rebuilt from the end point back to the first step
  • A second-method check with the gap between the two answers explained
  • A table of small input changes and how far each moves the result
  • A return path, a backup, and a score out of 100 with how it was worked out
• Plan failure reviewer: Find the ways your plan could fail before you commit. Paste your plan and goal, and get ranked failure risks with a fix for each.
  • The goal in one line
  • A list of failure modes specific to your plan, survival risks first
  • A change to the plan for each failure
  • The bet stated, and a set of attacks for the people you pick to argue against it
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.
• Michael Porter: Review a business strategy using Michael Porter’s recorded tools. Compare industry forces, choose a clear position and check which activities support it.
  • Your problem worked on the way Michael Porter would: their questions, their method, their push-back
  • The answer or the work, in Michael Porter's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Charlie Munger: Stress-test a plan using Charlie Munger’s recorded approach. Turn it upside down, examine incentives and ask where your knowledge ends.
  • Your problem worked on the way Charlie Munger would: their questions, their method, their push-back
  • The answer or the work, in Charlie Munger'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

• You list what you offer and keep adding to it.
• You have a roadmap of features and cannot say what it should change.
• You must show a board, partner or bank that the plan holds.

Limits to check before starting

• You plan one campaign or one launch: use the Big problem splitter to break it into smaller parts.
• You only want to know if your edge holds up against rivals: use the Competitive advantage tester.
• You need a single yes or no on one choice: use the Plan objection writer, or ask a trusted adviser.

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 four skill files, in the order they run: Strategy trade-off planner, Product outcome roadmap planner, Backwards planning checker and Plan failure reviewer.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project, which can need a paid plan) and say "Follow HANDOFF.md".
• State your end date and the result you want in plain numbers at the start. Step 3 needs both.
• Tell it about any commitment you cannot drop, so the not-do list stays honest.
• Read the failure list last and decide which changes to make before you share the roadmap.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/set-your-position-and-turn-it-into-a-checked-roadmap 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.