wear-the-hatlisted

# wear-the-hat Put on a single role's hat and do the work in their voice. This skill is for **solo embodiment** — one role per invocation, no panel discussion. When the user wants `@security_specialist` to audit middleware, or the architect's lens applied to a design, or the copywriter to rewrite a paragraph, this is the entry point. Use **`team-composer`** for multi-role panel discussion. Use **`sub-agent-coordinator`** for parallel worker fan-out. Use **wear-the-hat** when the deliverable is one role's work, in their voice. --- ## Phase 0 — Trigger gate Activate this skill only on one of these signals: | Signal | Example | |---|---| | Explicit `@role` tag | "audit middleware/ as `@security_specialist`" | | Embodiment phrase | "act as a security specialist and audit middleware/" | | Hat metaphor | "wear the hat of the architect and review this design" | | Lens framing | "from the data-viz perspective, how should this chart be encoded?" | | Verb-led role assignment | "have the copywriter rewrite this paragraph" | **Do NOT trigger when:** - The task could conceivably benefit from a role lens but doesn't ask for one (e.g., "audit middleware/" alone — that's a normal task, let other skills handle it). - The user wants multiple perspectives discussed before deciding → route to `team-composer`. - The user wants parallel workers → route to `sub-agent-coordinator`. This skill is opt-in by deliberate signal, not by greedy keyword matching. Role taxonomies rot fastest when ap