---
name: hutchrok-software-automation
description: "Use for Hutchrok scope custom programming, company OS, integrations or automation. Produce evidence-based drafts, plans and review handoffs."
---

# Custom software and workflow automation advisory

## 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
Map current workflows, users, data boundaries and desired outcomes. Produce architecture and integration requirements with verified systems, least-privilege roles, audit events, failure handling and measurable acceptance criteria. ChatGPT handles intelligence and QA; Claude owns implementation; Gemini handles Workspace/media as directed. GitHub remains code source of truth and Dropbox the requested transfer route when authorized and available. Do not invent a Hutchrok OS repository or live MCP endpoint. Capture pending credentials as access requirements, never as embedded secrets.

## Required output
Engineering handoff, interface/data contracts, security requirements and validation plan. 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.