Changelog Management

"If it's not logged, it didn't happen."

TL;DR

Maintains changelog.md as the cross-session continuity log. Records significant decisions, completions, amendments, insights, blockers, and discoveries with date, type, description, rationale, and constitutional principle references. Read during session protocol (Step 2: State Recovery) to understand what happened in recent sessions. [EXPLICIT]

Procedure

Step 1: Discover

• Read existing changelog.md (or create if missing)
• Identify the event to log (decision, completion, amendment, etc.)
• Determine which constitutional principles are involved

Step 2: Analyze

• Classify event type: decision, completion, amendment, insight, blocker, discovery
• Draft description (concise, actionable)
• Identify rationale (why this matters)
• Map to constitutional principles

Step 3: Execute

• Append entry to changelog.md under today's date:

  ## 2026-03-23
  - **[decision]**: Selected strip-over-escape for input sanitization — simpler, covers primary vector (copy-paste) [Principle VII, XIV]
  - **[completion]**: Firebase Auth integration complete — email + Google social login [Principle I, VII]
  - **[insight]**: Audit log paths must be fully qualified for recovery — captured in insights/security.md [Principle VII]
  

• If no section for today exists, create it
• Keep entries chronological (newest date at top)

Step 4: Validate

• Entry includes date, type, description, rationale, principles
• No duplicate entries for the same event
• Changelog is readable by someone with zero context (self-sufficient entries)
• Recent entries (last 5) are loadable during session protocol

Quality Criteria

• Entry has correct type tag
• Description is concise and self-sufficient
• Constitutional principles referenced
• Date is correct
• No duplicates
• Evidence tags applied

Related Skills

• session-protocol — Reads changelog during state recovery
• tasklog-management — Complementary log for task tracking
• continuous-learning — Insights logged here and in insights/

Usage

Example invocations:

• "/changelog-management" — Run the full changelog management workflow
• "changelog management on this project" — Apply to current context

Assumptions & Limits

• Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
• Requires English-language output unless otherwise specified [EXPLICIT]
• Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate