documentation-and-adrs

Record architectural decisions in ADRs and decision logs.

Updated Aug 27, 2026

Search Tags:#changelog #documentation #adr #governance #traceability #architecture-decisions #decision-logs

Ready to run

npx skills add https://github.com/chenxingqiang/tdd-agent-skills --skill documentation-and-adrs-chenxingqiang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-and-adrs
Source: https://github.com/chenxingqiang/tdd-agent-skills/tree/main/skills/documentation-and-adrs
Command: npx skills add https://github.com/chenxingqiang/tdd-agent-skills --skill documentation-and-adrs-chenxingqiang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records the reasoning behind architectural and API changes so future engineers understand why decisions were made.

Core Features & Use Cases

Template-driven ADRs to capture context, constraints, and trade-offs.
Centralized decision log referencing .cursorrules, CLAUDE.md, and docs/decisions/changes.md.
Onboarding and governance support for teams and AI agents.

Quick Start

Create or update an ADR when you change a public API or key architecture decision, and place it under docs/decisions with a sequential ADR number.

Frequently Asked Questions about documentation-and-adrs

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

FAQPage Schema

How do I document architecture decisions to preserve rationale for future engineers?▼

Document architecture decisions using template-driven ADRs to capture context, constraints, and trade-offs. This preserves the reasoning behind architectural and API changes, ensuring future engineers understand why specific technical choices were made.

What is an ADR and when should I create one?▼

An ADR is an architectural decision record that captures context, constraints, and trade-offs. Create or update an ADR whenever you change a public API or key architecture decision to maintain traceability for future engineering teams and AI agents.

How do I manage a centralized decision log for API and architecture changes?▼

Manage a centralized decision log by referencing .cursorrules, CLAUDE.md, and docs/decisions/changes.md. Place ADRs under docs/decisions with a sequential ADR number to maintain auditable governance and traceability across project changes.

Does this approach support onboarding and governance for AI agents?▼

Yes, the centralized decision log provides onboarding and governance support for both engineering teams and AI agents. By recording artifacts in .cursorrules and CLAUDE.md, AI agents can access architectural rationale and decision history.

What's the best way to structure ADR files for auditability?▼

Structure ADR files under docs/decisions with a sequential ADR number. Use template-driven formats to capture context, constraints, and trade-offs, ensuring core decision artifacts are recorded for auditability and future reference.

Why do I need to record the reasoning behind architectural changes?▼

Recording architectural reasoning solves the problem of lost context over time. By capturing context, constraints, and trade-offs in ADRs, future engineers understand why decisions were made, preventing repeated debates and ensuring governance compliance.