| Field | Value |
|---|---|
| marp | true |
| title | Launch Readiness Review |
| paginate | true |
| theme | default |
Slide 1 of 7
Launch Readiness Review
Review Copilot sample deck for launch, support, and demo readiness.
1 / 7
Why now
- Docs teams are receiving more generated drafts.
- Reviewers need rendered context before line-level source context.
- Support needs clear handoff language before launch.
- Agents need bounded comments that map back to documents, routes, and components.
2 / 7
What Commentary demonstrates
- Rendered Markdown review.
- Static HTML report review.
- Draft and Brainstorming Reviews.
- Live Preview element comments.
3 / 7
Launch gates
| Gate | Owner | State |
|---|---|---|
| Support FAQ reviewed | Support | In review |
| Static HTML report approved | Product | Ready |
| GitHub Pages Live Preview embeds | Engineering | Needs validation |
| Demo reset manifest current | Growth | Pending reset |
4 / 7
Demo narrative
- Open a Markdown PR and review the rendered launch brief.
- Move to the HTML migration report and inspect Preview plus Raw.
- Open the Live Preview sample and comment on a billing control.
- Show Draft and Brainstorming Reviews as agent-ready app-native records.
5 / 7
Risks to discuss
- GitHub Pages routes must serve real app content at
/,/settings/billing,/usage, and/checkout. - The Live Preview SDK must load without exposing secrets.
- Demo comments should sound like real implementation feedback.
6 / 7
Decision slide
Launch when rollback ownership, support FAQ, and sample demos are all ready.
7 / 7