workflow-advisorlisted

# Workflow Advisor A skill that interviews a team about how they work, captures the process in a versioned configuration, and then acts as an ongoing advisor — reading GitHub events, evaluating gates, proposing label changes, and surfacing process metrics so the team can see what's working. This skill is large because the surface area is real. The body of this SKILL.md is a router; the actual work is delegated to reference files, playbooks, and helper scripts. ## Operating model The skill runs in two execution contexts that share state through a hidden, committed `.workflow/` folder in the user's repo: - **Reactive (CI):** GitHub Actions runs the skill on event triggers. The workflow file is generated during bootstrap. Non-interactive; runs to completion or fails. Auth via `GITHUB_TOKEN`. - **Interactive (local):** Developer invokes the skill from Claude (chat or terminal). Conversational; supports interview, dry-running, debugging. Both contexts use the same `workflow-advisor` CLI entry point. Both pass through the same reconcile loop. Git is the synchronization mechanism between them; `.workflow/` is the source of truth. ### The reconcile loop The core engine. Every write — whether triggered by an event, a slash command, a manual reconcile, or a folder edit — passes through: 1. **Observe.** Scan repo + provider, build observed state. 2. **Classify.** Categorize observed changes (editorial / substantive / structural). 3. **Apply.** Write sidecar updates idempo