boss-advancedlisted

# Boss Advanced Orchestration Patterns ## Skill vs Agent Conflict Resolution When both a skill and an agent could handle the request, evaluate three dimensions: | Dimension | -> Skill | -> Agent | |-----------|---------|---------| | **Scope** | Narrow (single file/function/document) | Wide (multi-file, project-wide, cross-module) | | **Depth** (weighted 2x) | Shallow (template, format, generate, lookup) | Deep (analyze patterns, trace dependencies, investigate, reason about code) | | **Interactivity** | One-shot (produce output, done) | Iterative (explore -> decide -> act -> verify) | **Scoring:** Depth counts double. Tally: Skill-points vs Agent-points (max 4). Higher score wins. - Scope->Skill = 1pt, Depth->Skill = 2pt, Interactivity->Skill = 1pt -> Skill total - Scope->Agent = 1pt, Depth->Agent = 2pt, Interactivity->Agent = 1pt -> Agent total - Tie -> ask the user one clarifying question **Special cases:** - **File-format deliverable** (the output IS a pdf/docx/xlsx/pptx) -> Skill always wins, regardless of dimensions - **Visual design deliverable** (landing page, component, UI) where the primary output is rendered HTML/CSS -> Skill wins (one-shot generation); **design consultation** (evaluate existing design, propose improvements iteratively) -> Agent wins (iterative exploration) - **Single-file security review** -> If scope is exactly 1 file, prefer gstack `/cso` Skill (checklist-based review is more thorough for single files); if multi-file -> gstack `/cso` also pr