Recipes Overview
Step-by-step plays the agent follows as its plan.
A recipe (a "play") is a validated, step-by-step task plan. When one matches your task,
the hyreflow-recruit agent follows it as its plan — the recipes encode filter shapes, costs,
and pitfalls learned from real runs. They're patterns the agent composes at runtime, not
hard-coded pipelines.
Drive any of these by stating your task in plain English:
/hyreflow-recruit <your task>Candidate sourcing
JD → Shortlist
Paste a job description → parse → search (general + competitor-poach) → qualify → enrich. The most-requested recruiter play.
IT / Developer Sourcing
GitHub ground-truth + people-DBs in parallel → merge → qualify. Free emails.
Multi-source Candidate Search
Search across several people-DBs, dedupe, qualify on required skills.
Qualify Against ICP
The qualification gate — only ICP-fit pass before you spend enrich credits.
Signal-driven BD
Funding → BD
A company raises → qualify → find hiring managers → work email → BD sequence → CRM.
Layoff Signal → Poach
A company cuts staff → poach displaced talent + open a BD angle with survivors.
Outreach
The pipeline
Every recipe is a slice of the same arc. Candidate sourcing is people-first; BD/signal work is company-first.
source → qualify → enrich → sequence → push to ATSChannel rule: candidates get personal email + LinkedIn, never work email. BD contacts get work email. The agent enforces this per recipe.