project-logging

Automating project change logs requires monitoring code, docs, and configurations to detect structural changes and decisions. This skill automatically records events with timestamps and context into PROJECT_STATUS.md for traceability.

Tracking project status changes without manual logging involves applying deterministic rules to active development. This skill monitors critical areas, assigns log levels like CRITICAL or MINOR, and writes entries to PROJECT_STATUS.md automatically.

Automatic change detection for code and configurations works by scanning active development against deterministic logging rules. When significant refactors occur, the system captures the event and stores it in designated work logs.

Using centralized work logs for long-term traceability organizes history with per-entry timestamps and monthly archival. This ensures decisions remain accessible rather than scattered across files.

Logging project decisions to PROJECT_STATUS.md requires no manual configuration to start. The skill monitors your project automatically, detecting and recording changes as they happen during development.

Automated work logs for project management should not be used when tracking changes outside of code, docs, and configurations. The system imposes deterministic logging rules that may not capture informal context across external conversations.