@vpxa/aikit 0.1.107 → 0.1.108

package/scaffold/dist/adapters/claude-code.mjs

@@ -1,5 +1,5 @@
-import{AGENTS as e}from"../definitions/agents.mjs";import{AGENT_BODIES as t}from"../definitions/bodies.mjs";import{HOOKS as n}from"../definitions/hooks.mjs";import{MCP_SERVER_ENTRY as r,SERVER_NAME as i}from"../definitions/mcp.mjs";import{CLAUDE_MODELS as a}from"../definitions/models.mjs";import{PROMPTS as o}from"../definitions/prompts.mjs";import{PROTOCOLS as s}from"../definitions/protocols.mjs";import{buildAgentTable as c,buildHooksSection as l,buildInlineAgentSection as u,buildMcpConfigJson as d,buildPromptSections as f}from"./_shared.mjs";const p=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow_status` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow_step({ action: 'next' })`.","Use `flow_list` to see available flows and `flow_start` to begin one."].join(`
-`),m=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow_status` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow_step({ action: 'next' })`.","Use `flow_list` to see available flows and `flow_start` to begin one."].join(`
+import{AGENTS as e}from"../definitions/agents.mjs";import{AGENT_BODIES as t}from"../definitions/bodies.mjs";import{HOOKS as n}from"../definitions/hooks.mjs";import{MCP_SERVER_ENTRY as r,SERVER_NAME as i}from"../definitions/mcp.mjs";import{CLAUDE_MODELS as a}from"../definitions/models.mjs";import{PROMPTS as o}from"../definitions/prompts.mjs";import{PROTOCOLS as s}from"../definitions/protocols.mjs";import{buildAgentTable as c,buildHooksSection as l,buildInlineAgentSection as u,buildMcpConfigJson as d,buildPromptSections as f}from"./_shared.mjs";const p=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow({ action: 'step', advance: 'next' })`.","Use `flow({ action: 'list' })` to see available flows and `flow({ action: 'start', name, topic })` to begin one."].join(`
+`),m=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow({ action: 'step', advance: 'next' })`.","Use `flow({ action: 'list' })` to see available flows and `flow({ action: 'start', name, topic })` to begin one."].join(`
 `);function h(e,t){let n=[];return n.push(`# aikit ${e}`),n.push(``),t.description&&(n.push(`> ${t.description}`),n.push(``)),n.push(t.content.trim()),n.push(``),n.join(`
 `)}function g(e,n){let r=t[e];return typeof r==`function`?r(n):r||``}function _(e){let t=[];e.extraBody&&t.push(e.extraBody),e.sharedBase&&s[e.sharedBase]&&t.push(s[e.sharedBase]);for(let n of e.sharedProtocols||[])s[n]&&t.push(s[n]);return t}function v(t){let n=[];for(let[r,i]of Object.entries(e)){let e=g(r,t),a=_(i);if(i.variants){for(let[t,o]of Object.entries(i.variants))n.push(u({name:`${r}-${t}`,title:i.title,description:o.description||i.description,body:e,skills:i.skills,additionalSections:[...a,o.bodyAddendum].filter(Boolean)}));continue}let o=[...a];r===`Orchestrator`&&o.push(p,m),n.push(u({name:r,title:i.title,description:i.description,body:e,skills:i.skills,additionalSections:o}))}return n.join(`
 `)}function y(){let t=c(e,a);return[`# aikit — Claude Code Instructions`,``,"This project uses an MCP server (`aikit`) providing tools for search, analysis, memory, and validation.",``,`## MCP Server`,``,"Server name: `aikit`","Configured in `.mcp.json` (already done if scaffold was deployed).",``,`## Agents`,``,t,``,`## Agent Instructions`,``,v(t),`## Prompts`,``,f(o),``,`## Session Protocol`,``,l(n),``].join(`

package/scaffold/dist/adapters/copilot.mjs

@@ -1,4 +1,4 @@
-import{AGENTS as e}from"../definitions/agents.mjs";import{AGENT_BODIES as t}from"../definitions/bodies.mjs";import{COPILOT_MODELS as n,VARIANT_GROUPS as r}from"../definitions/models.mjs";import{PROMPTS as i}from"../definitions/prompts.mjs";import{PROTOCOLS as a,TEMPLATES as o}from"../definitions/protocols.mjs";import{IDE_CAPABILITIES as s}from"../definitions/tools.mjs";const c={terminal:`execute/runInTerminal`,problems:`read/problems`,readFile:`read/readFile`,lastCommand:`read/terminalLastCommand`,subagent:`agent/runSubagent`,createFile:`edit/createFile`,editFiles:`edit/editFiles`,rename:`edit/rename`,createDirectory:`edit/createDirectory`,search:`search/changes, search/codebase, search/usages`,web:`web/fetch, web/githubRepo`,todo:`todo`,memory:`vscode/memory`,newWorkspace:`vscode/newWorkspace`,reviewPlan:`vscode/reviewPlan`,askQuestions:`vscode/askQuestions`,resolveMemoryFileUri:`vscode/resolveMemoryFileUri`,runCommand:`vscode/runCommand`,switchAgent:`vscode/switchAgent`,killTerminal:`execute/killTerminal`,createTask:`execute/createAndRunTask`,terminalSel:`read/terminalSelection`,fileSearch:`search/fileSearch`,listDir:`search/listDirectory`,textSearch:`search/textSearch`,searchSubagent:`search/searchSubagent`,browser:`browser/openBrowserPage, browser/readPage, browser/screenshotPage, browser/navigatePage, browser/clickElement, browser/dragElement, browser/hoverElement, browser/typeInPage, browser/runPlaywrightCode, browser/handleDialog`};function l(e){return`[${[...(s[e]||[]).map(e=>c[e]).filter(Boolean),`aikit/*`].join(`, `)}]`}function u(e){let t=n[e];return t?Array.isArray(t)?t[0]||`Auto (copilot)`:t:`Auto (copilot)`}const d=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow_status` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow_step({ action: 'next' })`.","Use `flow_list` to see available flows and `flow_start` to begin one."].join(`
+import{AGENTS as e}from"../definitions/agents.mjs";import{AGENT_BODIES as t}from"../definitions/bodies.mjs";import{COPILOT_MODELS as n,VARIANT_GROUPS as r}from"../definitions/models.mjs";import{PROMPTS as i}from"../definitions/prompts.mjs";import{PROTOCOLS as a,TEMPLATES as o}from"../definitions/protocols.mjs";import{IDE_CAPABILITIES as s}from"../definitions/tools.mjs";const c={terminal:`execute/runInTerminal`,problems:`read/problems`,readFile:`read/readFile`,lastCommand:`read/terminalLastCommand`,subagent:`agent/runSubagent`,createFile:`edit/createFile`,editFiles:`edit/editFiles`,rename:`edit/rename`,createDirectory:`edit/createDirectory`,search:`search/changes, search/codebase, search/usages`,web:`web/fetch, web/githubRepo`,todo:`todo`,memory:`vscode/memory`,newWorkspace:`vscode/newWorkspace`,reviewPlan:`vscode/reviewPlan`,askQuestions:`vscode/askQuestions`,resolveMemoryFileUri:`vscode/resolveMemoryFileUri`,runCommand:`vscode/runCommand`,switchAgent:`vscode/switchAgent`,killTerminal:`execute/killTerminal`,createTask:`execute/createAndRunTask`,terminalSel:`read/terminalSelection`,fileSearch:`search/fileSearch`,listDir:`search/listDirectory`,textSearch:`search/textSearch`,searchSubagent:`search/searchSubagent`,browser:`browser/openBrowserPage, browser/readPage, browser/screenshotPage, browser/navigatePage, browser/clickElement, browser/dragElement, browser/hoverElement, browser/typeInPage, browser/runPlaywrightCode, browser/handleDialog`};function l(e){return`[${[...(s[e]||[]).map(e=>c[e]).filter(Boolean),`aikit/*`].join(`, `)}]`}function u(e){let t=n[e];return t?Array.isArray(t)?t[0]||`Auto (copilot)`:t:`Auto (copilot)`}const d=[`## Flows`,``,"This project uses aikit's pluggable flow system. Check flow status with the `flow` MCP tool.","If a flow is active, follow the current step's skill instructions. Advance with `flow({ action: 'step', advance: 'next' })`.","Use `flow({ action: 'list' })` to see available flows and `flow({ action: 'start', name, topic })` to begin one."].join(`
 `);function f(){let t=[];for(let[i,a]of Object.entries(e))if(a.variants)for(let e of r[i]||[]){let r=`${i}-${e}`,o=n[r]||n[i],s=Array.isArray(o)?o[0]:o||`Unknown`,c=(a.variants[e]||{}).description||a.description;t.push(`| **${r}** | ${c} | ${s} | ${a.category} |`)}else{let e=n[i],r=Array.isArray(e)?e[0]:e||`Unknown`;t.push(`| **${i}** | ${a.description} | ${r} | ${a.category} |`)}return`| Agent | Purpose | Model | Category |\n|-------|---------|-------|----------|\n${t.join(`
 `)}`}function p(e,t,n){let i=`${e}-${t}`,o=n.variants[t]||{},s=u(i),c=o.description||n.description,f=o.identity||(t===r[e]?.[0]?`, the primary ${e} agent.`:`, a variant of ${e}. Same responsibilities, different model perspective.`),p=n.sharedBase&&a[n.sharedBase]?`\n\n${a[n.sharedBase]}`:``,m=n.extraBody?`\n\n${n.extraBody}`:``,h=o.bodyAddendum?`\n\n${o.bodyAddendum}`:``,g=n.skills?.length?`\n\n## Skills (load on demand)\n\n| Skill | When to load |\n|-------|--------------|\n${n.skills.map(([e,t])=>`| ${e} | ${t} |`).join(`
 `)}`:``,_=n.title||e;return`---

package/scaffold/dist/definitions/bodies.mjs

@@ -70,14 +70,14 @@ This is the **proportional response** — match ceremony to complexity. Floor-ti
 
 ### Flow Activation (MANDATORY after bootstrap)
 
-1. \`flow_status\` — check for an active flow from a previous session
+1. \`flow({ action: 'status' })\` — check for an active flow from a previous session
 2. **If active flow exists:**
    - Note current step name and instruction path
-   - Read the current step instruction with \`flow_read_instruction\`
+   - Read the current step instruction with \`flow({ action: 'read' })\`
    - Follow its instructions
-   - When complete: \`flow_step({ action: 'next' })\`
+   - When complete: \`flow({ action: 'step', advance: 'next' })\`
 3. **If NO active flow:**
-   - \`flow_list\` — retrieve ALL available flows (builtin AND custom)
+   - \`flow({ action: 'list' })\` — retrieve ALL available flows (builtin AND custom)
    - **Auto-select** the flow when the task clearly matches:
 
      | Task signal | Auto-activate flow |
@@ -87,7 +87,7 @@ This is the **proportional response** — match ceremony to complexity. Floor-ti
      | New feature, API design, architecture change, multi-component work | \`aikit:advanced\` |
      | Task matches a custom flow's description/tags exactly | That custom flow |
 
-   - **Auto-start:** When exactly one flow matches, start it immediately — \`flow_start({ flow: '<matched>', topic: '<task description>' })\` — and inform the user which flow was activated and why. The \`topic\` becomes the \`.flows/\` directory name (slugified).
+   - **Auto-start:** When exactly one flow matches, start it immediately — \`flow({ action: 'start', name: '<matched>', topic: '<task description>' })\` — and inform the user which flow was activated and why. The \`topic\` becomes the \`.flows/\` directory name (slugified).
    - **Ask only when ambiguous:** If the task could fit multiple flows, or no flow clearly matches, present the options and let the user choose.
    - Do NOT present a menu for obvious cases. Speed matters.
 4. **Every Standard/Critical task goes through a flow.** Floor-tier tasks use the fast path above.
@@ -96,20 +96,20 @@ This is the **proportional response** — match ceremony to complexity. Floor-ti
 
 For EACH step in the active flow:
 
-1. \`flow_read_instruction\` — read the current step's README.md
+1. \`flow({ action: 'read' })\` — read the current step's README.md
 2. Follow the step's instructions — delegate work to the appropriate agents
 3. Apply **Orchestrator Protocols** (PRE-DISPATCH GATE, FORGE, review cycle) during execution
 4. When the step is complete and results are approved:
-   - \`flow_step({ action: 'next' })\` to advance
+   - \`flow({ action: 'step', advance: 'next' })\` to advance
 5. Repeat until all flow steps AND epilogue steps are complete
 
 **Epilogue steps** (mandatory, injected by aikit):
 - After the last flow step, the state machine transitions to epilogue steps (e.g., \`_docs-sync\`)
-- \`flow_status\` will show \`phase: 'after'\` and \`isEpilogue: true\` during epilogue
+- \`flow({ action: 'status' })\` will show \`phase: 'after'\` and \`isEpilogue: true\` during epilogue
 - Delegate epilogue work to the appropriate agent (e.g., Documenter for \`_docs-sync\`)
-- Epilogue steps follow the same execution pattern: \`flow_read_instruction\` → do work → \`flow_step({ action: 'next' })\`
+- Epilogue steps follow the same execution pattern: \`flow({ action: 'read' })\` → do work → \`flow({ action: 'step', advance: 'next' })\`
 
-**Custom flows work identically** — \`flow_list\` returns them alongside builtins. The execution loop is the same for ALL flows.
+**Custom flows work identically** — \`flow({ action: 'list' })\` returns them alongside builtins. The execution loop is the same for ALL flows.
 
 ### Design & Decision Detection (applies to ALL flows including custom)
 
@@ -133,8 +133,8 @@ Custom flows are NOT expected to reference these protocols in their step instruc
 Flows MUST be driven to completion. A flow left active forever blocks future work.
 
 **Normal completion:**
-- When the last flow step's \`flow_step({ action: 'next' })\` is called, the flow transitions to **mandatory epilogue steps** (e.g., \`_docs-sync\`)
-- Epilogue steps run automatically after every flow — they are NOT optional (but can be skipped with \`flow_step({ action: 'skip' })\` + warning)
+- When the last flow step's \`flow({ action: 'step', advance: 'next' })\` is called, the flow transitions to **mandatory epilogue steps** (e.g., \`_docs-sync\`)
+- Epilogue steps run automatically after every flow — they are NOT optional (but can be skipped with \`flow({ action: 'step', advance: 'skip' })\` + warning)
 - The \`_docs-sync\` epilogue loads the \`docs\` skill and updates \`docs/\` based on changes made during the flow
 - After ALL epilogue steps complete, the flow reaches \`completed\` status
 - After completion: run post-implementation protocol (\`check\` → \`test_run\` → \`blast_radius\` → \`reindex\`)
@@ -142,13 +142,13 @@ Flows MUST be driven to completion. A flow left active forever blocks future wor
 - Then continue with \`produce_knowledge\` → \`remember\`
 - Inform the user the flow is complete with a summary of artifacts produced
 
-**Stale flow detection** (check at session start when \`flow_status\` returns an active flow):
+**Stale flow detection** (check at session start when \`flow({ action: 'status' })\` returns an active flow):
 - If the active flow's current step has no matching work context in the conversation → **ask the user**: "A flow \`<name>\` is active at step \`<step>\`. Continue, or reset to start fresh?"
-- If the user says reset → \`flow_reset()\` then activate a new flow for the current task
+- If the user says reset → \`flow({ action: 'reset' })\` then activate a new flow for the current task
 - If the user says continue → resume from the current step
 
 **Abandoned step recovery:**
-- If a step has been attempted ≥ 2 times with \`BLOCKED\` status → escalate to user with diagnostics, offer to \`flow_step({ action: 'skip' })\` or \`flow_reset()\`
+- If a step has been attempted ≥ 2 times with \`BLOCKED\` status → escalate to user with diagnostics, offer to \`flow({ action: 'step', advance: 'skip' })\` or \`flow({ action: 'reset' })\`
 - Never silently retry a blocked step indefinitely
 
 **One active flow at a time.** To switch tasks, the current flow must be completed or reset first.
@@ -177,7 +177,7 @@ Batch 2 (after batch 1):
 2. **Goal** — acceptance criteria, testable
 3. **Arch Context** — varies by \`config.tokenBudget\`: efficient → \`stratum_card({tier:'T1'})\`, normal → \`compact({path, query})\`, full → \`digest({sources})\`. Default to efficient unless task complexity requires more.
 4. **Constraints** — patterns, conventions
-5. **Artifacts Path** — the active flow's run directory and artifacts path from \`flow_status\` (e.g. \`.flows/add-authentication/.spec/\`)
+5. **Artifacts Path** — the active flow's run directory and artifacts path from \`flow({ action: 'status' })\` (e.g. \`.flows/add-authentication/.spec/\`)
 6. **FORGE** — tier + task_id + evidence requirements (reviewers add CRITICAL/HIGH claims into your task_id; never create their own)
 7. **Self-Review** — checklist before declaring status
 
@@ -196,35 +196,26 @@ Reviewers add findings to the Orchestrator's existing \`evidence_map\` \`task_id
 
 | Tool | Purpose |
 |------|---------|
-| \`flow_list\` | List installed flows and active flow |
-| \`flow_info\` | Get detailed flow info including steps |
-| \`flow_start\` | Start a flow with a topic — creates \`.flows/{topic-slug}/\` run directory |
-| \`flow_step\` | Advance: next, skip, or redo current step |
-| \`flow_status\` | Check current execution state including slug, runDir, artifactsPath |
-| \`flow_reset\` | Abandon the active flow (preserves run directory for history) |
-| \`flow_read_instruction\` | Read the current step's instruction with \`{{artifacts_path}}\` resolved |
-| \`flow_runs\` | List all flow runs (current and past) with topic, status, progress |
-| \`flow_add\` | Install a new flow from a git URL, local path, or shorthand (e.g. "openspec") |
-| \`flow_remove\` | Remove an installed flow by name (builtin flows cannot be removed) |
-| \`flow_update\` | Update an installed flow to its latest version (git pull / npm update) |
+| \`flow\` | Manage flows — list, start, navigate steps, read instructions, inspect runs, and add/remove/update. Use the \`action\` parameter. |
 
 ### Multi-Root Workspace Support
 
 When the IDE workspace contains **multiple repository roots**, flows support cross-repo orchestration:
 
-**Detection:** \`flow_list\` and \`flow_status\` return \`allRoots\` — the list of all workspace roots. When \`allRoots.length > 1\`, the workspace is multi-root.
+**Detection:** \`flow({ action: 'list' })\` and \`flow({ action: 'status' })\` return \`allRoots\` — the list of all workspace roots. When \`allRoots.length > 1\`, the workspace is multi-root.
 
 **Single-repo task (default):** Omit the \`roots\` parameter — flow creates \`.flows/\` in the primary root only.
 
-**Multi-repo task:** Pass \`roots\` to \`flow_start\` listing ALL participating repositories:
+**Multi-repo task:** Pass \`roots\` to \`flow({ action: 'start', ... })\` listing ALL participating repositories:
 \`\`\`
-flow_start({
-  flow: "aikit:advanced",
+flow({
+   action: 'start',
+   name: 'aikit:advanced',
   topic: "cross-repo-auth",
   roots: ["E:/repos/api-gateway", "E:/repos/auth-service", "E:/repos/shared-types", "E:/repos/frontend"]
 })
 \`\`\`
-This creates \`.flows/cross-repo-auth/\` with synchronized \`meta.json\` in each listed root. Every \`flow_step\`, \`flow_reset\`, and state change is automatically replicated to all roots.
+This creates \`.flows/cross-repo-auth/\` with synchronized \`meta.json\` in each listed root. Every \`flow\` step/reset action and state change is automatically replicated to all roots.
 
 **Decision criteria for multi-root flows:**
 
@@ -371,12 +362,12 @@ This applies to YOU (the Orchestrator) when you use \`web_fetch\`/\`http\` direc
 ### Start (do ALL)
 
 \`\`\`
-flow_status({})                                                # Check/resume active flow FIRST
-# If flow active → flow_read_instruction({ step }) → follow step instructions
+flow({ action: 'status' })                                     # Check/resume active flow FIRST
+# If flow active → flow({ action: 'read', step }) → follow step instructions
 status({})                                                     # Check AI Kit health + onboard state
 # If onboard not run → onboard({ path: "." })                 # First-time codebase analysis
-flow_list({})                                                  # See available flows
-# Select flow based on task → flow_start({ flow: "<name>", topic: "<task>" })  # Start flow — creates .flows/{topic}/
+flow({ action: 'list' })                                       # See available flows
+# Select flow based on task → flow({ action: 'start', name: "<name>", topic: "<task>" })  # Start flow — creates .flows/{topic}/
 knowledge({ action: "list" })                                 # See stored knowledge
 search({ query: "SESSION CHECKPOINT", origin: "curated" })     # Resume prior work
 \`\`\`
@@ -399,9 +390,9 @@ search({ query: "SESSION CHECKPOINT", origin: "curated" })     # Resume prior wo
 
 ## Flows
 
-This project uses aikit's pluggable flow system. Check flow status with the \`flow_status\` MCP tool.
-If a flow is active, follow the current step's instructions. Advance with \`flow_step({ action: 'next' })\`.
-Use \`flow_list\` to see available flows and \`flow_start\` to begin one.
+This project uses aikit's pluggable flow system. Check flow status with the \`flow\` MCP tool.
+If a flow is active, follow the current step's instructions. Advance with \`flow({ action: 'step', advance: 'next' })\`.
+Use \`flow({ action: 'list' })\` to see available flows and \`flow({ action: 'start', name, topic })\` to begin one.
 `,Planner:`**Read \`AGENTS.md\`** in the workspace root for project conventions and AI Kit protocol.
 
 Load the \`aikit\` skill for full tool documentation, workflow chains, and session protocol.
@@ -437,13 +428,13 @@ Load the \`aikit\` skill for full tool documentation, workflow chains, and sessi
 The Planner is typically activated by the Orchestrator as part of a flow step (e.g., \`aikit:advanced\` plan step, \`aikit:basic\` assess step, or a custom flow's planning step).
 
 **When activated as part of a flow:**
-1. \`flow_status\` — check current step context and which flow is active
-2. \`flow_read_instruction\` — read the current step's README.md for specific instructions
+1. \`flow({ action: 'status' })\` — check current step context and which flow is active
+2. \`flow({ action: 'read' })\` — read the current step's README.md for specific instructions
 3. Follow the step's instructions as the primary guide, applying Planner methodology on top
 4. Read the flow's README.md for overall context on how the flow works
 5. Produce required artifacts (as specified by the flow step's \`produces\` field)
 6. When complete, report status to Orchestrator: \`DONE\` | \`DONE_WITH_CONCERNS\` | \`NEEDS_CONTEXT\` | \`BLOCKED\`
-7. Do NOT call \`flow_step\` — the Orchestrator controls flow advancement
+7. Do NOT advance the flow with \`flow\` — the Orchestrator controls flow advancement
 
 **When no flow is active** (standalone mode), operate autonomously following normal Planner methodology.
 

package/scaffold/dist/definitions/flows.mjs

@@ -17,7 +17,7 @@ Load the \`docs\` skill before proceeding — it contains the full documentation
 Read all artifacts produced during this flow — they contain design decisions, requirements, and verification results that are the most valuable documentation input.
 
 \`\`\`
-flow_status()                                           # Get artifactsPath
+flow({ action: 'status' })                             # Get artifactsPath
 find({ pattern: "*.md", path: "{{artifacts_path}}" })   # Discover all flow artifacts
 digest({ sources: [                                     # Compress artifacts for context
   { path: "<found-artifact-1>" },
@@ -117,7 +117,7 @@ If the flow's changes don't warrant doc updates (e.g., pure bug fix with no reve
 - [ ] \`docs/\` bootstrapped with tool outputs if it didn't exist
 - [ ] Relevant docs created or updated (or skipped with reason)
 - [ ] \`docs/README.md\` index is current
-- [ ] No placeholder/empty docs created — all content tool-generated or hand-written with purpose`}],"aikit-advanced":[{file:`README.md`,content:"# aikit:advanced — Full Development Flow\n\nFull development flow for **new features, API design, and architecture changes**.\n\n## Steps\n\n| # | Step | Skill | Produces | Requires | Agents |\n|---|------|-------|----------|----------|--------|\n| 1 | **Design Gate** | `steps/design/README.md` | `design-decisions.md` | — | Researcher-Alpha/Beta/Gamma/Delta |\n| 2 | **Specification** | `steps/spec/README.md` | `spec.md` | `design-decisions.md` | Researcher-Alpha |\n| 3 | **Planning** | `steps/plan/README.md` | `plan.md` | `spec.md` | Planner, Explorer |\n| 4 | **Task Breakdown** | `steps/task/README.md` | `tasks.md` | `plan.md` | Planner, Architect-Reviewer-Alpha |\n| 5 | **Execution** | `steps/execute/README.md` | `progress.md` | `tasks.md` | Orchestrator, Implementer, Frontend, Refactor |\n| 6 | **Verification** | `steps/verify/README.md` | `verify-report.md` | `progress.md` | Code-Reviewer-Alpha/Beta, Architect-Reviewer-Alpha/Beta, Security |\n\n## How It Works\n\nEach step has a **README.md** file that contains the detailed instructions for the agent(s) executing that step. The Orchestrator reads the README.md via `flow_read_instruction` and delegates work accordingly.\n\n### Step 1: Design Gate\n- Full brainstorming session for new features and architectural changes\n- FORGE classification (`forge_classify`) + grounding (`forge_ground`) for complex tasks\n- Full 3-phase multi-model decision protocol for non-trivial technical decisions (see Orchestrator's inlined Multi-Model Decision Protocol)\n- ADR generation for critical-tier tasks\n- **Mandatory user stop** before proceeding — design decisions must be approved\n- Read `steps/design/README.md` for the full protocol\n\n### Step 2: Specification\n- Elicit requirements from the user, clarify scope\n- Define acceptance criteria and constraints\n- Build on design decisions from the previous step\n\n### Step 3: Planning\n- Deep codebase analysis using `search`, `scope_map`, `trace`, `analyze_*`\n- Design architecture based on spec and design decisions\n- Create comprehensive implementation plan with file-level changes\n\n### Step 4: Task Breakdown\n- Break the plan into ordered, atomic implementation tasks\n- Define dependencies between tasks\n- Identify parallel batches for multi-agent execution\n- Architecture review of the task structure\n\n### Step 5: Execution\n- Orchestrator dispatches agents in parallel batches per the task breakdown\n- Each agent gets a scoped task (1-3 files) with clear acceptance criteria\n- TDD: write tests first, then implement\n- Per-batch review cycle: Code Review (dual) → Arch Review → Security → Evidence Gate\n\n### Step 6: Verification\n- Dual code review (Code-Reviewer-Alpha + Beta)\n- Architecture review (Architect-Reviewer-Alpha + Beta)\n- Security review\n- Run `check({})` + `test_run({})` + `blast_radius({})`\n- `evidence_map({ action: \"gate\" })` for final quality gate\n\n## Using Skills Inside Steps\n\nWhen the Orchestrator activates a step:\n\n1. **Read the instruction first** — `flow_read_instruction` returns the README.md for the current step\n2. **Follow step instructions** — the README.md is the primary guide for what to do\n3. **Delegate to listed agents** — each step lists which agents are appropriate\n4. **Produce the required artifact** — the step's `produces` field specifies what file to create in the artifacts directory\n5. **Check dependencies** — the step's `requires` field lists artifacts from previous steps that must exist\n6. **Report status** — agents report `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED` to the Orchestrator\n\n## Artifacts\n\nAll artifacts are stored in the run directory under `.flows/{topic}/`. The template variable `{{artifacts_path}}` resolves to the actual path at runtime.\n"},{file:`steps/design/README.md`,content:`# Design Gate — Advanced Flow
+- [ ] No placeholder/empty docs created — all content tool-generated or hand-written with purpose`}],"aikit-advanced":[{file:`README.md`,content:"# aikit:advanced — Full Development Flow\n\nFull development flow for **new features, API design, and architecture changes**.\n\n## Steps\n\n| # | Step | Skill | Produces | Requires | Agents |\n|---|------|-------|----------|----------|--------|\n| 1 | **Design Gate** | `steps/design/README.md` | `design-decisions.md` | — | Researcher-Alpha/Beta/Gamma/Delta |\n| 2 | **Specification** | `steps/spec/README.md` | `spec.md` | `design-decisions.md` | Researcher-Alpha |\n| 3 | **Planning** | `steps/plan/README.md` | `plan.md` | `spec.md` | Planner, Explorer |\n| 4 | **Task Breakdown** | `steps/task/README.md` | `tasks.md` | `plan.md` | Planner, Architect-Reviewer-Alpha |\n| 5 | **Execution** | `steps/execute/README.md` | `progress.md` | `tasks.md` | Orchestrator, Implementer, Frontend, Refactor |\n| 6 | **Verification** | `steps/verify/README.md` | `verify-report.md` | `progress.md` | Code-Reviewer-Alpha/Beta, Architect-Reviewer-Alpha/Beta, Security |\n\n## How It Works\n\nEach step has a **README.md** file that contains the detailed instructions for the agent(s) executing that step. The Orchestrator reads the README.md via `flow({ action: 'read' })` and delegates work accordingly.\n\n### Step 1: Design Gate\n- Full brainstorming session for new features and architectural changes\n- FORGE classification (`forge_classify`) + grounding (`forge_ground`) for complex tasks\n- Full 3-phase multi-model decision protocol for non-trivial technical decisions (see Orchestrator's inlined Multi-Model Decision Protocol)\n- ADR generation for critical-tier tasks\n- **Mandatory user stop** before proceeding — design decisions must be approved\n- Read `steps/design/README.md` for the full protocol\n\n### Step 2: Specification\n- Elicit requirements from the user, clarify scope\n- Define acceptance criteria and constraints\n- Build on design decisions from the previous step\n\n### Step 3: Planning\n- Deep codebase analysis using `search`, `scope_map`, `trace`, `analyze_*`\n- Design architecture based on spec and design decisions\n- Create comprehensive implementation plan with file-level changes\n\n### Step 4: Task Breakdown\n- Break the plan into ordered, atomic implementation tasks\n- Define dependencies between tasks\n- Identify parallel batches for multi-agent execution\n- Architecture review of the task structure\n\n### Step 5: Execution\n- Orchestrator dispatches agents in parallel batches per the task breakdown\n- Each agent gets a scoped task (1-3 files) with clear acceptance criteria\n- TDD: write tests first, then implement\n- Per-batch review cycle: Code Review (dual) → Arch Review → Security → Evidence Gate\n\n### Step 6: Verification\n- Dual code review (Code-Reviewer-Alpha + Beta)\n- Architecture review (Architect-Reviewer-Alpha + Beta)\n- Security review\n- Run `check({})` + `test_run({})` + `blast_radius({})`\n- `evidence_map({ action: \"gate\" })` for final quality gate\n\n## Using Skills Inside Steps\n\nWhen the Orchestrator activates a step:\n\n1. **Read the instruction first** — `flow({ action: 'read' })` returns the README.md for the current step\n2. **Follow step instructions** — the README.md is the primary guide for what to do\n3. **Delegate to listed agents** — each step lists which agents are appropriate\n4. **Produce the required artifact** — the step's `produces` field specifies what file to create in the artifacts directory\n5. **Check dependencies** — the step's `requires` field lists artifacts from previous steps that must exist\n6. **Report status** — agents report `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED` to the Orchestrator\n\n## Artifacts\n\nAll artifacts are stored in the run directory under `.flows/{topic}/`. The template variable `{{artifacts_path}}` resolves to the actual path at runtime.\n"},{file:`steps/design/README.md`,content:`# Design Gate — Advanced Flow
 
 Full design gate for new features, API design, and architecture changes. Runs brainstorming, decision protocol, and FORGE classification before specification begins.
 
@@ -244,7 +244,7 @@ After user approves:
 - \`DONE_WITH_CONCERNS\` — approved with caveats (list them)
 - \`NEEDS_CONTEXT\` — user raised questions that need more research
 
-**Do NOT call \`flow_step\`** — let the Orchestrator advance the flow.
+**Do NOT call \`flow({ action: 'step', advance: 'next' })\`** — let the Orchestrator advance the flow.
 
 ## Outputs
 
@@ -311,7 +311,7 @@ Before starting this step, verify:
 - [ ] Task breakdown approved with valid task graph
 - [ ] \`{{artifacts_path}}/tasks.md\` exists with defined batches and dependencies
 
-If prerequisites are NOT met -> **backtrack to task step** (\`flow_step({ action: 'redo' })\` on previous step)
+If prerequisites are NOT met -> **backtrack to task step** (\`flow({ action: 'step', advance: 'redo' })\` on previous step)
 
 ## Purpose
 
@@ -456,7 +456,7 @@ Before starting this step, verify:
 - [ ] Specification approved with clarity score ≥90
 - [ ] \`{{artifacts_path}}/spec.md\` exists and is complete
 
-If prerequisites are NOT met → **backtrack to spec step** (\`flow_step({ action: 'redo' })\` on previous step)
+If prerequisites are NOT met → **backtrack to spec step** (\`flow({ action: 'step', advance: 'redo' })\` on previous step)
 
 ## Purpose
 
@@ -582,7 +582,7 @@ Before starting this step, verify:
 - [ ] Design decisions approved (design-decisions.md exists with user approval)
 - [ ] FORGE tier assigned and documented
 
-If prerequisites are NOT met -> **backtrack to design step** (\`flow_step({ action: 'redo' })\` on previous step)
+If prerequisites are NOT met -> **backtrack to design step** (\`flow({ action: 'step', advance: 'redo' })\` on previous step)
 
 ## Purpose
 
@@ -703,7 +703,7 @@ Before starting this step, verify:
 - [ ] Implementation plan approved
 - [ ] \`{{artifacts_path}}/plan.md\` exists with defined phases
 
-If prerequisites are NOT met → **backtrack to plan step** (\`flow_step({ action: 'redo' })\` on previous step)
+If prerequisites are NOT met → **backtrack to plan step** (\`flow({ action: 'step', advance: 'redo' })\` on previous step)
 
 ## Purpose
 
@@ -823,7 +823,7 @@ Before starting this step, verify:
 - [ ] \`check({})\` and \`test_run({})\` pass
 - [ ] \`{{artifacts_path}}/progress.md\` exists with execution results
 
-If prerequisites are NOT met → **backtrack to execute step** (\`flow_step({ action: 'redo' })\` on previous step)
+If prerequisites are NOT met → **backtrack to execute step** (\`flow({ action: 'step', advance: 'redo' })\` on previous step)
 
 ## Purpose
 
@@ -954,7 +954,7 @@ Before completing this step, persist important findings using \`knowledge({ acti
 - **Session checkpoint**: Summarize what was accomplished, decisions made, and any remaining work
 
 **Every step produces knowledge worth preserving.** If you discovered something that would help a future session, call \`knowledge({ action: "remember", ... })\` now.
-`}],"aikit-basic":[{file:`README.md`,content:"# aikit:basic — Quick Development Flow\n\nQuick development flow for **bug fixes, small features, and refactoring**.\n\n## Steps\n\n| # | Step | Skill | Produces | Requires | Agents |\n|---|------|-------|----------|----------|--------|\n| 1 | **Design Gate** | `steps/design/README.md` | `design-decisions.md` | — | Researcher-Alpha/Beta/Gamma/Delta |\n| 2 | **Assessment** | `steps/assess/README.md` | `assessment.md` | `design-decisions.md` | Explorer, Researcher-Alpha |\n| 3 | **Implementation** | `steps/implement/README.md` | `progress.md` | `assessment.md` | Implementer, Frontend |\n| 4 | **Verification** | `steps/verify/README.md` | `verify-report.md` | `progress.md` | Code-Reviewer-Alpha, Security |\n\n## How It Works\n\nEach step has a **README.md** file that contains the detailed instructions for the agent(s) executing that step. The Orchestrator reads the README.md via `flow_read_instruction` and delegates work accordingly.\n\n### Step 1: Design Gate\n- **Auto-skips** for bug fixes and refactors (produces a minimal `design-decisions.md` noting it was skipped)\n- For small features: runs quick brainstorming, FORGE classification, and optional decision protocol (see Orchestrator's inlined Multi-Model Decision Protocol for the full 3-phase process)\n- Read `steps/design/README.md` for the full decision tree\n\n### Step 2: Assessment\n- Explore the codebase to understand scope and impact\n- Use `search`, `scope_map`, `file_summary`, `compact` to gather context\n- Identify the approach and produce `assessment.md`\n\n### Step 3: Implementation\n- Write code following the assessment plan\n- The Orchestrator dispatches Implementer/Frontend agents with specific file scopes\n- Follow TDD practices where applicable\n\n### Step 4: Verification\n- Code review, test execution, security check\n- Run `check({})` + `test_run({})` + `blast_radius({})`\n- Produce `verify-report.md` with findings\n\n## Using Skills Inside Steps\n\nWhen the Orchestrator activates a step:\n\n1. **Read the instruction first** — `flow_read_instruction` returns the README.md for the current step\n2. **Follow step instructions** — the README.md is the primary guide for what to do\n3. **Delegate to listed agents** — each step lists which agents are appropriate\n4. **Produce the required artifact** — the step's `produces` field specifies what file to create in the artifacts directory\n5. **Check dependencies** — the step's `requires` field lists artifacts from previous steps that must exist\n6. **Report status** — agents report `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED` to the Orchestrator\n\n## Artifacts\n\nAll artifacts are stored in the run directory under `.flows/{topic}/`. The template variable `{{artifacts_path}}` resolves to the actual path at runtime.\n"},{file:`steps/assess/README.md`,content:`---
+`}],"aikit-basic":[{file:`README.md`,content:"# aikit:basic — Quick Development Flow\n\nQuick development flow for **bug fixes, small features, and refactoring**.\n\n## Steps\n\n| # | Step | Skill | Produces | Requires | Agents |\n|---|------|-------|----------|----------|--------|\n| 1 | **Design Gate** | `steps/design/README.md` | `design-decisions.md` | — | Researcher-Alpha/Beta/Gamma/Delta |\n| 2 | **Assessment** | `steps/assess/README.md` | `assessment.md` | `design-decisions.md` | Explorer, Researcher-Alpha |\n| 3 | **Implementation** | `steps/implement/README.md` | `progress.md` | `assessment.md` | Implementer, Frontend |\n| 4 | **Verification** | `steps/verify/README.md` | `verify-report.md` | `progress.md` | Code-Reviewer-Alpha, Security |\n\n## How It Works\n\nEach step has a **README.md** file that contains the detailed instructions for the agent(s) executing that step. The Orchestrator reads the README.md via `flow({ action: 'read' })` and delegates work accordingly.\n\n### Step 1: Design Gate\n- **Auto-skips** for bug fixes and refactors (produces a minimal `design-decisions.md` noting it was skipped)\n- For small features: runs quick brainstorming, FORGE classification, and optional decision protocol (see Orchestrator's inlined Multi-Model Decision Protocol for the full 3-phase process)\n- Read `steps/design/README.md` for the full decision tree\n\n### Step 2: Assessment\n- Explore the codebase to understand scope and impact\n- Use `search`, `scope_map`, `file_summary`, `compact` to gather context\n- Identify the approach and produce `assessment.md`\n\n### Step 3: Implementation\n- Write code following the assessment plan\n- The Orchestrator dispatches Implementer/Frontend agents with specific file scopes\n- Follow TDD practices where applicable\n\n### Step 4: Verification\n- Code review, test execution, security check\n- Run `check({})` + `test_run({})` + `blast_radius({})`\n- Produce `verify-report.md` with findings\n\n## Using Skills Inside Steps\n\nWhen the Orchestrator activates a step:\n\n1. **Read the instruction first** — `flow({ action: 'read' })` returns the README.md for the current step\n2. **Follow step instructions** — the README.md is the primary guide for what to do\n3. **Delegate to listed agents** — each step lists which agents are appropriate\n4. **Produce the required artifact** — the step's `produces` field specifies what file to create in the artifacts directory\n5. **Check dependencies** — the step's `requires` field lists artifacts from previous steps that must exist\n6. **Report status** — agents report `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED` to the Orchestrator\n\n## Artifacts\n\nAll artifacts are stored in the run directory under `.flows/{topic}/`. The template variable `{{artifacts_path}}` resolves to the actual path at runtime.\n"},{file:`steps/assess/README.md`,content:`---
 name: assess
 description: Understand scope, analyze the codebase, and identify the implementation approach.
 ---
@@ -980,7 +980,7 @@ Before executing this step, verify:
 
 If any prerequisites are missing or incomplete:
 1. Inform the Orchestrator with specifics about what's missing
-2. Recommend \`flow_step({ action: 'redo' })\` on the **design** step
+2. Recommend \`flow({ action: 'step', advance: 'redo' })\` on the **design** step
 3. Do NOT proceed with partial inputs — quality degrades downstream
 
 ## Process
@@ -1132,7 +1132,7 @@ When complete, report status:
 - \`DONE\` — design decisions captured, ready for assessment
 - \`DONE_WITH_CONCERNS\` — design captured but open questions remain (list them)
 
-**Do NOT call \`flow_step\`** — let the Orchestrator advance the flow.
+**Do NOT call \`flow({ action: 'step', advance: 'next' })\`** — let the Orchestrator advance the flow.
 
 ## Outputs
 
@@ -1206,7 +1206,7 @@ Before executing this step, verify:
 
 If any prerequisites are missing or incomplete:
 1. Inform the Orchestrator with specifics about what's missing
-2. Recommend \`flow_step({ action: 'redo' })\` on the **assess** step
+2. Recommend \`flow({ action: 'step', advance: 'redo' })\` on the **assess** step
 3. Do NOT proceed with partial inputs — quality degrades downstream
 
 ## Process
@@ -1338,7 +1338,7 @@ Before executing this step, verify:
 
 If any prerequisites are missing or incomplete:
 1. Inform the Orchestrator with specifics about what's missing
-2. Recommend \`flow_step({ action: 'redo' })\` on the **implement** step
+2. Recommend \`flow({ action: 'step', advance: 'redo' })\` on the **implement** step
 3. Do NOT proceed with partial inputs — quality degrades downstream
 
 ## Process

package/scaffold/dist/definitions/prompts.mjs

@@ -52,7 +52,7 @@ Merge findings from both reviewers:
 - **Disagreements**: Contradicting verdicts → present both to user
 
 ### Step 5: Report
-Present unified review with: verdict, findings by severity, recommended actions.`},"flow-add":{description:`Install a new flow from a git URL or local path — with interactive error recovery`,agent:`Orchestrator`,tools:[`flow_add`,`flow_list`,`flow_info`,`search`,`compact`,`file_summary`,`present`],content:`## Flow Installation Assistant
+Present unified review with: verdict, findings by severity, recommended actions.`},"flow-add":{description:`Install a new flow from a git URL or local path — with interactive error recovery`,agent:`Orchestrator`,tools:[`flow`,`search`,`compact`,`file_summary`,`present`],content:`## Flow Installation Assistant
 
 Install a development flow from a git repository or local directory.
 
@@ -65,8 +65,8 @@ Provide a git URL or local path:
 
 ### Workflow
 
-1. **Attempt Install** — Call \`flow_add\` with the provided source
-2. **On Success** — Show installed flow info with \`flow_info\`, present summary to user
+1. **Attempt Install** — Call \`flow({ action: 'add', source })\` with the provided source
+2. **On Success** — Show installed flow info with \`flow({ action: 'info', name })\`, present summary to user
 3. **On Failure** — Classify the error and enter the appropriate recovery path:
 
 ### Error Recovery Paths
@@ -79,7 +79,7 @@ If the error mentions authentication, credentials, 401, 403, permission denied,
    - **SSH key**: Walk through \`ssh-keygen -t ed25519\`, adding the public key to their git host, and retrying with the SSH URL
    - **Personal Access Token (PAT)**: Guide them to create a PAT in their git host settings, configure \`git credential.helper store\`, and retry
    - **Git Credential Manager**: Check if GCM is installed, help install if needed, then retry (GCM opens a browser for auth)
-3. After credentials are configured, retry \`flow_add\`
+3. After credentials are configured, retry \`flow({ action: 'add', source })\`
 
 #### Network / Connectivity Failure
 If the error mentions timeout, host not found, SSL, or proxy:
@@ -89,7 +89,7 @@ If the error mentions timeout, host not found, SSL, or proxy:
 3. Retry after the issue is resolved
 
 #### Format Not Recognized
-If \`flow_add\` succeeds cloning but returns a format/structure error:
+If \`flow({ action: 'add', source })\` succeeds cloning but returns a format/structure error:
 
 1. Explain that the source was fetched but doesn't match any supported format
 2. List the 3 supported formats:
@@ -102,7 +102,7 @@ If \`flow_add\` succeeds cloning but returns a format/structure error:
    - If it has a different workflow format → propose conversion
    - If it's missing key parts → guide user to fill them in
 5. Create the missing \`flow.json\` manifest and step structure
-6. Retry \`flow_add\` with the fixed source
+6. Retry \`flow({ action: 'add', source })\` with the fixed source
 
 ### Native flow.json Format Reference
 \`\`\`json
@@ -130,25 +130,25 @@ If \`flow_add\` succeeds cloning but returns a format/structure error:
 ### Post-Install
 After successful installation:
 - Show the flow name, steps, and description via \`present\`
-- Remind user they can start it with \`flow_start\``},"flow-manage":{description:`List, inspect, update, and remove installed flows`,agent:`Orchestrator`,tools:[`flow_list`,`flow_info`,`flow_status`,`flow_update`,`flow_remove`,`flow_start`,`flow_reset`,`present`],content:`## Flow Management
+- Remind user they can start it with \`flow({ action: 'start', name, topic })\``},"flow-manage":{description:`List, inspect, update, and remove installed flows`,agent:`Orchestrator`,tools:[`flow`,`present`],content:`## Flow Management
 
 Manage your installed development flows.
 
 ### Available Actions
 
-1. **List flows** — \`flow_list\` to see all installed flows with status
-2. **Inspect a flow** — \`flow_info\` to see detailed steps, agents, and artifacts
-3. **Check status** — \`flow_status\` to see the active flow and current step
-4. **Update a flow** — \`flow_update\` to pull latest changes for git-installed flows
-5. **Remove a flow** — \`flow_remove\` to uninstall (builtin flows cannot be removed)
-6. **Start a flow** — \`flow_start\` to begin executing a flow
-7. **Reset active flow** — \`flow_reset\` to clear active flow state
+1. **List flows** — \`flow({ action: 'list' })\` to see all installed flows with status
+2. **Inspect a flow** — \`flow({ action: 'info', name })\` to see detailed steps, agents, and artifacts
+3. **Check status** — \`flow({ action: 'status' })\` to see the active flow and current step
+4. **Update a flow** — \`flow({ action: 'update', name })\` to pull latest changes for git-installed flows
+5. **Remove a flow** — \`flow({ action: 'remove', name })\` to uninstall (builtin flows cannot be removed)
+6. **Start a flow** — \`flow({ action: 'start', name, topic })\` to begin executing a flow
+7. **Reset active flow** — \`flow({ action: 'reset' })\` to clear active flow state
 
 ### Workflow
-1. If no specific action requested, start with \`flow_list\` and present overview
+1. If no specific action requested, start with \`flow({ action: 'list' })\` and present overview
 2. Use \`present\` to display flow information in a clear table/card format
 3. For updates, warn if there's an active flow that might be affected
-4. For removals, confirm with user before proceeding`},"flow-create":{description:`Create a new flow from scratch or migrate an existing workflow to aikit format`,agent:`Orchestrator`,tools:[`flow_add`,`flow_list`,`flow_info`,`search`,`compact`,`file_summary`,`present`],content:`## Flow Creation Assistant
+4. For removals, confirm with user before proceeding`},"flow-create":{description:`Create a new flow from scratch or migrate an existing workflow to aikit format`,agent:`Orchestrator`,tools:[`flow`,`search`,`compact`,`file_summary`,`present`],content:`## Flow Creation Assistant
 
 Create a new development flow or migrate an existing workflow to the aikit flow format.
 
@@ -166,7 +166,7 @@ Guide the user through building a complete flow:
    - Optionally assign preferred agents
 4. **Generate flow.json** — Create the manifest with all steps
 5. **Write step READMEs** — Create instruction files for each step
-6. **Install** — Use \`flow_add\` to install from the local directory
+6. **Install** — Use \`flow({ action: 'add', source })\` to install from the local directory
 
 ### Mode 2: Migrate Existing Workflow
 
@@ -177,7 +177,7 @@ If the user has an existing workflow (scripts, docs, runbooks) that they want to
 3. **Identify gaps** — What's missing for a complete flow? (instructions? ordering? agents?)
 4. **Fill gaps with user** — Ask user to clarify any ambiguous parts
 5. **Generate the flow** — Create flow.json + step READMEs
-6. **Install and validate** — Use \`flow_add\` and \`flow_info\` to verify
+6. **Install and validate** — Use \`flow({ action: 'add', source })\` and \`flow({ action: 'info', name })\` to verify
 
 ### Flow Structure