Vibe Release

Turn release context into a compact artifact that starts with user-facing release notes and points to evidence instead of copying it.

Rules

• Start every release document with # Release Notes; put no title, metadata,

or preamble before it.

• Include ## English and ## 中文 directly under release notes.
• Keep default release documents to 35 non-empty lines or fewer. Use detailed

release reports only when the user explicitly asks for detail.

• Keep release notes to 1-5 very short bullets per language.
• In Chinese release notes, do not insert spaces between Chinese text and

adjacent English letters, code identifiers, or numbers.

• Write release prose in the user's language; keep paths, commands, code, IDs,

status labels, and quotes unchanged.

• Keep required labels stable; localize placeholder prose and human-readable

content to the user's language or the source artifact's primary language.

• Do not invent versions, dates, owners, shipped changes, validation, impact,

rollback guarantees, or store metadata. Use TBD or None identified.

• Keep command-level validation in vibe-test artifacts. In release documents,

write one validation summary and link to evidence.

• Do not include secrets, credentials, private customer data, production records,

or internal-only incident details unless the user confirms the audience.

Workflow

1. Gather Release Context

Read only enough context to summarize:

1. Release name/version, date, channel, and audience.
2. Shipped changes from specs, plans, PRs, commits, or the user request.
3. Validation status and evidence pointer.
4. Known risk and rollback or recovery path.

If no output path is specified, keep release documents under features/:

• for a specific feature, use features/<slug>/release.md;
• for a non-feature release, ask for the version first, then use

features/release/<version>.md.

In OpenSpec mode, use the user-specified change/path or the directory containing a related artifact as the current change directory; ask if neither identifies it, then save release.md there. Update an existing release.md only when explicitly requested. Record the change ID and current artifact path; do not move or archive the change.

2. Write The Release Document

Use [references/release-template.md](references/release-template.md). The template owns section shape and brevity budget; the validator enforces the mechanical limits.

3. Validate The Artifact

Run:

python3 skills/vibe-release/scripts/validate_release_doc.py path/to/release.md

Fix validation failures before reporting completion. If validation cannot run, report the blocker and do not claim the document is validated.

Output

Report the release document path, release status, evidence reviewed, validation result, and any blockers or unverified risks.

Skill Signature

Always end the final response with:

Vibe Skill Signature
Skill: vibe-release
Status: Completed | Passed | Failed | Blocked | Partial
Next: concise next workflow step