changelog
MANDATORY PREPARATION
Invoke /product-thinking — it contains the Context Gathering Protocol and the AI Slop Test. Follow the protocol before proceeding.
Mindset
A changelog is not a commit log. It's a story about what changed for users, written in their language. Engineers care about what was built. Users care about what they can do now. A good changelog bridges both — it's specific enough for engineers to recognize their work, and clear enough for users to understand the impact.
Step 1: Gather Parameters
Ask the user:
- Time range — what period does this changelog cover? Examples: "last 7 days", "last month", "since v2.1", "since 2026-03-01". If provided as the argument, use that.
- Format — text only, or text and video script? If video, the changelog will include a companion script suitable for a walkthrough recording.
Step 2: Analyze Changes
More from vgrss/acumen
features
Build and maintain a lightweight feature inventory. Use after shipping, when planning, or to understand the current product surface.
9measure
Check KPI health — what's working, what's not, where to dig deeper. Suggests /workshop for opportunities. Use for metric reviews, health checks, or when something feels off in the numbers.
9diagnose
Find current problems in the product based on data, value delivery for main personas, and current features. Suggests /workshop for ideation on solutions.
9scout
Build and maintain a living competitor map. Supports both quick scans and deep competitive analysis. Use when entering a new market, a competitor launches something, before scoping a feature, or for strategic positioning decisions.
9persona
Build and maintain behavioral personas grounded in real user patterns. Use when launching, after user research, or when user understanding feels stale.
9narrate
Write product communication for a specific audience, including when stakes are high and stakeholders disagree. Use for exec summaries, eng briefs, customer announcements, or tradeoff negotiations.
9