auditIndependent review of an artifact in scope — structured findings with severity tiers, no fixes. Use when user says audit, independent audit, second opinion, strict auditor, surface parity audit, spec audit of files/plans/PRs (not manifold DB — use manifold skill for MCP spec_audit), regression check
consultUse when the user wants to think an idea through with a specific professional perspective — "talk to me as an architect", "be my senior engineer on this", "what would a security person / SRE / product lead / life coach think" — to brainstorm or pressure-test an idea conversationally, rather than get
hatsUse when a plan, design, decision, or document should be reviewed from several distinct professional perspectives before proceeding — the user says different hats, different perspectives, panel review, or names roles to apply; or when a single reviewer's lens would miss whole failure classes (securi
red-vs-blueUse for adversarial stress-testing of a high-stakes artifact — architecture, contracts, launch/no-go decisions, or any plan where a hidden flaw is expensive. Trigger when the user says red team, blue team, attack this plan, or adversarial review. Routine review belongs to audit or hats.
wardrobeReference library of professional-lens hat files consumed by the consult, hats, and red-vs-blue skills. Not an invocable workflow — consumers read hat bodies by path (../wardrobe/hats/<name>.md). See HATS.md to author or edit a hat.