What problem does it solve? In a multi-layer agent orchestration system, it is easy to misplace project tasks, issues, or feedback in the wrong layer, commit project data to the root repository, or target the wrong Git branch. This Skill applies the Layer-0 root/global operating rules to classify every request and decide where data should be stored or promoted. ## Core Features & Use Cases - Layer Classification: Sorts incoming requests into Layer 0 (common rules), Layer 1 (Project SSoT), Layer 2 (Project Work SSoT), or Layer 3 (silo local findings). - Branch Routing: Determines the correct base and working branches (e.g., main-v3/main vs project-{projectName}/main) and prevents mixing Layer-0 and project changes in one PR. - Promotion Judgment: Decides whether silo-local findings should be promoted to project or global rules, and whether project assets belong in a fork, submodule, or reference. - Use Case: When a bug fix in a project silo reveals a reusable pattern, use this Skill to decide whether it stays local, becomes a project task, or is promoted as a separate Layer-0 update with its own branch and PR. ## Quick Start Ask the agent to classify this request and decide which layer, storage location, and branch it belongs to before making any changes.
