Launch Readiness
Help PMs ensure launches are well-planned with nothing falling through the cracks. Use before any feature launch, experiment rollout, or release.
Install
$ agentstack add skill-hardiktiwari-pm-operating-os-launch-readiness ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hardiktiwari-pm-operating-os-launch-readiness) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Launch Readiness
Help PMs run launch readiness checklists and make go/no-go recommendations. Ensures launches are planned, risks are surfaced, and stakeholders are aligned.
When to Use
- Before a feature launch
- Before an experiment rollout
- Before a product release
- Go/no-go meeting prep
- When asked "are we ready to launch?"
Process / Template
1. Define Launch Scope
- What is being launched? (feature, experiment, release)
- Target audience and rollout plan (% of users, segments)
- Launch date and any phased milestones
2. Run the Checklist
Product & Quality
- [ ] All P0/P1 bugs resolved or accepted
- [ ] Acceptance criteria met
- [ ] Edge cases and error states handled
- [ ] Rollback plan documented
Technical
- [ ] Feature flags / kill switches in place
- [ ] Monitoring and alerting configured
- [ ] Performance and load tested (if applicable)
- [ ] Data pipeline or analytics verified
Legal, Compliance, Security
- [ ] Legal review complete (if required)
- [ ] Privacy/compliance checks done
- [ ] Security review (if applicable)
Go-to-Market
- [ ] Support team briefed and docs updated
- [ ] Customer-facing comms ready (if applicable)
- [ ] Internal launch post drafted
Stakeholders
- [ ] Key stakeholders informed
- [ ] Escalation path defined
- [ ] Post-launch review scheduled
3. Assess Risks
- What could go wrong?
- Mitigation in place?
- Acceptable residual risk?
4. Make Go/No-Go Recommendation
| Status | Criteria | |--------|----------| | Go | All critical items green, risks acceptable | | Conditional Go | Minor items open; launch with monitoring | | No-Go | Critical gaps; delay until resolved |
5. Document Decision
- Summary of checklist outcome
- Open items and owners
- Go/no-go recommendation with rationale
- Next steps (if no-go or conditional)
Output
A Launch Readiness Summary including:
- Checklist status (green/yellow/red per area)
- Risk assessment
- Go/no-go recommendation
- Open items with owners
- Post-launch plan (monitoring, review)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.