references/workflow-discovery-checklist.md·Markdown·4 KB·View on GitHub
Before creating ANY resources for a new workflow, gather the following from the
user. Do not proceed until all required items are answered. Ask in this order —
later questions depend on earlier answers.
Are we modifying an existing workflow or building a new one?
If modifying: identify existing resources (flow ARNs, channel IDs, endpoint
names) before making changes. Use describe/list API calls to understand
current state.
If new: proceed through the full checklist below.
What kind of workflow is this? (reference the workflow types from the routing table in SKILL.md).
Expected concurrent viewership (drives CDN egress — the dominant cost at scale)?
Is this always-on (24/7 linear) or event-based (start/stop)?
Always-on → flag reserved pricing opportunities (MediaLive, MediaConnect, CloudFront).
Event-based → on-demand pricing, but remind to stop resources between events.
Any existing reserved capacity or commitments (MediaLive reservations, CloudFront committed pricing, MediaConvert reserved slots)?
Use answers here to shape downstream decisions: channel class, ABR rung count,
segment duration, DVR window, and CDN price class. Load
references/workflow-cost-optimization.md if the user has explicit cost constraints
or asks for a cost comparison between options.