القائمة
Orchestrator: routing work and agent phases
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
When writing or reviewing BSL, apply 1C standards
При написании или ревью BSL применять стандарты 1С
Оркестратор: маршрутизация работы и фаз агентов
BSL LSP navigation: definitions, refs, call graph
Rules for using RLM tools for project search and navigation in 1C/BSL
Find an existing equivalent before new BSL code
| name | orchestrator |
| description | Orchestrator: routing work and agent phases |
Important. Previously, the orchestrator's entire operational main-thread handling lived in this always-on document and was inherited by subagents - exactly the kind of channel A bloat that retiering eliminated (see the manifest
docs/rules-skills-retiering/manifest.md, §6, §7.1, §7.2). Now, handling is the durable identity of the main thread in its system prompt, not a loaded document.
| Layer | Content | Location | Durability |
|---|---|---|---|
| 1. Lead / dispatcher | classification; choosing the short/full cycle; for short - self vs delegate under the quick-fix guard | profile framework/subagents/orchestrator.md | durable, every request (main-only) |
| 2. Orchestration discipline | "I do not execute - I delegate", routing, gates, review-cycle, BUG-routing, escalation filter, cross-provider (§7), Infostart audit (§9), LOG protocol | profile framework/subagents/orchestrator.md | durable; active only in full mode |
| 3. Detailed phase mechanics | phases Phase 0...4, artifact transfer, error handling | framework/workflows/full-cycle/SKILL.md | read-on-choice (when entering a phase) |
| Anchor / cross-harness bridge | a thin self-promoting stub that raises the profile on any harness | framework/rules/framework-bootstrap/SKILL.md (always-on) | survives compact, re-triggers |
--append-system-prompt is the recommended default,
or --agent orchestrator; see profile § "Launch method" and manifest §6.1). On harnesses without these
flags, the profile raises the portable framework-bootstrap stub (manifest §7.3).quick-fix) or full.full-cycle.md on entry to each phase.The main agent is Lead, putting on one of the hats, not "always the orchestrator". The prohibition
"the orchestrator is NOT an executor" applies ONLY in full mode. In Lead/short mode, main executes itself
or delegates one subagent within the quick-fix bounds (< 20 lines, 1 file, no new metadata objects, no architecture) with a mandatory verify step. The full wording is in the profile
(Layer 1 §1.3, Layer 2 "PROHIBITED").
depends_on: