process-notes

Create timestamped atomic notes in process-notes/ to preserve project decisions and progress.

4|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ttorres33/project-docs --skill process-notes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-notes
Source: https://github.com/ttorres33/project-docs/tree/main/skills/process-notes
Command: npx skills add https://github.com/ttorres33/project-docs --skill process-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Process Notes Documentation Skill helps teams capture and preserve a complete, chronological history of a project by creating atomic entries in a dedicated process-notes/ folder. Each entry is timestamped and named, enabling grep-friendly searching and easy retrospective review of decisions, milestones, and dead ends.

Core Features & Use Cases

  • Atomic entries in process-notes/ to keep work small and easily grep-able
  • Readable workflow for when to update notes (context window, milestones, explicit user requests)
  • Automatic naming and organization of entries to preserve history and enable audits

Quick Start

Create a new process-notes entry in process-notes/ using the standard template.

Frequently Asked Questions about process-notes

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

FAQPage Schema
How do I document project decisions and milestones without losing chronological history?▼

Capture project decisions by creating atomic, timestamped entries in a dedicated process-notes/ folder. This approach preserves a complete chronological history of decisions, milestones, and dead ends, preventing the loss of important project context over time.

What is an atomic process note and when should I create one?▼

An atomic process note is a single, timestamped record of a project event, decision, or dead end. Create one when reaching a milestone, hitting a dead end, or receiving an explicit request to document progress, ensuring entries remain small and easily grep-able.

How do I organize project history entries so they are easy to search retrospectively?▼

Organize project history by placing atomic entries into a process-notes/ directory with per-entry filenames and a fixed structure. This naming and organization strategy enables grep-friendly searching and makes retrospective review of the project timeline straightforward.

Can I modify existing project history entries after they are created?▼

No, existing process note entries are never modified. The system enforces an append-only workflow where new entries are created in the process-notes/ folder to preserve the integrity of the project's decision history and enable reliable audits.

Does this documentation method work for software development and process reviews?▼

Yes, this method is applied to documenting sessions, decisions, dead ends, and milestones across both software projects and process reviews. It provides a standardized template for capturing progress regardless of the specific project type.