Skip to content
Skills Library
Programming · Writing

draft

/draft

Writes the release note for one tenant and window from reconciled, tiered items - fills the tenant's template section by section, one short line per item, every line carrying at least one evidence ID and a visible link (tracker issue, release, email subject and date, or chat permalink), carry-over items first, Released only for T1, Completed pending release for T2, and Mentioned unconfirmed for T3 on internal notes only - then proves every citation resolves for gate G5. Also parses an uploaded template into sections. Use it when a run's items are ready to be written up, when someone asks to re

Licence
MIT
Last repository change
31.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Writes the release note for one tenant and window from reconciled, tiered items - fills the tenant's template section by section, one short line per item, every line carrying at least one evidence ID and a visible link (tracker issue, release, email subject and date, or chat permalink), carry-over items first, Released only for T1, Completed pending release for T2, and Mentioned unconfirmed for T3 on internal notes only - then proves every citation resolves for gate G5. Also parses an uploaded template into sections. Use it when a run's items are ready to be written up, when someone asks to re

Original author description

Writes the release note for one tenant and window from reconciled, tiered items - fills the tenant's template section by section, one short line per item, every line carrying at least one evidence ID and a visible link (tracker issue, release, email subject and date, or chat permalink), carry-over items first, Released only for T1, Completed pending release for T2, and Mentioned unconfirmed for T3 on internal notes only - then proves every citation resolves for gate G5. Also parses an uploaded template into sections. Use it when a run's items are ready to be written up, when someone asks to re

How it works

  1. Before anything else
  2. Steps
  3. Rules
Original SKILL.md headings · 39 lines, 325 words
SKILL.md preview
---
name: draft
description: Writes the release note for one tenant and window from reconciled, tiered items - fills the tenant's template section by section, one short line per item, every line carrying at least one evidence ID and a visible link (tracker issue, release, email subject and date, or chat permalink), carry-over items first, Released only for T1, Completed pending release for T2, and Mentioned unconfirmed for T3 on internal notes only - then proves every citation resolves for gate G5. Also parses an uploaded template into sections. Use it when a run's items are ready to be written up, when someone asks to redraft a section, or to turn an uploaded template into the tenant's template.md. Do not use it to rewrite for voice (humanise), to decide tiers or tenants (reconcile), to send (send), or for routing and gates (release-notes).
metadata:
  author: Sayandip Bagchi
---

# Draft: every line cited

## Before anything else

The router runs first (`${CLAUDE_PLUGIN_ROOT}/skills/release-notes/SKILL.md`). Input: tenant, run ID,
window, items from `reconcile`. Template rules: `references/template-parsing.md`. Citation format:
`references/citation-format.md`.

## Steps

1. Read `tenants/<name>/template.md` and the audience from `config.json`.
2. Call rn-harness `ledger_carry_over(tenant)`. Carried items that are now T1 go first under Released
   with "previously reported as pending"; still-T2 carried items go first under the pending section.
3. Place each item in its template section by tier and type: Released (New, Improved, Fixed, Known
   issues by tracker issue type or label), pending (T2), mentioned (T3, internal only).
4. Write one line per item: what changed, for whom, in plain words, then the citation. Use the
   tracker title as the base; use comms excerpts only to clarify, never to add a claim the tracker or
   release does not support.
5. Fill `{{banner}}` with every partial, unknown or unreachable source and every excluded source,
   or remove it when all sources are complete.
6. Build `lines = {line_id: [evidence_ids]}` and call `citation_resolve(tenant, run_id, lines)`. Any
   uncited line or unknown ID fails G5: fix or remove the line.
7. Fill the trace appendix from `${CLAUDE_PLUGIN_ROOT}/skills/release-notes/templates/trace-appendix.md`.
8. Save to `tenants/<name>/runs/<run_id>/draft.md` and `trace.md`, and return both with the line map.

## Rules

- **No line without evidence.** No summary sentences that make claims ("a big release for
  reliability") unless every item they summarise is cited in the same section.
- **No invented facts.** No dates, versions, owners, metrics or customer names that are not in the
  evidence. A missing fact stays missing.
- **T2 and T3 never under Released.**
- **Empty window:** a short note that says no items met the release definition in the window, with
  the trace appendix. No padding.
- **External audience:** no Mentioned block, no internal links (use public reference IDs or none),
  no internal people's names, no other customers' names.
- **Held items never appear** in the note; they appear only in the trace appendix's held table.
Files in this package (3)
  • SKILL.md 3 KB
  • references/citation-format.md 1 KB
  • references/template-parsing.md 2 KB

Versions

RepositoryScoreLicence
This page · SayandipBagchi/release-notes-plugin90MIT
tony/skills100MIT
eclecticv/skills100MIT
drafthq/draft100MIT
gagoar/foghorn100MIT
anthropics/claude-for-legal100Apache-2.0
tance-mang/chinese-webnovel-skills100MIT
alirezarezvani/gaios100MIT
lawdroidai/legal-aid-plugin100Apache-2.0

Database snapshot: 13.11.2026 · package version e6e5319c3072 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90reconcile
    Turns a run's evidence into release-note items for one tenant - joins email and chat mentions to tickets by extracting ticket keys, removes duplicates, maps every item to exactly one tenant with the deterministic mapping rules (items matching zero or two or more tenants are…
  • 100release-notes
    Routes and governs release-note work for one tenant (an org, client, product, BU or OU). Holds the model gate (Opus or above), tenant resolution, the blocking gates G0 to G9 (model, tenant, window, collect completeness, reconcile, grounded draft, fact-locked humanise, review,…
  • 95release-note-draft
    Draft structured release notes from git history. Use when the user wants to write release notes, a changelog entry, a sprint summary, or wants to know what changed since a tag, branch, or previous release — even without the phrase "release notes". Not for publishing, tagging, or…
  • 95release-notes
    Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
  • 100draft-release-notes
    Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
  • 100mflux-pr-docs
    Write the PR body for the current mflux branch and show it to the developer for approval. Fills the What section, the release-note block and the Verification section of the PR template. Use when the developer asks to write, fill or update a PR description or a release note.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.