skills.rest
aplaceforallmystuff
aplaceforallmystuffCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

log-to-project

Log project activity to CHANGELOG.md, Sessions/, and Decisions/ folders.

17|3|Updated Jan 4, 2026
Search Tags:#workflow#changelog#documentation#decisions#sessions#project#log
One-click install
npx skills add https://github.com/aplaceforallmystuff/minervia-starter-kit --skill log-to-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: log-to-project
Source: https://github.com/aplaceforallmystuff/minervia-starter-kit/tree/main/skills/log-to-project
Command: npx skills add https://github.com/aplaceforallmystuff/minervia-starter-kit --skill log-to-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logs project activity to a dedicated project folder, preserving a changelog, session notes, and decision records to keep context across work sessions.

Core Features & Use Cases

  • Canonical project folder structure management (PROJECT.md, CHANGELOG.md, Sessions/, Decisions/)
  • Record and update session notes and decisions to reflect progress and rationale
  • Maintain a complete activity history for onboarding, handoffs, and audits

Quick Start

Identify the target project folder inside 02 Projects/, then update CHANGELOG.md, create a session log for substantial work, and add a decision record when important choices are made

Frequently Asked Questions about log-to-project

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

FAQPage Schema
How do I maintain a project changelog and preserve session history?▼

To maintain a project changelog, log activity to dedicated project folders and update CHANGELOG.md, create session logs in Sessions/, and add decision records to Decisions/ to preserve history across work sessions.

What is the best way to document project decisions and rationale for future reference?▼

Documenting project decisions involves archiving rationale in a Decisions/ folder, ensuring important choices are recorded and searchable for future onboarding, handoffs, and audits.

How do I record session outcomes and track progress across multiple projects?▼

Record session outcomes by identifying the target project folder inside 02 Projects/ and creating a session log for substantial work, updating documentation to reflect progress across multiple projects.

Does this project logging approach require a specific folder structure?▼

Yes, this project logging approach enforces a canonical folder structure requiring updates to PROJECT.md, CHANGELOG.md, Sessions/, and Decisions/ as applicable to maintain a complete activity history.

When should I create a session log versus updating the changelog?▼

You should update the CHANGELOG.md for any logged activity, create a session log specifically for substantial work, and add a decision record only when important choices are made.

Related Skills

Explore More Product & Management Skills→
YoniChechikYoniChechik

cd-permanent

Change the working directory to a validated path within the project root.

Community
Basic
ZateZate
9

worklog-management

Maintain a markdown worklog with commit references for completed tasks.

Community
Intermediate
bdbchbdbch
2

changelog-writing

Generates changelogs from commit history using 'Keep a Changelog' format and Changeset files.

Community
Intermediate
esopianesopian
2

checkpoint

Save git branch, status, diffs, and logs as session checkpoints.

Community
Basic