Publish Notes Skill
[!IMPORTANT]
Draft user-facing release notes, store changelogs, and internal publish summaries.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Publish Notes Workflow
Goal: Convert verified changes into accurate user-facing and internal release notes.
Steps
- Gather inputs:
- Merged commits/diff, verification report, UAT signoff, deployment report, and STLC Stage 6 closure evidence (
skills/quality-engineering/quality-engineering-test-plan-authoring/references/lifecycle-and-roles.md).
- Product/store constraints, mobile platform/OS versions, and artifact build digest.
- Product evidence contracts (
docs/product/<slug>/evidence.json: measurement owner, MET baseline, instrumentation, guardrails).
- Load
common-operator-profile; carry inherited operator_profile without re-inferring.
- User-facing change
- Bug fix
- Security or privacy note
- Operational change
- No-user-impact internal change
- Draft notes:
- Use plain language and business outcomes for every tier;
operator_profile=business gets Public Notes as the primary artifact, Internal Notes as an appendix.
- Keep sensitive security details high-level.
- Respect platform character limits.
- Verify and persist:
- Cross-check notes against verified shipped scope and closure evidence; remove unshipped, blocked, or deferred claims.
- Separate delivery proof from customer ROI. Feature
feature_status=released preserved when product value observations are pending.
- Write run record to
artifacts/runs/[slug]/[compactISO]-publish-notes.json when allowed.
- Route process lessons, defect escapes, and release gaps to
retro-learn.
- Use after
deploy-release or uat-signoff to draft user-facing and internal release communication.
- Required inputs: shipped diff/commits plus verification or deployment report to cross-check against.
- Return BLOCKED only when no verified shipped scope exists to draft notes from. Feature released status is retained when product value is pending or inconclusive.
Handoff Payload
slug, operator_profile, public notes, internal notes, security/privacy notes, measurement contract refs when present, verification source, next workflow.
Blocking Questions
- Ask max 3 at a time with a recommended default and 2-3 options.
Output Template
# Release Notes: [Version]
## Public Notes
## Internal Notes
## Security Or Privacy Notes
## Verification Source
## Outcome Report
{schema_version: 1, run_id: "[run-id]", slug: "[slug]", workflow: publish-notes, feature_status: released, started_at: "[timestamp]", completed_at: "[timestamp]", requirement_trace: {brd_objectives: [], requirements: [], acceptance_criteria: [], srs: []}, completed_evidence: [], missing_evidence: [], decision_needed: [], recommended_next_workflow: retro-learn, cost: {source: unavailable}, agent: {identity: "[agent-identity]", model: "[model]"}}
## Next Workflow
retro-learn
## Cost Report
Call `get_session_cost(workflow="publish-notes")` before final handoff.
1---2name: publish-notes3description: "Draft user-facing release notes, store changelogs, and internal publish summaries."4metadata:5 source: https://skillmd.com/skills/hoangnguyen0403/publish-notes6 internal: true7 triggers:8 keywords:9 - publish notes10 - workflow11---1213# Publish Notes Skill1415> [!IMPORTANT]16> Draft user-facing release notes, store changelogs, and internal publish summaries.1718Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.1920## Instructions2122When the user asks to perform this workflow, execute the following steps:232425# Publish Notes Workflow2627Goal: Convert verified changes into accurate user-facing and internal release notes.2829## Steps30311. Gather inputs:32 - Merged commits/diff, verification report, UAT signoff, deployment report, and STLC Stage 6 closure evidence (`skills/quality-engineering/quality-engineering-test-plan-authoring/references/lifecycle-and-roles.md`).33 - Product/store constraints, mobile platform/OS versions, and artifact build digest.34 - Product evidence contracts (`docs/product/<slug>/evidence.json`: measurement owner, MET baseline, instrumentation, guardrails).35 - Load `common-operator-profile`; carry inherited `operator_profile` without re-inferring.36 - User-facing change37 - Bug fix38 - Security or privacy note39 - Operational change40 - No-user-impact internal change413. Draft notes:42 - Use plain language and business outcomes for every tier; `operator_profile=business` gets Public Notes as the primary artifact, Internal Notes as an appendix.43 - Keep sensitive security details high-level.44 - Respect platform character limits.454. Verify and persist:46 - Cross-check notes against verified shipped scope and closure evidence; remove unshipped, blocked, or deferred claims.47 - Separate delivery proof from customer ROI. Feature `feature_status=released` preserved when product value observations are pending.48 - Write run record to `artifacts/runs/[slug]/[compactISO]-publish-notes.json` when allowed.49 - Route process lessons, defect escapes, and release gaps to `retro-learn`.50- Use after `deploy-release` or `uat-signoff` to draft user-facing and internal release communication.51- Required inputs: shipped diff/commits plus verification or deployment report to cross-check against.52- Return BLOCKED only when no verified shipped scope exists to draft notes from. Feature released status is retained when product value is pending or inconclusive.53## Handoff Payload54- `slug`, `operator_profile`, public notes, internal notes, security/privacy notes, measurement contract refs when present, verification source, next workflow.55## Blocking Questions56- Ask max 3 at a time with a recommended default and 2-3 options.5758## Output Template5960```md61# Release Notes: [Version]6263## Public Notes6465## Internal Notes6667## Security Or Privacy Notes6869## Verification Source7071## Outcome Report72{schema_version: 1, run_id: "[run-id]", slug: "[slug]", workflow: publish-notes, feature_status: released, started_at: "[timestamp]", completed_at: "[timestamp]", requirement_trace: {brd_objectives: [], requirements: [], acceptance_criteria: [], srs: []}, completed_evidence: [], missing_evidence: [], decision_needed: [], recommended_next_workflow: retro-learn, cost: {source: unavailable}, agent: {identity: "[agent-identity]", model: "[model]"}}7374## Next Workflow7576retro-learn7778## Cost Report79Call `get_session_cost(workflow="publish-notes")` before final handoff.80```81