project-notes

Write repo-scoped Obsidian notes with YAML frontmatter and wikilinks.

2|Updated Jun 1, 2017
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill project-notes-carlos-algms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-notes
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/project-notes
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill project-notes-carlos-algms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you permanently record what happened in a specific repository—findings, investigations, decisions, and coding lessons—so future work doesn’t repeat the same research or lose crucial context.

Core Features & Use Cases

  • Repo-scoped, durable note storage: Saves notes under 020-work/project-notes/<project-name>/ with date-first filenames for stable sorting.
  • Structured capture for provenance: Supports reproducible investigations and clear decision records with forward-only history (no rewriting past outcomes).
  • Topic discovery via consistent formatting: Enforces required conventions like frontmatter schema, required sections such as ## Sources, and wikilink references for cross-notes.
  • Use cases: Log a bug investigation, document a technical decision, capture a coding lesson from failed tests, or create a reusable per-project reference note.

Quick Start

Ask the AI to save your latest project finding as a date-prefixed note under 020-work/project-notes/<project-name>/ with an appropriate topic slug and an ## Sources section.

Frequently Asked Questions about project-notes

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

FAQPage Schema
How do I log a technical decision or bug investigation in an Obsidian vault?▼

You can log a technical decision or bug investigation by saving findings as standardized Obsidian notes with YAML frontmatter, date-first filenames, and a mandatory ## Sources section for reproducible repo provenance.

What is a forward-only decision log for software development?▼

A forward-only decision log permanently records technical decisions and coding lessons without rewriting past outcomes, ensuring future work retains crucial context and avoids repeating prior research.

How do I structure project notes with wikilinks and frontmatter in Obsidian?▼

You structure project notes by applying strict folder conventions under 020-work/project-notes/, adding YAML frontmatter, and using wikilink-based cross-references to connect related investigations and decisions.

Does this project notes approach work for capturing coding lessons from failed tests?▼

Yes, this approach works for capturing coding lessons from failed tests by creating reusable per-project reference notes that document findings and prevent the same research from being repeated.

What folder structure is required for reproducible repo-scoped investigations?▼

Reproducible repo-scoped investigations require saving notes under 020-work/project-notes/<project-name>/ using date-first filenames for stable sorting and clear provenance tracking.

Why use a forward-only history instead of editing past project notes?▼

Using a forward-only history instead of editing past notes preserves original decision context and investigation outcomes, preventing historical data loss and maintaining accurate repo provenance.