session-documentation

Automate session documentation into structured Markdown files in the docs/ directory.

4|Updated Nov 22, 2025

Search Tags:#documentation #markdown #guide #adr #knowledge capture #session log

Ready to run

npx skills add https://github.com/r1cA18/dotfiles --skill session-documentation-r1ca18

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-documentation
Source: https://github.com/r1cA18/dotfiles/tree/main/skills/session-documentation
Command: npx skills add https://github.com/r1cA18/dotfiles --skill session-documentation-r1ca18

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of documenting your work sessions, ensuring that your progress, decisions, and learnings are captured in an organized and accessible manner within your project's documentation.

Core Features & Use Cases

Structured Documentation: Creates Markdown files in docs/ based on session content.
Template Selection: Supports different documentation types (guides, ADRs, research logs, session logs) with customizable templates.
Use Case: After a coding session where you implemented a new feature and made a key technical decision, you can trigger this skill to automatically generate a guide for the feature and an Architecture Decision Record (ADR) for the decision, saving you manual documentation time.

Quick Start

Document the current session's work into the docs directory using the default guide template.

Frequently Asked Questions about session-documentation

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

FAQPage Schema

How do I automatically generate markdown documentation for my coding sessions?▼

You can automate session documentation by generating structured Markdown files directly within the `docs/` directory. This process captures progress, decisions, and learnings automatically, saving manual documentation time.

What is the best way to create an Architecture Decision Record after a coding session?▼

Creating an Architecture Decision Record (ADR) is best handled by triggering automated documentation generation using the ADR template. This automatically structures your technical decisions into a standardized Markdown file.

Can I use different templates for guides, research, and session logs in my project docs?▼

Yes, you can use customizable templates for guides, ADRs, research logs, and session logs. The documentation process supports template selection to ensure your Markdown files are structured correctly for each specific use case.

How does automatic file naming and directory organization work for project documentation?▼

Automatic file naming and directory organization works by placing generated Markdown files into the `docs/` directory based on the session content. This ensures your project documentation and knowledge capture records remain accessible.

Do I need any external dependencies to capture technical decisions into markdown files?▼

No external dependencies are required to capture technical decisions into Markdown files. The session documentation process operates independently to generate guides and ADRs without relying on external tools or libraries.