Skip to content
Back to skills

Danthamanvoiss V1 Launch Checklist

ASecurity

Provide a concise go-live checklist for publishing the suite as a stable v1.0.0 release.

  • 76 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
testinggo

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add jiayaoqijia/cryptoskill --skill danthamanvoiss-v1-launch-checklist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Danthamanvoiss V1 Launch Checklist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Danthamanvoiss V1 Launch Checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jiayaoqijia-danthamanvoiss-v1-launch-checklist/badge)](https://www.skillsdirectory.com/skills/jiayaoqijia-danthamanvoiss-v1-launch-checklist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: v1-launch-checklist
description: Provide a concise go-live checklist for publishing the suite as a stable v1.0.0 release.
version: 1.0.0
tags: [core, release, checklist, v1]
---

## Purpose

Capture the minimum final checks needed to publish this suite as a stable v1 release without turning launch prep into a heavyweight process.

## Use when

- Finalizing the v1.0.0 release.
- Running a last-pass go-live review.
- Coordinating docs, routing, and catalog completion before publish.

## Required inputs

- Current release version and catalog state.
- Validation status.
- Any known open issues or review comments.

## Safety/authority

- Do not mark launch-ready while blockers remain unresolved.
- Keep the checklist factual and release-focused.
- Separate blocking issues from nice-to-have polish.

## Workflow

1. Confirm router hierarchy, docs, catalog, and validation are all aligned to the target release.
2. Check that context-first workflow guidance and handoff conventions are documented.
3. Verify there are no unresolved critical overlap or routing-confidence concerns.
4. Confirm the published inventory count and version are correct.
5. Return a short launch-ready checklist with only the necessary next actions.

## Output format

```
- Release version: ...
- Launch-ready items complete: ...
- Remaining blockers: ...
- Remaining polish: ...
- Final go-live recommendation: ...
```

## Quality checks

- The checklist is short and actionable.
- Routing, context, docs, and catalog are all represented.
- Blocking issues are explicit.
- The result is suitable for a final publish pass.

## Related skills

release-readiness-check, catalog-maintenance-guide, routing-confidence-check

Files in this skill

  • LICENSE1 KB
  • SKILL.md1.7 KB
  • SOURCE.md416 B
  • TRUST.auto.yaml2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…