documentation-and-adrs

Document architectural decisions and ADRs to preserve rationale and context.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pyoclaw/agent-skills --skill documentation-and-adrs-pyoclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-and-adrs
Source: https://github.com/pyoclaw/agent-skills/tree/main/skills/documentation-and-adrs
Command: npx skills add https://github.com/pyoclaw/agent-skills --skill documentation-and-adrs-pyoclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records decisions and documentation to ensure future engineers understand why certain architectural choices were made, what alternatives were considered, and how public APIs and features should be used going forward.

Core Features & Use Cases

  • Architecture Decision Records (ADRs) guide developers to capture rationale, constraints, and trade-offs for significant technical decisions.
  • Inline documentation practice and decision-record templates to keep a single source of truth for project context.
  • Structured documentation practices for quick onboarding, API changes, and feature rollouts across teams.

Quick Start

Review the ADRs and decision records before making architectural changes.

Frequently Asked Questions about documentation-and-adrs

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.

How do I document architectural decisions for a new feature rollout?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.

Does this approach work for recording API changes and design trade-offs across teams?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.

What is the best way to preserve codebase context for future engineers?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.

Can I use ADRs to speed up developer onboarding for my project?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.

When should I not use Architecture Decision Records?

To document architectural decisions, use ADR templates to capture rationale, constraints, and trade-offs. Enforce inline documentation practices and structured readme formats to maintain a single source of truth for project context across teams.