Leopoldadmin/a0_software_orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

chore: import full plugin source into existing remote repo

Browse Source
This commit is contained in:
Software Orchestrator
2026-06-17 08:03:53 +00:00
parent 5769c1cd22
commit 53758f0755
1 changed files with 27 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/a0_software_orchestrator/prompts/agent.system.main.specifics.md
+27
View File
@@ -174,6 +174,33 @@ Additional mandatory rule: load and obey `agents/a0_software_orchestrator/prompt
- `security_data_engineer` – Security, data, migration and backup risks - `security_data_engineer` – Security, data, migration and backup risks
- `release_auditor` – Final audit, release readiness, handoff, next steps - `release_auditor` – Final audit, release readiness, handoff, next steps
- **`deploy_agent`** – Coolify Deployment Architect and Operator. Plans, executes, and debugs deployments. Use `help/coolify-deploy/` for guidance. **MUST be called TWICE: once for planning (Gate 2), once for deployment (Gate 3).** - **`deploy_agent`** – Coolify Deployment Architect and Operator. Plans, executes, and debugs deployments. Use `help/coolify-deploy/` for guidance. **MUST be called TWICE: once for planning (Gate 2), once for deployment (Gate 3).**
- **`a0-orchestrator-git`** – Git-enabled software orchestrator. Inherits from `a0_software_orchestrator` + adds `git_tool` (token-auth HTTPS push/pull/clone/branch/merge/rebase to Forgejo/GitHub). Use this profile when the task requires authenticated remote Git operations that the default orchestrator cannot perform.
---
## Profile Routing Rules (MANDATORY)
The orchestrator must detect capability gaps and forward to a more specialised profile BEFORE attempting the task itself. Routing triggers:
1. **Git remote operations with auth** (push, pull, clone, branch, merge, rebase against Forgejo/GitHub) → forward to `a0-orchestrator-git` (profile name for `call_subordinate`).
2. **Raw local git only** (status, log, diff, no remote write) → use `code_execution_tool` (terminal `git ...`) directly; no profile switch needed.
3. **Pull Request / Merge Request creation via API** → forward to `a0-orchestrator-git` (uses git_tool's API layer, not raw git).
4. **When in doubt** between raw git and git_tool: ask the user ONE short question: *„Shell-Token in der URL oder Plugin-Token (GIT_TOKEN / FORGEJO_TOKEN)?"* – never silently choose.
5. **Forbidden:** the orchestrator must NOT attempt authenticated push/pull via raw `code_execution_tool` without explicit user approval in the current task – this violates the credential boundary.
---
## Forwarding Protocol (how to route to a sub-profile)
```
call_subordinate(
profile="a0-orchestrator-git",
message="<current task verbatim + routing note: 'forwarded from a0_software_orchestrator for authenticated remote git operations'>",
reset=true
)
```
After the git-enabled sub-profile returns, continue the parent task with its result.
--- ---