skills.rest
tuanfung
tuanfungCOMMUNITY
Explore all skills by this author →
GitHub

documentation-and-adrs

Document architecture decisions and design choices using structured ADR templates.

Updated Jun 29, 2026
Search Tags:#documentation#software development#architecture decisions#code documentation#ADRs
One-click install
npx skills add https://github.com/tuanfung/pqt-agent-skills --skill documentation-and-adrs-tuanfung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-and-adrs
Source: https://github.com/tuanfung/pqt-agent-skills/tree/main/skills/documentation-and-adrs
Command: npx skills add https://github.com/tuanfung/pqt-agent-skills --skill documentation-and-adrs-tuanfung

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps streamline the process of documenting architecture decisions, decisions, and key information within a project, making it easier for both team members and future developers to understand the project.

Core Features & Use Cases

  • Centralized Decision Documentation: Store architectural decisions and design choices in a standardized format.
  • Architecture Decision Records (ADRs): Provide detailed explanations and context behind important architectural decisions.
  • inline Gotchas: Document known issues and common mistakes to avoid potential pitfalls.
  • API Documentation: Provide clear documentation for public APIs and interfaces.

Quick Start

Document an important architecture decision by creating an ADR and following the structured template.

Frequently Asked Questions about documentation-and-adrs

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

FAQPage Schema
What are Architecture Decision Records and how do they improve code documentation?▼

Architecture Decision Records (ADRs) document architectural decisions and design choices in a standardized format, enhancing code documentation by retaining project knowledge and explaining the context behind key decisions.

How do I document architecture decisions for team collaboration in a software project?▼

You can document architecture decisions by creating an ADR using a structured template. This framework centralizes design choices, inline gotchas, and API documentation to streamline team collaboration and knowledge retention within codebases.

What is the best way to document known issues and common mistakes in software development?▼

The best way to document known issues is to use inline gotchas within your documentation framework. This captures common mistakes alongside ADRs to help developers avoid potential pitfalls and understand architectural decisions.

Can I use this documentation framework for public API documentation?▼

Yes, this framework includes features for providing clear API documentation. It allows you to document public APIs and interfaces while centralizing architectural decisions and inline gotchas for comprehensive project understanding.

Does this ADR template require any specific dependencies to set up?▼

No specific dependencies are required to set up this ADR framework. It operates independently using included scripts and reference components to help you start documenting architecture decisions and design choices directly within your codebase.

Related Skills

Explore More Software Engineering Skills→
mayurpisemayurpise
39

init

Generate architecture diagrams and context files for brownfield codebases.

Community
Advanced
walekingwaleking

notion-md-sync

Batch upload local Markdown files to Notion via the Notion API.

Community
Intermediate
gatezhgatezh
2

sandbox-fetch-docs

Compare documented library APIs against actual implementations in node_modules.

Community
Intermediate
BuiDommBuiDomm

wiki

Manage persistent markdown-based project wikis with CRUD operations and keyword search.

Community
Advanced