Skip to content

Build Your AI Workflow

Part of: AI Workflow Framework

Build turns your approved Design Plan into a working workflow on your platform. It works through the plan’s tasks in order, checks each one against what it must do, and installs the workflow where it will run.

Build works in three parts. Most of your part comes first; after that, Build asks you to confirm where changes land, answer the workflow’s checkpoints as you would at work, and install it:

  1. Your setup — you set up the workflow’s own place with Build’s steps (nothing to do on Claude Code, Codex or Copilot Cowork), connect each tool in your account (Build reads something back to prove it’s the right one), and Build places the context files the workflow reads. With your OK, Build makes one quick real check of each kind of change: one small real change somewhere only you can see. It also asks whether an older version of the workflow is already set up, so the two never run side by side.
  2. Building and checking — Build builds each task in your plan and checks it with a dry run, showing every change instead of making it.
  3. Save it and test — Build saves or installs the workflow where it runs, keeps a copy, writes your build record, and gives you the phrase to start Test.
  • Your workflow: its skills and agents, installed where it runs, each with a practice-run mode: start a run with “practice run” and it shows each change instead of making it. Practice runs are built never to send or change anything; if your platform asks you to approve a send or a change during one, choose Deny (or your platform’s refuse button).
  • Your build record: build-record.md in framework/<workflow>/ in your working folder, saying what was built and what it can access.

Say “run the build skill” with where your files are, for example “run the build skill. My files are in Google Drive, in ai-workspace/framework/weekly-status-report.” On Claude Code you can also type /handsonai:build.

  • Instructions come from your requirements. Build writes the workflow’s instructions from your requirement lines and the rules that must always hold, so every part can be checked against what it must do.
  • On Microsoft 365 Copilot, agents are built in Agent Builder. Skills are made in Copilot Cowork, where you run Build. For an agent, Build writes a short prompt; you open Copilot › Chat › Agents › New agent and paste it into the Agent Builder chat, add the context files Build names under Knowledge, check that only what the workflow uses is switched on under Work content, choose Create, and paste the agent’s instructions back into Build’s chat, so Build can check they kept the lines every practice run needs. The ordinary Copilot Chat can describe an agent but can’t create one.

Next: Test runs your workflow on practice inputs and one new input it hasn’t seen.