Hire an AI shop operations and expansion planner

Everything it can hand back

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

• Standards with numbers and a list of what you never cut
• A job card for each role, a missed-standard rule and a day-one trial sheet
• A list of gaps from the trial, each with a fix
• A check that the first location earns without you, and a go or no-go on the next one

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: One location works well and you want a second, a partner or a franchisee to run it the same way without you.

• Standards. Yes-or-no standards with numbers, the lines you never cut and one job for each person.
• Manual. A job card for each role, a rule for missed standards and a trial sheet for the newcomer.
• Ready to copy check. The gaps from the trial with a fix for each, and whether the first place earns without you.
• Go or no-go. A go or no-go on the next location, a halfway check and the first fix to make.
• HAND-BACK SUMMARY. Each step's file, any step not run 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 Ray Kroc and Clayton Christensen would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Writes the standards. Walks the customer's path from order to hand-off and turns quality, service, cleanliness and value into yes-or-no standards with numbers.
• Turns them into a manual. One job card per role, in order, with a done-when check on each step, a missed-standard rule and a trial sheet.
• Pauses for a real trial. A person who has never worked for you runs a shift from the manual. You write down every stop, question and guess.
• Checks it is ready to copy. Sorts the trial notes into gaps with fixes, checks the first location earns without you, and checks the site, supplies and the named person.
• Makes the call. Checks the plan for known faults, sets a halfway check and says go or no-go.

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 shop-system-playbook 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/shop-system-playbook/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 sell and how a customer gets it, from order to hand-off
• Your roles and what each person does in a shift
• Takings and costs for a week you were away, if you have them (optional)

Helpful context (optional)

• Your opening and closing routines
• Takings and costs for a week you were away
• Photos of what done looks like

Tools and access

• Claude: Holds four steps, your numbers and the trial notes in one run.
• A phone camera: A photo of what done looks like settles most arguments about a step.
• Any good chat AI: Sorting plain rules into checkable form is text work any strong chat AI does well with this skill.
• A printed clipboard: The visit check works best on paper, carried through the place.
• Any good chat AI: Turning a standards sheet into ordered steps is writing work any strong chat AI does well.
• A phone camera: A short photo of what done looks like settles most arguments about a step.
• Claude, ChatGPT or Gemini: Sorting notes into gaps and running a fixed list of checks is reasoning work. No files, web access or paid tools needed.
• Your till or sales report: Takings for a week you were away turn the first check into a number.
• Any good chat AI: Checking a plan against a fixed list of faults is text work any strong chat AI does well with this skill.

Functions and deliverables

• Shop operations and expansion planner: Share how your best location works and its results. Get standards, role guides and an expansion review after a real newcomer trial.
  • Standards with numbers and a list of what you never cut
  • A job card for each role, a missed-standard rule and a day-one trial sheet
  • A list of gaps from the trial, each with a fix
  • A check that the first location earns without you, and a go or no-go on the next one
• Repeatable standards sheet writer: Turn how you make your product or service into a one-page standards sheet with yes-or-no checks, so it feels the same every time.
  • A one-page standards sheet with yes-or-no checks
  • A never-cut list and one job per role
  • A training plan and a ten-minute visit check
• Operations manual writer: Turn your standards sheet into an operations manual: one job card per role, a missed-standard rule and a day-one trial sheet for a newcomer.
  • One job card per role, with ordered steps and numbers
  • A missed-standard rule for each key standard
  • A list of what is fixed and what a local owner may change
  • A day-one trial sheet that records every place a newcomer stops
• Second location readiness checker: See if your business runs without you before opening a second location. Get trial gaps, a fix list and a ready or not yet call.
  • Each trial note sorted into a gap, with a one-line fix
  • A check that the first location earns without you on site
  • A check on the second site, its supplies and who runs it
  • A call of ready, ready with fixes or not yet
  • A fix list in order, with an owner and a date for each
• Go or no-go launch checker: Check a launch plan against six faults and three readiness checks. Get a go, wait or no verdict and a fix list before you spend.
  • Each of six faults marked present, absent or missing, with a reason from your plan
  • Three halfway checks answered yes, no or missing
  • One verdict, go, wait or no, with the single reason that decided it
  • A fix list for each fault found, and what would turn a wait into a go
• 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.
• Ray Kroc: Plan shop operations using Ray Kroc’s recorded approach. Write the basics, try them in one place and check costs before copying the system.
  • Your problem worked on the way Ray Kroc would: their questions, their method, their push-back
  • The answer or the work, in Ray Kroc's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Clayton Christensen: Explore why customers buy using Clayton Christensen’s recorded approach. Start with a real situation, the struggle and what the buyer used before.
  • Your problem worked on the way Clayton Christensen would: their questions, their method, their push-back
  • The answer or the work, in Clayton Christensen'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

• One location works well and you want a second, a partner or a franchisee to run it the same way without you.
• A new hire keeps asking you things that should be written down.
• You are about to hire a manager and hand over the keys.

Limits to check before starting

• You run one site and will never copy it: use a plain staff checklist for each role instead.
• Your work has no repeatable steps, such as custom one-off projects: write notes on how you decide, not a manual.
• You only need to check a launch plan for faults: use the Rapid growth readiness reviewer.

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: Repeatable standards sheet writer, Operations manual writer, Second location readiness checker and Go or no-go launch checker.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Describe your business and your roles. It works step by step and saves each result.
• At the pause, print the trial sheet, have a newcomer run one shift, and write down every stop. Bring the notes back.

Read it as data

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