launch-readiness-auditor
Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Launch Readiness Auditor Audit one launch at one lifecycle read. Preflight evaluates readiness/assets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite. ## When This Must Trigger - Before a committed launch/announcement when go/no-go evidence is needed. - During/after the launch window when execution quality must be assessed. - After the declared lag when actual outcomes and learnings are reviewed. ## Quick Start ```text Run RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA. Run the outcome profile at day 30; keep it separate from the preflight result. ``` ## Skill Contract **Reads:** one launch, one lifecycle read, registry/canon/claims state, and profile-specific evidence. **Writes:** only a permissioned v3 artifact. **Done when:** the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation. `launch-registry` owns stage/date/embargo facts. `launch-day-conductor` executes the runbook. This auditor only judges the frozen evidence. ## Data Sources | Need | Prefer
- When This Must Trigger
- Quick Start
- Skill Contract
- Data Sources
- Instructions
- Runtime Reads
- Runtime and Setup
- Profile Procedure
- §2 RAMP Worked Examples
- §3 RAMP Guardrails
- §5 RAMP Translation
- Report and Verdict
- Validation Checkpoints
- Persistence
What does the launch-readiness-auditor skill do?
Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.