pmstudio-changelog

Generate and maintain a chronological changelog from CLAUDE.local.md and Meeting Notes.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill pmstudio-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmstudio-changelog
Source: https://github.com/rkz91/coco/tree/main/skills/change-log
Command: npx skills add https://github.com/rkz91/coco --skill pmstudio-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and ongoing maintenance of a structured change log for a product or platform by consolidating scattered notes, memory items, and meeting outcomes into an auditable, chronological record.

Core Features & Use Cases

  • Init: backfill a new changelog from existing notes and memory sources to establish a baseline.
  • Update: append new entries as changes occur, preserving a clear, chronological history.
  • Release: generate concise release notes from accumulated entries for stakeholders.
  • Works with sources like CLAUDE.local.md Recent Changes and Meeting Notes to stay aligned with decisions and discussions.

Quick Start

Create a new changelog and start logging changes from CLAUDE.local.md.

Frequently Asked Questions about pmstudio-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a product changelog from meeting notes?

Backfill a structured changelog by using the init mode to consolidate existing notes and memory sources into a chronological, append-only baseline record.

How do I generate release notes from an existing change log?

Generate release notes by applying the release mode to summarize accumulated changelog entries into concise, stakeholder-facing documentation for version updates.

How do I backfill a structured changelog from scattered documentation?

Backfill a structured changelog by using the init mode to consolidate existing notes and memory sources into a chronological, append-only baseline record.

What is the best way to maintain an append-only audit trail for product management?

Maintain an append-only audit trail by applying the update mode to append new entries chronologically, ensuring no duplicates while capturing metadata like date, type, impact, and responsible parties.

Can I track product changes using CLAUDE.local.md recent changes?

Track product changes by consolidating CLAUDE.local.md recent changes into a structured log, appending new entries with metadata fields for impact and responsible parties.