Prashanthvara Vertical Onboarding Playbooks
Replaces the generic 80-question onboarding packet with a vertical-scoped one. Generic intake collects irrelevant data and stretches response cycles to weeks. Scoped intake gets answers in days.
Inputs
- Vertical: healthcare, government (federal/state/local), education, retail
- Deployment scope: user provisioning method (SSO/SCIM/manual), integration protocol, payment configuration, approval workflow complexity
Workflow
- Read the vertical module in
references/(healthcare.md,government.md,education.md,retail.md). Each module lists that vertical's mandatory fields, its regulatory riders (BAA needs, funding-source restrictions, tax exemption documentation), and the questions that vertical never needs. - Run
scripts/build_packet.py --vertical <v>to assemble the packet: only fields marked mandatory or conditionally triggered by the stated deployment scope. - Sequence the packet by dependency: fields the customer can answer immediately first, fields requiring their IT or legal teams flagged with expected turnaround and a named-owner slot.
- Emit a completion tracker: each field, owner, status, blocker.
Output format
Customer-facing packet (markdown, grouped by owning team on the customer side) plus internal tracker (CSV).
Guardrails
- Every question must trace to a configuration decision it unblocks. Questions without a consumer get cut.
- Legal and IT dependent fields get flagged on day one. Discovering them in week three is the failure this skill exists to prevent.