convert-flat-process-notes-to-dir

Split flat process-notes.md by ## headings into dated per-entry files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Converts a legacy flat process-notes.md file into the per-entry process-notes/ folder format. Use when the process-notes skill refuses to write because it detects the old format, or when the user explicitly requests /project-docs:convert-flat-process-notes-to-dir.

Core Features & Use Cases

  • Splits the flat file on every ## heading, creating individual entry files under process-notes/.
  • Extracts dates from headings and writes dated entries as process-notes/YYYY-MM-DDTHHMM-slug.md and undated entries as process-notes/NNNN-slug.md, preserving order.
  • Renames the original to process-notes.md.archive as a safety net and prints a detailed conversion summary.

Quick Start

Run the Python script to convert an existing process-notes.md into the per-entry process-notes folder and archive the original.

Frequently Asked Questions about convert-flat-process-notes-to-dir

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

FAQPage Schema
How do I convert a flat process-notes.md file into a structured folder format?▼

To convert a flat process-notes.md file into a structured folder format, run the migration script to split the file by ## headings, extract dates, and store entries as individual markdown files inside a process-notes/ directory.

Why does my process notes skill refuse to write to an existing markdown file?▼

Your process notes skill refuses to write because it detects a legacy flat process-notes.md format instead of the expected per-entry folder structure, requiring migration to the new directory format before writing can proceed.

How are dated and undated markdown entries handled during process notes migration?▼

During process notes migration, dated entries extracted from headings are stored as process-notes/YYYY-MM-DDTHHMM-slug.md files, while undated entries are stored as process-notes/NNNN-slug.md files to preserve their original order.

What happens to the original process-notes.md file after migrating to a folder structure?▼

After migrating to a folder structure, the original process-notes.md file is safely renamed to process-notes.md.archive, preserving the legacy content as a backup while the new per-entry directory takes over.

Do I need any external dependencies to split process notes into individual files?▼

No external dependencies are required to split process notes into individual files, as the conversion is handled entirely by a standalone Python script that parses headings and manages the file structure output.

Can I verify the results after converting a flat process notes file into a directory?▼

Yes, you can verify the results of converting a flat process notes file because the script outputs a detailed conversion summary that validates the newly created per-entry markdown files and archived original.