docs

Archive session decisions and repo changes into structured docs and AGENTS.md.

4.6k|378|Updated Jun 28, 2024
One-click install
npx skills add https://github.com/latitude-dev/latitude-llm --skill docs-latitude-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/latitude-dev/latitude-llm/tree/main/.agents/skills/docs
Command: npx skills add https://github.com/latitude-dev/latitude-llm --skill docs-latitude-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams keep repository knowledge durable by synchronizing decisions, rules, and conventions from ongoing conversations and git changes into structured docs and the AGENTS.md file.

Core Features & Use Cases

  • Durable knowledge capture: Convert session outcomes and repo changes into authoritative domain and governance docs.
  • Documentation governance: Propose and escalate repo-wide rules into AGENTS.md to codify conventions and prohibitions.
  • Change mapping: Align updated designs, architecture decisions, and workflow changes with the docs suite, ensuring future-state consistency.

Quick Start

Run a session scan to sync new durable knowledge into the docs directory and AGENTS.md.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I keep repository documentation in sync with code changes?

Documentation governance codifies repo-wide rules and conventions into AGENTS.md. It escalates decisions from ongoing sessions and git changes to establish authoritative prohibitions and standards.

How does knowledge management for architecture decisions work in a git repository?

Yes, you can sync workflow changes and product decisions to docs by running a session scan. It identifies durable knowledge and updates the docs directory and AGENTS.md automatically.

What is the best way to archive durable conventions from a development session?

This skill targets workflow sessions where durable decisions and invariants exist, applying to changes in product, architecture, or repo-wide standards to keep your documentation authoritative.

When should I update AGENTS.md for repository governance?

A limitation is that this skill only targets workflow sessions containing durable decisions, rules, or conventions; it does not archive transient or non-durable session knowledge.