document

Capture software work knowledge and rationale into structured Markdown documents.

5|Updated Apr 9, 2026

Search Tags:#architecture #debugging #documentation #knowledge-management #document

Ready to run

npx skills add https://github.com/KodingDev/meridian --skill document-kodingdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/KodingDev/meridian/tree/main/skills/document
Command: npx skills add https://github.com/KodingDev/meridian --skill document-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture knowledge and rationale from software work to prevent loss between sessions, ensuring teams preserve what was learned.

Core Features & Use Cases

Document after completing features with non-obvious behavior, after debugging sessions, or when hard-won insights exist.
Capture gotchas, root causes, fixes, and sources, and preserve architecture decisions for future maintainers.
Use as a living knowledge base to guide future work and onboarding.

Quick Start

Use the document skill to capture the key learnings from your latest debugging session into a structured knowledge note.

Frequently Asked Questions about document

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

FAQPage Schema

How do I document architecture decisions and gotchas after a debugging session?▼

To document architecture decisions and gotchas after a debugging session, capture the root causes, fixes, and sources in a structured Markdown note with clear frontmatter, preserving hard-won engineering insights for future maintainers.

What is the best way to capture hard-won engineering knowledge before losing it across sessions?▼

Capturing hard-won engineering knowledge across sessions requires recording non-obvious software behavior and rationale in a living knowledge base, using structured Markdown to ensure teams preserve what was learned during feature handoffs.

Can I use Markdown with frontmatter to manage my software knowledge base?▼

Yes, you can use Markdown with frontmatter to manage your software knowledge base, as the format requires clear frontmatter with a name and description, and loads a Markdown body containing structured guidance for your notes.

When should I document non-obvious software behavior and complex engineering challenges?▼

You should document non-obvious software behavior and complex engineering challenges immediately after completing features or debugging sessions, ensuring that hard-won insights and rationale are captured before context is lost between work sessions.

Does this knowledge-management approach support optional scripts and references for onboarding?▼

Yes, this knowledge-management approach supports optional scripts, references, and assets for onboarding, allowing you to load on-demand information alongside the structured Markdown body to guide future work and new team members.