record-progress

Generates daily Obsidian progress changelog files from journal entries and modified project notes.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/tmwang7324/Obsidian-Notes --skill record-progress-tmwang7324
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-progress
Source: https://github.com/tmwang7324/Obsidian-Notes/tree/main/.claude/skills/record-progress
Command: npx skills add https://github.com/tmwang7324/Obsidian-Notes --skill record-progress-tmwang7324

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually writing end-of-day progress logs across multiple projects is tedious and easy to skip. This Skill automates the synthesis of a day's work — the dated journal plus every project note modified that day — into structured, per-project changelog files in an Obsidian vault, complete with frontmatter, goal links, and cited sources. ## Core Features & Use Cases - Deterministic day scan: A bundled PowerShell script resolves the date, computes the Monday-based week folder, locates the journal, and lists every project note modified that day with (DONE)/(INCOMPLETE)/(DECISION) markers. - Structured progress files: Writes one (C) YYYY-MM-DD.md per active project with type: progress frontmatter, a summary, an Advances goal link, Done/Decisions/Next steps sections, and cited sources. - Iteration Log wiring: Routes unfinished work into type: next-step files, linking existing logs instead of duplicating them. - Use Case: At the end of a working session, ask to record today's progress and receive one changelog file per project that saw activity, with decisions linked to their ADRs and open threads captured as next steps. ## Quick Start Ask the assistant to record today's progress in the vault and it will scan the day's journal and modified project notes, then write the dated progress files automatically.

Frequently Asked Questions about record-progress

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

FAQPage Schema
How do I log daily progress in an Obsidian vault automatically?

Run the record-progress workflow at the end of the day. It scans the dated journal and all project notes modified that day, then writes one progress file per active project with Done items, decisions, next steps, and cited sources.

How does the skill decide what counts as finished work?

It reads the user's (DONE) and (INCOMPLETE) markers in note filenames and bodies, detected by the scan script. DONE items go into the Done section, INCOMPLETE items become next steps, and unmarked notes are folded in as supporting evidence.

Does it work if there is no journal entry for the date?

Yes, it proceeds from the modified working notes alone but warns that the narrative source is missing. If only the journal exists with no working notes, it flags the entry as thin since the convention requires at least two sources.

What happens if a progress file already exists for that date?

The scan detects existing progress files across all Week of folders and reports them. The skill asks before overwriting and defaults to merging new Done lines rather than replacing the existing file.

Can it handle a note that belongs to multiple projects?

Yes. When a modified note touches several projects, it is cited as a source under each relevant project's progress file for that date.