capture

Capture domain knowledge into structured Markdown files.

Updated Aug 23, 2026

Search Tags:#software engineering #documentation #knowledge management #domain modeling #knowledge capture

Ready to run

npx skills add https://github.com/lostsolution/makelele --skill capture-lostsolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/lostsolution/makelele/tree/main/skill-graph/skills/capture
Command: npx skills add https://github.com/lostsolution/makelele --skill capture-lostsolution

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill captures domain knowledge from engineers and stores it in a structured Markdown format, making complex information accessible and organized.

Core Features & Use Cases

Knowledge Capture: Gathers essential information about domains, including overview, architecture, constraints, and anti-patterns.
Structured Output: Generates organized .md files for easy reference and integration into documentation.
Use Case: A new engineer joins a project and needs to understand a specific microservice. They can use this Skill to ask targeted questions and generate a comprehensive overview of the service's domain.

Quick Start

Run /skill-graph:capture to begin capturing domain knowledge.

Frequently Asked Questions about capture

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

FAQPage Schema

How do I document domain knowledge for a software project into Markdown?▼

To document domain knowledge into Markdown, you need to interactively provide specific details about the domain. The tool then structures this information into organized `.md` files covering architecture, constraints, and anti-patterns for easy reference.

What is the best way to capture software architecture and constraints for new engineers?▼

Capturing software architecture and constraints for new engineers requires gathering targeted domain information through user interaction. This process generates a comprehensive Markdown overview of the service's domain, making complex project details accessible.

What specific information do I need to provide to capture domain knowledge effectively?▼

To capture domain knowledge effectively, you must provide specific details about the domain's overview, architecture, constraints, anti-patterns, and review checklists. This user interaction is required to structure the documentation accurately.

Can I generate structured documentation for a microservice without prior knowledge of the domain?▼

Generating structured documentation without prior domain knowledge is possible because the tool interactively asks for specific details. However, you must supply the architectural and constraint information to produce the structured Markdown output.

How does interactive knowledge management compare to static documentation for software domains?▼

Interactive knowledge management actively collects essential domain information on constraints and anti-patterns through user queries, whereas static documentation relies on manual entry. This approach generates organized Markdown files for easier integration and reference.