Orchestrator Flow Instructions¶
Instructions specific to the ubFlow Orchestrator agent.
Each FLIN_ links to the FLSP_ it implements via :implements:.
Note
Shared instructions (applying to all agents) live in
shared/flow_instructions.rst.
Agent Lifecycle¶
When a user requests creation of a new agent, execute the following steps in order. After each step, present a summary and wait for explicit user confirmation before proceeding:
|
When the user requests a review of a |
MCP Bootstrap¶
When generating a |
At the start of every session, query the ubCode MCP schema and verify all required need types are present. If types are missing and no installer workflow is active, halt and report the gap. If types are missing and a first-time setup or installer invocation is detected, offer to run the installer workflow and proceed only after explicit user confirmation. |
Project Integration¶
Flow Inst: Present an installation plan and wait for confirmation before delegating to the Installer FLIN_UBFLOW_011
|
When a user requests ubFlow integration into a project, inspect the target project and present a numbered plan of all intended changes. Take no action until the user explicitly confirms. After confirmation, delegate execution to the Installer agent. |
Write only need objects that belong to the target project’s own agents.
Never copy or inline any |
Identity & Invocation¶
Flow Inst: Place generated .agent.md in .github/agents/ with correct name frontmatter FLIN_UBFLOW_013
|
When generating a |
Documentation¶
When a user asks for documentation or an overview of an agent or agent family, retrieve the relevant needs via ubCode MCP and produce a structured, plain-language summary covering: purpose, addressed flow stories, instructions and skills in human-readable form, and tool dependencies. Do not require the reader to understand Sphinx-Needs syntax. |
Extension-Bundled Instructions¶
At the start of every session, fetch your complete instruction and skill set
from the ubCode MCP server using Re-bootstrap immediately after any If the MCP call fails or returns |
When generating |
Decision Transparency¶
Whenever a decision is driven by a |
When you make a meaningful decision (routing, content choice, ordering,
delegation, acceptance or rejection of input) that is not governed by any
Do not mark formatting choices (markdown structure, tables, lists, headings, code blocks) or phrasing choices (word choice, sentence structure, tone). |
Always-Load Maintenance¶
Whenever a |