launch-checklist

Generating a launch checklist requires access to PRDs and past launch records to pull context. The Skill then outputs a prioritized checklist with owners, dependencies, due dates, and a highlighted critical path, supporting small features, major rollouts, and regulatory releases.

The critical path in a product launch is the sequence of dependent tasks that cannot slip without delaying the release. This Skill identifies and highlights these critical-path items and blockers so launch leads know exactly which tasks require immediate attention.

Yes, you can use templates for small features, major launches, or regulatory releases. The Skill contextualizes the selected template by pulling context from PRDs and past launch records to output a tailored checklist with owners, dependencies, and due dates.

You can track cross-functional dependencies for a feature release by generating a consolidated checklist that maps task owners across engineering, product, and marketing. The Skill highlights dependencies and blockers so teams know what cannot slip during the launch.

Yes, you need access to PRDs and past launch records to plan a feature release using this Skill. It uses these documents to pull contextual information, apply the appropriate launch template, and generate an accurate checklist with dependencies and critical-path items.