project-advisorlisted

# Project Advisor Governance layer for project management. Reads per-project configuration from `workflow/projects/*.yaml` to know field values, governance rules, and state mappings. Actual execution (creating issues, updating fields) goes through the `github-projects-manager` skill. **This skill is cross-cutting** — applies to every repo that uses GitHub Projects or Azure DevOps Boards, not just The Bridge. ## Project Registry Configuration lives in `workflow/projects/*.yaml`. Each file defines one project: - Field values (status, priority, type, size, stage, etc.) - Governance rules (K/W/B levels, per-rule overrides) - State mappings (project status → normalized state for trackers) - Review comment templates ``` projects/ ├── _schema.yaml # Schema documentation ├── _template.yaml # Blank template for new projects ├── examples/ # Neutralized examples (CORE layer) │ ├── operational.yaml # Type A: management, coordination │ ├── technical.yaml # Type B: software development │ ├── minimal.yaml # Type C: workshops, experiments │ └── ado-project.yaml # Azure DevOps integration └── {slug}.yaml # Actual project configs (USER layer) ``` **When creating issues or updating fields:** always read the matching `workflow/projects/{slug}.yaml` first. Use the field values defined there — never hardcode emojis, status names, or priority values. ## When This Skill Activates - User asks about project