project-notes

Synthesize closed sprint beads into structured RELEASE-NOTES.md entries.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill project-notes-cosmicdreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-notes
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/sprint/skills/project-notes
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill project-notes-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of compiling sprint accomplishments into consistent, readable release notes by automatically synthesizing closed sprint work into a project-level changelog entry.

Core Features & Use Cases

  • Beads-to-Release-Notes Synthesis: Reads closed beads from .beads/sprint.db and drafts one well-structured analysis-reports/RELEASE-NOTES.md entry per card.
  • Git Log Context Enrichment: When an associated worktree exists for an issue: frontmatter field, it pulls the last commits to inform the “Approach” and “Files touched” sections.
  • Team-Lead Confirmation Workflow: Produces drafts for review and blocks file writes until explicit approval is given.
  • Vault Snapshot Export: Archives the new sprint notes into the Neurons Obsidian vault under a per-project, per-date path for cross-project querying.

Quick Start

Use the sprint project-notes skill to generate draft entries from your closed sprint beads and git history, then ask for confirmation to prepend them into analysis-reports/RELEASE-NOTES.md.

Frequently Asked Questions about project-notes

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

FAQPage Schema
How do I generate release notes from completed sprint work automatically?

This Skill synthesizes closed sprint beads from `.beads/sprint.db` into a structured `RELEASE-NOTES.md` entry, drafting one formatted markdown block per card to document sprint accomplishments automatically.

Can I enrich sprint documentation with git log history from issue worktrees?

Yes, sprint documentation can be enriched by pulling git log history from associated issue worktrees. It extracts commit history to inform the “Approach” and “Files touched” sections of the release notes.

What is the workflow for updating a project-level RELEASE-NOTES.md file?

The workflow for updating `RELEASE-NOTES.md` involves drafting entries from closed beads, requesting team-lead confirmation, and prepending approved content into `analysis-reports/RELEASE-NOTES.md` to maintain a chronological project changelog.

Does release note generation work with an Obsidian vault for cross-project querying?

Yes, release note generation works with an Obsidian vault by archiving sprint notes into a Neurons vault snapshot path. It saves content under a per-project, per-date path to enable cross-project querying.

Can I use Kanban delivery data to compile project reporting without manual formatting?

You can use Kanban delivery data stored as closed beads to compile project reporting without manual formatting. It reads `.beads/sprint.db` and outputs fixed markdown formats for each card.

Do I need team-lead approval before writing sprint documentation to project files?

Yes, you need team-lead approval before writing sprint documentation to project files. The system produces drafts for review and blocks file writes to `RELEASE-NOTES.md` until explicit approval is given.