HashWarlock

Draft an offer letter with compensation details and terms

Create structured interview plans with competency-based questions and scorecards. Triggers on "interview plan for [role]", "interview questions for [role]", "scorecard for [role]"

Headcount planning, org design, and team structure optimization. Triggers on "org planning", "headcount plan", "team structure", "reorg", "who should we hire next"

Track and manage recruiting pipeline from sourcing through offer. Triggers on "recruiting update", "candidate pipeline", "how many candidates", "hiring status for [role]"

Generate a prioritized daily plan. Triggers on "plan my day", "what's on my plate", "start my day", "morning plan", "daily priorities"

Quick meeting prep for any meeting — context, agenda, and talking points. Triggers on "prep for my meeting", "what's my next meeting about", "meeting context for [topic]"

Summarize and triage your task backlog. Triggers on "show my tasks", "task status", "what am I behind on", "triage my tasks"

Run a weekly review — what happened, what's next, what needs attention

Use when doing any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when you have a written implementation plan to execute with review checkpoints

Use when implementation is complete and all tests pass — guides completion by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when starting feature work that needs isolation from current workspace or before executing implementation plans

Use when implementing any feature or bugfix, before writing implementation code

Use when requests involve nixo or nixosandbox sandbox lifecycle operations, catalog queries, session-id workflows, or CLI errors such as 'Could not find flake.nix' and create flag conflicts.

Use when a user asks to connect from any paired channel and you need a URL-first enclout install flow with install-session polling and automatic connector/device identity binding.