How do I install the Drillan Speckit Gates Release Check skill?

Run npx skillmds@latest add tomevault-io/drillan-speckit-gates-release-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Drillan Speckit Gates Release Check skill do?

release-check It is listed under Coding & Dev Tools on SkillMD.

Is Drillan Speckit Gates Release Check safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Drillan Speckit Gates Release Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Drillan Speckit Gates Release Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Drillan Speckit Gates Release Check?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Drillan Speckit Gates Release Check by tomevault-io

Name: Drillan Speckit Gates Release Check
Rating: 4.2 (5 reviews)
Author: tomevault-io

File contents

release-check

Validates release readiness before creating a release.

Purpose

This skill validates that all artifacts are complete and consistent for release:

Spec kit artifacts: spec.md, plan.md, tasks.md exist and are complete
Documentation: README.md, CHANGELOG.md have required sections
Versioning: Version numbers are consistent across package.json and CHANGELOG
API docs: API documentation matches contract specifications

Output

The skill outputs a ReleaseChecklist with:

Overall readiness status (Ready/Not Ready)
Individual check items with pass/fail/skip status
Version consistency information
Specific issues to address before release

Usage

This is a manual skill - run it before creating a release:

npx skills run release-check

Or via AI agent:

User: Check if we're ready for release

Exit Codes

Code	Status	Meaning
0	Ready	All checks pass
1	Not Ready	Some checks failed
3	Error	Required files missing

Checks Performed

Artifact Checks (FR-022)

Check	Requirement
spec.md exists	Required
plan.md exists	Required
tasks.md exists	Required
All tasks complete	Required

Documentation Checks (FR-023)

Check	Requirement
README.md exists	Required
README.md has usage section	Required
CHANGELOG.md exists	Required
CHANGELOG.md has unreleased section	Required

Version Checks (FR-026)

Check	Requirement
package.json version present	Optional
CHANGELOG.md version present	Optional
Versions match	If both present

API Checks (FR-025)

Check	Requirement
contracts/ exists	Optional
API docs exist if contracts	Required if contracts
Endpoints documented	Required if contracts

Checklist Output Format

## Release Checklist

**Status**: Ready to Release / Not Ready

### Artifacts
| Status | Check | Details |
|--------|-------|---------|
| [PASS] | spec.md exists | |
| [PASS] | plan.md exists | |
| [FAIL] | All tasks complete | 5 tasks remaining |

### Documentation
| Status | Check | Details |
|--------|-------|---------|
| [PASS] | README.md exists | |
| [SKIP] | API docs | No contracts/ directory |

Recommendations

If release check fails:

Complete all remaining tasks in tasks.md
Ensure README.md has a usage section
Update CHANGELOG.md with release notes
Verify version numbers are consistent
Run release-check again to verify fixes

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: drillan-speckit-gates-release-checkdescription: > Use when this capability is needed.metadata: author: drillan---# release-checkValidates release readiness before creating a release.## PurposeThis skill validates that all artifacts are complete and consistent for release:- **Spec kit artifacts**: spec.md, plan.md, tasks.md exist and are complete- **Documentation**: README.md, CHANGELOG.md have required sections- **Versioning**: Version numbers are consistent across package.json and CHANGELOG- **API docs**: API documentation matches contract specifications## OutputThe skill outputs a **ReleaseChecklist** with:- Overall readiness status (Ready/Not Ready)- Individual check items with pass/fail/skip status- Version consistency information- Specific issues to address before release## UsageThis is a manual skill - run it before creating a release:```bashnpx skills run release-check```Or via AI agent:```User: Check if we're ready for release```## Exit Codes| Code | Status | Meaning ||------|--------|---------|| 0 | Ready | All checks pass || 1 | Not Ready | Some checks failed || 3 | Error | Required files missing |## Checks Performed### Artifact Checks (FR-022)| Check | Requirement ||-------|-------------|| spec.md exists | Required || plan.md exists | Required || tasks.md exists | Required || All tasks complete | Required |### Documentation Checks (FR-023)| Check | Requirement ||-------|-------------|| README.md exists | Required || README.md has usage section | Required || CHANGELOG.md exists | Required || CHANGELOG.md has unreleased section | Required |### Version Checks (FR-026)| Check | Requirement ||-------|-------------|| package.json version present | Optional || CHANGELOG.md version present | Optional || Versions match | If both present |### API Checks (FR-025)| Check | Requirement ||-------|-------------|| contracts/ exists | Optional || API docs exist if contracts | Required if contracts || Endpoints documented | Required if contracts |## Checklist Output Format```## Release Checklist**Status**: Ready to Release / Not Ready### Artifacts| Status | Check | Details ||--------|-------|---------|| [PASS] | spec.md exists | || [PASS] | plan.md exists | || [FAIL] | All tasks complete | 5 tasks remaining |### Documentation| Status | Check | Details ||--------|-------|---------|| [PASS] | README.md exists | || [SKIP] | API docs | No contracts/ directory |```## RecommendationsIf release check fails:1. Complete all remaining tasks in tasks.md2. Ensure README.md has a usage section3. Update CHANGELOG.md with release notes4. Verify version numbers are consistent5. Run release-check again to verify fixes---> Converted and distributed by [TomeVault](https://tomevault.io/claim/drillan) — claim your Tome and manage your conversions.

Frequently asked questions

Drillan Speckit Gates Release Check