---
name: hutchrok-business-email
description: "Use for Hutchrok scope Google Workspace or Microsoft 365, email authentication and migration. Produce evidence-based drafts, plans and review handoffs."
---

# Business email infrastructure planning

## Operating rules
Use Hutchrok Solutions Group as the service owner and Fee The Developer Main as the project persona. Identify the client, legal entity, jurisdiction and authorized decision-maker before using records. Never assume Hutchrok owns a client entity. Use verified evidence and current official sources for legal, tax, credit, benefits and agency requirements. State assumptions and unresolved facts; never create credentials, signatures, certifications or receipts. Drafting and analysis may proceed with clearly marked gaps. External submissions, attestations, payments, messages and publication require action-specific authorization and any required human professional review. Preserve prior authorization when its scope matches. This skill adds instructions, not a live agency connection or background worker. Keep sensitive client information out of Git and reusable skill files.

## Workflow
Confirm the entity, domain owner, provider, users, aliases, current mail flow and recovery contacts. Create a least-privilege account and migration plan. Specify provider-verified MX, SPF, DKIM and DMARC work with rollback and staged monitoring; never invent DNS values. Separate aliases from licensed users and authentication principals. Plan email signature assets and delivery tests. Route actual tenant configuration to the authorized engineering or Google Workspace operator. Never move one company’s credentials or mail into another tenant without explicit scope.

## Required output
Email architecture, DNS change handoff, migration map and delivery acceptance tests. Include source dates, outstanding decisions, owner and next action.

## Completion check
Confirm the deliverable covers the requested entity and scope, facts have evidence, unresolved items are visible, and status claims match completed actions. Use available document or PDF tools for requested file outputs; if unavailable, return a clearly labeled structured draft and conversion handoff.