launch-checklist

To generate a release readiness checklist, this Skill reads stage.txt, architecture-manifest, and open bug reports to compile sign-off-ready items across code, content, storefront, marketing, community, infrastructure, and legal reviews into a single Markdown file.

A cross-functional release readiness checklist ensures every department reviews and signs off on launch aspects—spanning code, content, infrastructure, and legal—before release, tracking progress and recording decisions to prevent oversights.

Yes, this checklist tool is designed for near-release scenarios, applying stage-by-stage validation across cross-functional areas including marketing, community, infrastructure, and legal to collect sign-offs and proceed with the launch.

The release checklist reads open bug reports and architecture-manifest files directly, applying platform and version information via frontmatter to output a structured Markdown file at production/releases/launch-checklist-[version].md.

The best way to track sign-off progress is using a structured checklist that validates each stage across cross-functional teams, compiling sign-off-ready items and recording decisions into a Markdown report for all teams to review.

Yes, generating a launch checklist requires stage.txt and architecture-manifest files as inputs, along with access to open bug reports, to produce a comprehensive cross-team readiness report with applied platform and version frontmatter.