peer-bank-tech-intellisted

# peer-bank-tech-intel The "what are peers actually doing?" skill. Banks rarely share details publicly, but enough information leaks through engineering blogs, conference talks, public open-source contributions, and named-analyst case studies to triangulate posture. ## When to use - Exec or board question: "what are JPMorgan / Goldman / etc. doing on AI coding?" - Posture review: is the bank ahead, on pace, or behind peers on a specific capability? - Vendor selection: which peers have publicly adopted vendor X — and what did they say afterward? - Annual peer-bank posture summary. ## When NOT to use - Specific vendor evaluation → `vendor-security-eval`. - Specific Copilot question → `copilot-faq-answerer`. - Confidential / non-public peer intelligence — out of scope, do not source from non-public material. ## Obsidian-first workflow (mandatory) 1. **Query the vault first** via `vault-querier`: - Full-text search the peer's name and the capability's key terms across `vault/research/peer-bank/**`, relevant `vault/facts/**` entities (per-bank entities where they exist), `vault/insights/**` (conference-talk notes often carry peer-bank signals), and recent `vault/digests/**` (last 90 days). - Backlink check on the peer-bank entity (e.g. `[[jpmorgan]]`, `[[capital-one]]`) and the capability's entities. 2. **Triage findings**: - If the vault answers the question fully → return the existing answer with source citations (vault path + original source URLs). No new write.