change-logkeeper

Record changes and task movements in a centralized changelog.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/kanitmann01/TitanTale-Analytics --skill change-logkeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-logkeeper
Source: https://github.com/kanitmann01/TitanTale-Analytics/tree/main/.cursor/skills/change-logkeeper
Command: npx skills add https://github.com/kanitmann01/TitanTale-Analytics --skill change-logkeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain modular ops changelog entries and coordinate movement of tasks between status folders to keep the project snapshot accurate and auditable.

Core Features & Use Cases

  • Record changes: add entries to ops/changes/YYYY-MM with a timestamp, role, and short description.
  • Move tasks: relocate tasks between ops/tasks subfolders and update the Status field accordingly.
  • Update snapshots: keep ops/CURRENT.md in sync with in-progress and recently completed work.

Quick Start

Record a new change in ops/changes/YYYY-MM and update ops/CURRENT.md to reflect completion.

Frequently Asked Questions about change-logkeeper

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

FAQPage Schema
How do I maintain an audit trail for project management task movements?

An ops changelog records changes and task movements in a centralized log using the format 'YYYY-MM-DD | Role | Short description', ensuring traceability and keeping the project snapshot accurate across ops directories.

How do I record changes in a modular ops changelog?

Record changes in a modular ops changelog by adding entries to ops/changes/YYYY-MM with a timestamp, role, and short description, then update ops/CURRENT.md to reflect the current state of in-progress and recently completed work.

What's the best way to keep a project snapshot accurate and auditable?

The best way to keep project snapshots accurate is applying a structured changelog workflow to ops/CURRENT.md, ops/changes/, and ops/tasks/ to record task movements and changes with timestamps, ensuring full traceability.

Can I move tasks between status folders and still maintain traceability?

Yes, you can move tasks between ops/tasks subfolders while maintaining traceability by updating the task Status field and adding a concise entry to ops/changes/YYYY-MM with a timestamp, role, and description.

Do I need any specific dependencies to run a task-management changelog workflow?

No dependencies are required to run this task-management changelog workflow. It operates directly on your project's ops directory structure, managing files like ops/CURRENT.md, ops/changes/, and ops/tasks/ without external tool integrations.