skills.rest
venikman
venikmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

design/record-drr

Create ADR-style Design-Rationale Records with sequential prefixes in Markdown.

Updated Jan 11, 2026
Search Tags:#design#architecture#documentation#audit#ADR#DRR
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill design-record-drr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design/record-drr
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/design/record-drr
Command: npx skills add https://github.com/venikman/fpf-foundry --skill design-record-drr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill records the reasoning behind architectural decisions by generating a formal Design-Rationale Record (DRR) to replace scattered notes with a consistent, auditable artifact.

Core Features & Use Cases

  • ADR-style DRR generation: Create a structured document that captures context, decision, and consequences.
  • Audit and governance: Provides a traceable history for design choices and trade-offs.
  • Use Case: When evaluating a major design change, record the rationale to support future reviews and compliance.

Quick Start

Use the design/record-drr skill to create a new DRR by providing a title, context, and decision. The system will write a new Markdown file under design/decisions/ with a numeric prefix and a kebab-case filename.

Frequently Asked Questions about design/record-drr

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

FAQPage Schema
How do I document architectural decisions for an audit?▼

You can document architectural decisions by generating a Design-Rationale Record (DRR) that captures context, decisions, and consequences to provide a traceable governance history.

What is the best way to record design rationale for a major change?▼

The best way to record design rationale is by creating an ADR-style DRR file to replace scattered notes with a consistent, auditable artifact for future reviews.

How are DRR files structured and named in the project directory?▼

DRR files are written as Markdown to the design/decisions/ directory using a sequential three-digit prefix and a kebab-case title based on the provided input.

Do I need any special dependencies to create a Design-Rationale Record?▼

No dependencies are required to create a Design-Rationale Record, as the skill operates independently to generate the Markdown file and optionally log telemetry.

When should I use a DRR instead of keeping standard design notes?▼

Use a DRR instead of standard notes when you need formal auditability and structured governance, replacing scattered documentation with consistent architectural context and consequences.

Related Skills

Explore More Design & Creative Skills→
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

architecture-decision-recorder

Capture architectural decisions and rationale in standardized ADR documents.

Official
Basic
KristopherlbKristopherlb

agent-decision-records

Standardize agent decision records with identifiers, governance metadata, and evidence references.

Community
Intermediate
mahg-esmahg-es
3

iar-generate

Map DRR findings to affected project artifacts and estimate effort and risk.

Official
Intermediate
im9im9
1

adr

Generate ADR documents with context, alternatives, and trade-offs.

Community
Intermediate