record

Record architectural decisions and implementation plans with ADR templates and index updates.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill record-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/record
Command: npx skills add https://github.com/kdlbs/kandev --skill record-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record architectural decisions and implementation plans to preserve rationale for future reference.

Core Features & Use Cases

  • Create ADRs to document architectural decisions, contexts, and consequences.
  • Save implementation plans with templates, standardized file naming, and traceable history.
  • Update central indexes (docs/decisions/INDEX.md and docs/plans/INDEX.md) to maintain a complete provenance trail.

Quick Start

Create an ADR document for the next design decision following the ADR template and place it under docs/decisions/NNNN-short-title.md, then update the index.

Frequently Asked Questions about record

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

FAQPage Schema
How do I document architectural decisions to preserve rationale for future reference?

Document architectural decisions using Architecture Decision Records (ADRs) to capture contexts, trade-offs, alternatives, and consequences. This ensures design choices and implementation details remain traceable over time.

What is the best way to create an implementation plan template with traceable history?

Create implementation plans using standardized templates and file-naming conventions. This approach maintains traceable history for software projects by structuring design choices and execution details consistently.

How do I maintain a complete provenance trail for design decisions and plans?

Update central indexes located at docs/decisions/INDEX.md and docs/plans/INDEX.md after creating new records. This index update workflow maintains a complete provenance trail across your project documentation.

When do I need ADRs and implementation plans in my software project?

You need ADRs and implementation plans in software projects of any size where design choices, trade-offs, and implementation details must be captured, reviewed, and traced over time.

What file naming convention should I use for architecture decision records?

Use the NNNN-short-title.md file naming convention for architecture decision records, placing them under the docs/decisions/ directory to ensure proper sorting and traceable history.

Can I use ADR templates for small software projects or are they only for large architectures?

ADR templates apply to software projects of any size. They are designed to capture design choices, trade-offs, and implementation details wherever these decisions must be reviewed and traced over time.