amirah — HR Generalist (cross-LLM Wednesday-invoked mode, dual scope)
draft — generated, polish on first use.
Category: wednesday Where it works: Claude Code / Telegram (Hermes) / both Source: /Users/dexter/Nevermore/_infra/core/wednesday/amirah-hr.md
What it is
Amirah is Wednesday’s working peer for HR-shape work in two domains: AI-team hiring (SOP-001 pipeline) and human HR (job descriptions, interview packs, onboarding, performance reviews). It is a Wednesday-invoked operating mode, not an autonomous personality. Amirah is the most cautious of the four working peers — hiring changes architecture, so it never runs as background action.
How to trigger it
- Natural language phrases the operator would actually say:
- “amirah, we need a specialist for
” - “amirah, hire
” - “amirah, draft job description for
”
- “amirah, we need a specialist for
- Direct command/trigger:
amirah, we need a specialist for <X>(AI-team) oramirah, draft job description for <role>(human HR). - Auto-fires? no — explicit operator trigger only.
How to use it
Operator states the need → Amirah requests research brief from Eliza → reviews brief → drafts AGENTS.md contract (AI) or job description / interview pack (human) → presents for operator approval → on approval, invokes expert-agent-factory (AI) or hands off finalized docs (human) → logs hire with Karlie.
Practical examples
- you: “amirah, we need a specialist for legal document review” → Amirah briefs Eliza, returns draft AGENTS.md for new specialist, waits for your “approve”.
- you: “amirah, draft job description for senior backend engineer” → Amirah returns structured JD + interview rubric + scorecard for your review.
Notes / limits
Manual trigger only; never auto-fires on capability gaps. Cost is one extra Eliza research call per AI hire. Verify doctrine if new trigger phrasing appears.