Software Orchestrator
5769c1cd22
- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung) - 25 Tests gruen (Pytest) - block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block) - 4 Restbaustellen gefixt - DB-Schema: plugin_settings-Tabelle hinzugefuegt - 3 Schattenprojekte aus DB geloescht - Plan v3 + Refactor-Plan + Worklog dokumentiert
1.3 KiB
1.3 KiB
name, description, tags
| name | description | tags | |||
|---|---|---|---|---|---|
| tool-governance | Tool registry, capability checks, and fallback handling for the orchestrator agent. |
|
Tool Governance
Purpose
Maintain a registry of available tools, verify capabilities before use, and define fallback behavior when a tool is unavailable.
When to Use
- Before invoking any tool for the first time
- When a tool returns an unexpected error
- When the agent needs to discover what tools exist
- During phase transitions
When Not to Use
- For well-known core tools (terminal, browser, code execution)
- For tools just confirmed working in this session
Procedure: Tool Discovery
- Use the
tool_registryplugin tool to list available tools - Read tool documentation from help//help.md
- Note required inputs, expected outputs, error modes
Procedure: Capability Check
- Verify the tool exists in registry
- Verify all required inputs are available
- Verify the tool is enabled (not toggled off)
- If any check fails: see Fallback
Procedure: Fallback
- Tool not found: use
capability_checkto find closest alternative - Tool disabled: ask user to enable or use alternative
- Tool errors persistently: delegate to test_debug_engineer for diagnosis
See Also
- Plugin tool:
tool_registry - Plugin tool:
capability_check