capability-delivery-checklist
SolidEnd-to-end checklist for delivering new capabilities across CLI, presets, and tests
Install
Quality Score: 79/100
Skill Content
Details
- Author
- Goldziher
- Repository
- Goldziher/ai-rulez
- Created
- 1 years ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
deliver-launch-checklist
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.
test-checklist
Produce a hand-runnable human test checklist alongside automated tests. Run after writing automated test suites for a phase/feature that ships user-visible behavior. Creates a markdown doc (public by default in tests/checklists/, or in a project-private location for sensitive content) that a human walks through to verify end-to-end behavior that mocks can't cover -- shell rendering, Windows codepages, real subprocess behavior, interactive prompts, file atomicity under real conditions, config isolation, and other "the mocks say it works but does it REALLY" scenarios.
launch-checklist
Launch-stage skill: turns a feature plus team context into a tailored launch checklist where every item has a named owner role and a verifiable done condition. Use when a ship date is approaching and the work needs enumerating — 'build the launch checklist', 'what do we need before we ship', 'launch readiness list', 'we ship in 3 weeks, what has to happen' — or when /pm routes such a request here. Do NOT use to write announcements (announcement-drafter), GTM one-pagers (gtm-brief), ship/no-ship decisions (ai-feature-go-no-go), or for definitions of launch process.