skills.rest
I2olanD
I2olanDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

knowledge-capture

Document and organize development knowledge into templated documentation artifacts.

Updated Dec 28, 2025
Search Tags:#templates#documentation#interfaces#patterns#deduplication#domain#knowledge-capture
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill knowledge-capture-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-capture
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/knowledge-capture
Command: npx skills add https://github.com/I2olanD/dotfiles --skill knowledge-capture-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how teams capture and reuse knowledge discovered during development, reducing duplication and ensuring consistent documentation practices.

Core Features & Use Cases

  • Documentation structure and guidance: Defines docs/ domains, patterns, and interfaces to organize knowledge.
  • Deduplication workflow: Guides search and updates vs creation to avoid documentation fragmentation.
  • Cross-reference and lifecycle management: Provides templates and versioning guidelines for documentation across teams.

Quick Start

Review existing documentation using the deduplication workflow, then create or update domain, patterns, and interfaces docs following the templates in templates/. Document new knowledge in docs/ with proper category and cross-references.

Frequently Asked Questions about knowledge-capture

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

FAQPage Schema
How do I capture development knowledge into reusable documentation?▼

To capture development knowledge, document business rules, technical patterns, and external interfaces into structured artifacts using predefined templates, ensuring consistent organization across domains and projects.

What is the best way to prevent documentation duplication across projects?▼

Prevent documentation duplication by applying a deduplication workflow that guides you to search and update existing artifacts before creating new ones, reducing fragmentation across teams.

How do I organize technical patterns and external interfaces for cross-team reuse?▼

Organize technical patterns and external interfaces by categorizing new knowledge into specific domains and applying cross-referencing and lifecycle guidelines within a structured docs directory.

Does this knowledge-capture approach enforce a specific documentation structure?▼

Yes, this approach enforces a templated structure for documenting business rules and patterns, providing versioning guidelines to maintain consistency across different teams and projects.

When do I need to update existing domain documentation instead of creating new files?▼

You need to update existing domain documentation when a search reveals related artifacts, triggering the deduplication workflow to modify and cross-reference rather than create new files.

Can I manage documentation lifecycles across multiple domains using templates?▼

Yes, you can manage documentation lifecycles across multiple domains using provided templates and versioning guidelines that enforce cross-referencing and consistent updates.

Related Skills

Explore More Content & Communication Skills→
studyplusstudyplus
10

miko.new_cap

Generate business rules and high-level design documents from capability descriptions.

Official
Advanced
ondrej-svecondrej-svec
18

share-html

Publish local HTML files or static site directories to a share server.

Community
Intermediate
PriNovaPriNova
80

arch-code-review

Validate architectural diffs against canonical YAML artifacts for consistency and governance.

Community
Advanced
granietgraniet
247

llm-wiki

Create and maintain interlinked markdown knowledge bases with linting and Obsidian integration.

Community
Advanced