documentation-and-adrs

Name: documentation-and-adrs
Availability: InStock
Author: tradertunante

Record architectural decisions and documentation within the repository.

Updated Feb 9, 2026

Search Tags:#architecture #documentation #adr #engineering #guidelines #decision-records

Ready to run

npx skills add https://github.com/tradertunante/servicecontrol --skill documentation-and-adrs-tradertunante

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation and ADRs capture the context, constraints, and trade-offs behind major decisions to help future engineers understand the codebase and rationale.

Core Features & Use Cases

ADR creation and lifecycle tracking to record decisions for architecture, APIs, and major feature changes.
Inline documentation guidelines that explain why a design was chosen and what alternatives were considered.
Quick transfer of knowledge for onboarding, audits, and knowledge silos prevention.

Quick Start

Create an ADR to capture the rationale for a major architectural decision and its trade-offs.

Frequently Asked Questions about documentation-and-adrs

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

FAQPage Schema

When do I need to create an Architecture Decision Record?▼

Create an ADR when making major decisions regarding architecture, APIs, or feature changes. It records context, constraints, and trade-offs to preserve rationale for future engineers and onboarding.

How do I document architectural trade-offs and alternatives in my repository?▼

Document architectural trade-offs using ADR templates and inline documentation guidelines. Store these records under docs/decisions/ to explain why a design was chosen and what alternatives were considered.

What is the best way to track the lifecycle of an API decision record?▼

Track the lifecycle of an API decision record using ADR lifecycle management features. This records the decision context and status within the repository to prevent knowledge silos during audits.

Can I use inline documentation guidelines for major feature changes?▼

Yes, inline documentation guidelines explain why a design was chosen for major feature changes. They support ADR templates to ensure context and constraints are preserved for future engineers.

Why does my engineering team struggle with knowledge silos during onboarding?▼

Knowledge silos occur when architectural context is lost. Creating Architecture Decision Records captures trade-offs and constraints, enabling quick knowledge transfer and preventing onboarding bottlenecks.