copilot-faq-answererlisted

# copilot-faq-answerer The day-job lever. The user fields the same handful of Copilot questions across stakeholders, legal, security, audit, and engineering. This skill makes the response consistent, sourced, and compliance-framed — and updates itself as `vault/facts/copilot/` accumulates new fact notes. ## When to use - Someone asks the user a Copilot question fitting one of the canonical categories below. - A stakeholder update needs a one-paragraph answer to a recurring Copilot concern. - The user is drafting a policy document and wants a single source of truth for the org's posture. ## When NOT to use - Truly novel Copilot questions with no canonical answer — those go through `copilot-deep-dive`, which does fresh research and lands in `vault/research/copilot/`. - Questions about a specific repo's config — that's `ghas-config-reviewer` territory. - Questions about Copilot rollout strategy / metrics — that's `copilot-rollout-playbook` / `copilot-metrics-analyzer`. ## Answer-resolution order For each question: 1. **Obsidian-first check**: query `vault/facts/copilot/` (via `vault-querier`) for any fact with a matching `predicate` more recent than the canonical answer's `last_verified` date. If found, **prefer the vault fact** and note that the canonical answer is being overridden. 2. **Canonical answer**: look up `canonical-answers.md` in this skill folder. 3. **Apply the regulated-org lens**: every answer ends with a 1-2 sentence "What this means for a regulated org"