Hire an AI OrgScript model designer

Everything it can hand back

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

• A .orgs file with a process, and rule, role, policy or state flow blocks where needed
• A list of assumptions and questions about unclear steps
• A Mermaid flowchart and a short plain summary of the process
• The exact commands to format and check the file, and their result if your AI could run them

How it does the job well

• Say what you ran and what you did not. You cannot run the OrgScript tool unless the host gives you a way.
• Do not claim the file is valid until a check has passed.
• Targets in the profile, such as test coverage, are goals. Do not report them as results.
• Ask before changing a live system or a shared repository.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You have a written procedure and want it as a clean file that an AI can follow.

• Process file (.orgs). Your process as strict text, with its trigger, conditions, notifications and status changes.
• Questions and assumptions. Each unclear step, what you must confirm, and any assumption used.
• Mermaid diagram. A flowchart of the process, marked as hand-written or tool-made.
• Plain summary. The process in a few lines, for a manager to compare with the real procedure.
• Check status. The format, validate and check commands, and whether each was run or not.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• 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 Kent Beck would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Read the procedure. It finds the trigger, the conditions, the roles, the state changes and where the process stops.
• Match it to what OrgScript allows. It checks each step against the supported blocks and statements, so the file stays a description, not a program.
• Draft the file. It writes the .orgs file with strict indentation, short lines and names a person can read.
• Flag gaps. Any step with no rule or no owner becomes a question, not a guess.
• Check the file. It gives the format, validate and check commands. If it can run them, it reports the result. If not, it marks the file unchecked.
• Export and explain. It writes a Mermaid diagram and a plain summary, and says if they were hand-written.

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 engineering-orgscript-engineer 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/engineering-orgscript-engineer/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 procedure as text, such as an SOP, an email thread or meeting notes
• What starts the process, and who takes part
• The rules with their numbers, such as "under $1,000 is disqualified"
• Your OrgScript spec or grammar file, if you have one (optional)
• An existing .orgs file to fix or review (optional)

Helpful context (optional)

• The OrgScript spec or grammar file.
• Two or three real cases that the process should handle, including an odd one.
• The names your team uses for roles and statuses.

Tools and access

• Claude, ChatGPT or Gemini with file upload: They can read a long SOP and keep your rules and names straight.
• The OrgScript command line tool: The profile uses it to format, validate and check files and to export diagrams.

Functions and deliverables

• OrgScript model designer: Turn a written procedure into an OrgScript process file with triggers, rules, roles and state changes, plus a plain check. Bring your SOP.
  • A .orgs file with a process, and rule, role, policy or state flow blocks where needed
  • A list of assumptions and questions about unclear steps
  • A Mermaid flowchart and a short plain summary of the process
  • The exact commands to format and check the file, and their result if your AI could run them
  Source: Michael Sitarzewski and Agency Agents contributors.
• Process and SOP writer: Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.
  • A step-by-step written procedure
  • A RACI table
  • A process flow
  • An exceptions and edge cases table
  • Metrics to track the process
  Source: Anthropic.
• Plain-text file reader code planner: Name a code file in your project. Claude Code explains it block by block in plain English, then sums up what the file does in one paragraph.
  • The file split into blocks, each with its line range, one of five labels and a plain English explanation
  • A one-paragraph summary: what the file is for, what goes in and what comes out
  • A short list of things this file does not show, such as which files call it
• Email automation gaps and trigger reviewer: Review a store’s email flows, triggers and timing. Get missing steps, possible rule conflicts and a house score based only on what was shown.
  • A score out of 100, with how it was worked out
  • Missing flow candidates, prioritized using available recipients and results
  • Trigger, filter and timing errors, each with a fix
  • The order to build or rework them
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck'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 have a written procedure and want it as a clean file that an AI can follow.
• You want lead routing, approval or refund rules written down as exact steps.
• You already use OrgScript and want a process, rule or state flow reviewed.
• You want a Mermaid flowchart of a process from its text.

Limits to check before starting

• You only want the procedure written clearly in plain words. Use the Engineering documentation writer.
• You want to design the software behind a process. Use the Software architect.
• You don't use OrgScript and don't plan to. A plain checklist is simpler.

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 pack and add it to your AI as a skill. Or open a new chat and paste SKILL.md, then references/source-agent.md.
• Paste your procedure. Add what starts it, who is involved and the rules with their numbers.
• If you have the OrgScript spec or grammar file, paste it too. Without it, the agent uses only what the profile lists.
• Answer the questions it asks. Don't let it guess a rule you haven't given.
• Run the format, validate and check commands on the file yourself, unless your AI can run them. They need the OrgScript command line tool, which this pack does not include. Without it, the check status reads "not run".
• Read the plain summary back against your real procedure before you share the file.

Read it as data

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