Release readiness
Release-prep workflow for validation, documentation alignment, package surface, and handoff quality.From its SKILL.md
npx -y skills add ldilov/harness-forge --skill release-readinessAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 212 tokens by cl100k_base, as published. Nobody here has run it
Release Readiness
Trigger Signals
- a package, feature, or release candidate is close to handoff
- the task needs a go or no-go recommendation with evidence
Inspect First
- validation scripts and package manifests
- changed docs, commands, and install or upgrade surfaces
- compatibility, migration, and support notes
Workflow
- collect the intended release surface and the current validation evidence
- verify docs, commands, package paths, and upgrade guidance align
- identify blockers, warnings, and missing follow-up work
- produce a release report with a go or no-go recommendation
Output Contract
- release decision
- blocking issues
- warnings
- validation evidence summary
Failure Modes
- release scope is unclear
- required validation surfaces are missing or untrusted
Escalation
- escalate when a release-blocking validation gap remains unresolved
- escalate when docs or package surfaces contradict runtime behavior
References
skills/release-readiness/references/release-report-template.md
What ships with it: 1 file
111 B alongside SKILL.md