dotcraft-release-draft

name	dotcraft-release-draft
description	Draft DotCraft GitHub Release notes from repository evidence. Use when preparing or revising release copy for a version.

Release Draft

Use this skill to produce an English GitHub Release body that feels consistent with recent DotCraft releases while staying grounded in current repo evidence. Evidence may be localized; synthesize the final release copy in English.

Standard Workflow

1. Identify the target version, reference version or URL, previous tag, and target commit/branch.
2. Inspect the reference release first when provided. Use read-only release inspection commands such as:

gh release view vX.Y.Z --repo DotHarness/dotcraft --json name,tagName,body,url,publishedAt,assets

3. Read the target What's New catalog when present:

desktop/resources/whats-new/releases/<version-without-v>.json

Use each card's title, summary, and media.url as the core feature list and GIF source.

4. Read concise supporting docs for each feature before expanding copy. Discover the current documentation locales and prefer:

• the current README and its localized mirrors
• feature documentation in every currently supported documentation locale
• relevant developer or SDK documentation across those locales
• targeted rg results for feature names, PR titles, and config keys

5. Generate or reconstruct the GitHub "What's Changed" section. releases/generate-notes is allowed only as a non-publishing helper that returns text:

gh api repos/DotHarness/dotcraft/releases/generate-notes -X POST -f tag_name=vX.Y.Z -f target_commitish=<branch-or-sha> -f previous_tag_name=vA.B.C

Fallbacks: git log --oneline vA.B.C..<target> and PR titles from gh pr view / gh pr list when available.

6. Draft the release body as a copy-paste Markdown template. Publishing is a user action.

Release Shape

Match the reference release's structure unless the user asks for a different format. For current DotCraft releases, use:

# DotCraft vX.Y.Z

DotCraft vX.Y.Z is a major release focused on ...

## Core Features

1. **Feature Name**
   Short user-facing paragraph.

![](https://github.com/DotHarness/resources/raw/master/dotcraft/whats-new/feature.gif)

## Infrastructure and Experience Improvements

1. **Improvement Name**
   Short user-facing paragraph.

## What's Changed

* ...

**Full Changelog**: https://github.com/DotHarness/dotcraft/compare/vA.B.C...vX.Y.Z

Writing Rules

• Write the complete release body in English. Keep identifiers, product names, code, and URLs in their canonical form.
• Match the reference release's tone, heading style, and level of detail. If the reference is v0.1.6, use concise copy with numbered feature sections.
• Lead with user-visible capabilities from What's New. Put reliability, tooling, and polish in "Infrastructure and Experience Improvements."
• Use the GIF URLs exactly from the What's New catalog when available.
• Expand terse What's New summaries with repo/docs evidence, not speculation.
• Preserve established product terminology. Examples (e.g., not an exhaustive list) include Agent Teams, Mission, Team Leader, App Binding, ChatGPT subscription, and What's New; inspect current product and documentation sources for additional terms.
• Mention plan tiers only when supported by docs/code or existing release copy.
• Preserve generated "What's Changed" links and attribution. Translate any non-English entry titles faithfully so the release body remains English; do not add unsupported claims.
• Never run commands that create, edit, publish, delete, or upload assets to a GitHub Release, such as gh release create, gh release edit, gh release delete, or gh release upload.
• State that the user must perform the actual GitHub Release publishing step; you only provide the draft template.
• If a tag or release does not exist yet, state that clearly and draft against the current branch/HEAD.
• If evidence conflicts, surface the assumption briefly instead of silently choosing.

Quality Bar

Before returning the draft:

• Confirm every highlighted feature has an evidence source.
• Confirm each media link renders from https://github.com/DotHarness/resources/raw/master/dotcraft/whats-new/.
• Confirm the compare range uses the previous release tag and target version.
• Confirm the release body is English except for canonical identifiers, product names, code, and URLs.
• Keep the answer copy-paste ready. Add a short note after the draft only for sources, caveats, or missing data.