documentation-and-adrs

Create and manage Architecture Decision Records and software documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of creating and managing Decision Records (ADRs) and documentation, streamlining the communication of significant technical decisions and improving codebase understanding.

Core Features & Use Cases

  • ADRs Creation: Facilitates the creation of ADRs for significant technical decisions.
  • Documentation Management: Provides a structured way to document architectural decisions and rationale.
  • Use Case: Ideal for onboarding new team members, ensuring consistent architectural standards, and capturing the 'why' behind design choices.

Quick Start

Use the documentation-and-adrs skill to create an ADR for your recent database schema redesign.

Frequently Asked Questions about documentation-and-adrs

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

FAQPage Schema
How do I create Architecture Decision Records for a new software design?

You can automate the creation of Architecture Decision Records to capture the rationale behind significant technical decisions. This ensures architectural standards remain consistent and improves overall codebase understanding for the team.

What is the best way to document architectural decisions for onboarding new developers?

Automating technical documentation through Architecture Decision Records captures the why behind software design choices, providing a structured way to communicate significant technical decisions and facilitating smoother onboarding for new developers.

When do I need to use an Architecture Decision Record in my codebase?

An Architecture Decision Record is needed when a significant technical decision impacts software design and team communication. Documenting these decisions maintains consistent architectural standards and clarifies the rationale behind codebase changes.

Can I use this to manage technical documentation for a database schema redesign?

Yes, you can automate the creation of an Architecture Decision Record specifically for a database schema redesign. This documents the architectural decisions and rationale, streamlining the communication of technical changes to the team.

Does this approach help with codebase understanding if I have existing undocumented design choices?

Automating Architecture Decision Records for existing design choices captures the rationale behind past software design decisions, directly improving codebase understanding. This structured technical documentation enhances team communication regarding historical architecture.