---
name: hiredata-plan-activation
description: Turn a recruitment or staffing problem into a prioritized HireData activation plan. Use when a customer, consultant, or implementation team needs to discover valuable automation use cases, connect them to user stories, assess data readiness, select channels, or decide which HireData workflows to implement first.
---

# Plan a HireData activation

Build a small, evidence-based activation plan around customer outcomes and actual HireData capabilities.

## Workflow

1. Establish the operating context: ATS, staffing model, main audiences, active channels, current HireData usage, and the problem to improve. Ask only for missing information that would materially change the recommendation.
2. Express each problem as: `When [actor] needs to [job], they struggle because [cause], resulting in [cost or risk].`
3. Use the HireData MCP to inspect the current workspace, connected apps, template library, available data, existing automations, and usage where access permits. Never invent unavailable workspace facts.
4. Identify opportunities across candidate, recruiter, and client journeys. Read [references/discovery-and-prioritization.md](references/discovery-and-prioritization.md) for discovery prompts, lifecycle patterns, and scoring.
5. Score opportunities by reach, frequency, outcome value, data readiness, implementation effort, and operational risk. Separate measured facts from estimates.
6. Recommend the smallest coherent first release, normally three to five workflows. Do not force a fixed number when fewer opportunities are justified.
7. For each recommendation, provide the user story, trigger moment, recipient, channel, expected action or signal, data dependencies, owner, success measure, and a safe first test.
8. Call out gaps that block implementation: missing relationships, unreliable fields, consent, sender setup, unsupported MCP actions, or unclear ownership.

## Output

Lead with the top recommendation and why it wins. Then provide a ranked plan and a 30-day measurement proposal. Keep numerical forecasts as ranges and show assumptions.

Do not create, publish, activate, send, or invite unless the user separately asks for that action. When implementation is requested, hand the approved workflow to the relevant creation skill.

## Guardrails

- Prefer observed customer problems and current workspace evidence over a generic template catalog.
- Do not expose internal retention claims, customer information, or commercially sensitive benchmarks.
- Do not promise outcomes based on unsupported open-rate, reply-rate, or credit-volume claims.
- Treat compliance and consent as context-dependent; flag uncertainty rather than giving legal advice.
- If the MCP is unavailable, provide a discovery plan and identify which facts still require verification.