--- name: hutchrok-filing-tracking description: "Use for Hutchrok track a filing from initial intake through agency acceptance or rejection. Produce evidence-based drafts, plans and review handoffs." --- # Filing intake, review and status tracking ## 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 Create a case ID tied to one client and entity. Record stages as intake, evidence pending, drafting, client review, operator review, submitted, accepted or rejected. For each transition record responsible person, timestamp, document version and evidence. Separate internal preparation targets from agency timing. Require a submission receipt to mark submitted and an official acceptance record to mark accepted. For rejection capture the exact agency reason and route a corrected draft for renewed review. Deliver approved documents through a verified restricted channel only when authorized. ## Required output Case timeline, readiness checklist, receipt register and next-action status report. 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.