How does the Note Taker skill organize captured information?

It categorizes insights into four specific markdown files within your project's docs directory: decisions.md, action-items.md, blockers.md, and findings.md.

Can I see what was captured after the skill runs?

Yes, the skill provides a summary output listing exactly how many new entries were added to each specific documentation file.

Does it capture routine file edits and search operations?

No, the skill is designed to skip routine operations and focus only on high-level insights, decisions, and actionable tasks to keep your docs concise.

Will it overwrite my existing project notes?

No, the skill is programmed to append new entries to existing files using date headers, ensuring your previous documentation remains safe and organized.

What happens if the docs directory doesn't exist?

The skill will automatically create the docs folder and the necessary markdown files if they are not already present in your repository.

Note Taker & Project Capture

Name: Note Taker & Project Capture
Author: karbassi

bykarbassi

•

Content Management

Captures key decisions, action items, and technical findings from your conversation into structured markdown documentation.

The Note Taker skill automates the tedious process of project documentation by extracting critical insights directly from your development sessions. It scans your conversation for architectural decisions, pending tasks, technical blockers, and important discoveries, then organizes them into standardized markdown files within a docs directory. By maintaining a persistent record of the rationale behind code changes and tracking unresolved issues, it ensures that project context is never lost and that follow-up actions are clearly identified for future sessions.

Key Features

01Automatic extraction of architectural decisions and their rationale

02Structured logging of technical blockers and unresolved questions

03Context-aware identification of research findings and insights

04Non-destructive appending to existing documentation files with date headers

051 GitHub stars

06Dynamic tracking of action items and project follow-ups

Use Cases

01Recording the 'why' behind complex refactoring or design choices

02Maintaining a technical discovery log when exploring new libraries or APIs

03Generating a punch-list of tasks after a debugging or brainstorming session

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add karbassi/claude-plugins capture

For use in Claude.ai and ChatGPT

Download Skill