skills.rest
greenheadHQ
greenheadHQCOMMUNITY
Explore all skills by this author →
GitHub

documenting-intent

Record CIR/ADR decisions or retrieve past decision history from code.

4|Updated Dec 21, 2025
Search Tags:#templates#documentation#adr#record#cir#decision-history
One-click install
npx skills add https://github.com/greenheadHQ/nixos-config --skill documenting-intent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documenting-intent
Source: https://github.com/greenheadHQ/nixos-config/tree/main/modules/shared/programs/claude/files/skills/documenting-intent
Command: npx skills add https://github.com/greenheadHQ/nixos-config --skill documenting-intent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Record CIR/ADR or retrieve past decision history. This skill helps teams capture the reasoning behind choices, ensuring context is not lost over time.

Core Features & Use Cases

  • Inline CIR/ADR logging during development to capture decisions.
  • Retrieval of past CIRs/ADRs from code history and references.
  • Templates and philosophy references to standardize decision records.

Quick Start

Record a CIR/ADR for a recent decision using the inline change intent blocks and templates.

Frequently Asked Questions about documenting-intent

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

FAQPage Schema
How do I record an ADR or CIR to preserve decision context in my codebase?▼

To record an ADR or CIR, use inline change intent blocks within commit messages and PR narratives to capture the reasoning behind choices. This preserves decision context across code changes, reviews, and releases.

What is the best way to retrieve past decision history for code reviews?▼

Retrieve past decision history by accessing logged CIRs and ADRs stored within your code history and reference materials. This allows teams to retrieve the reasoning behind past choices during reviews.

How do I standardize architecture decision records across my development workflow?▼

Standardize architecture decision records by applying provided templates and philosophy references to inline CIR blocks. This ensures structured guidance and consistent decision logging across software releases.

When do I need to use a change intent record in my development workflow?▼

You need a change intent record when capturing decisions during development to ensure context is not lost over time. It applies to software development workflows to preserve context across changes and releases.

Can I use inline CIR blocks for commit messages and PR narratives?▼

Yes, you can use inline CIR blocks for commit messages and PR narratives. The system provides structured guidance and templates specifically for embedding decision records directly into these workflows.

Why does capturing decision context matter for software releases?▼

Capturing decision context matters because it ensures the reasoning behind choices is not lost over time. Preserving this context across changes and releases maintains clarity for future development and reviews.

Related Skills

Explore More Software Engineering Skills→
angelgarciasolorzanoangelgarciasolorzano

spatie-version-control

Enforce Spatie Git conventions for commit messages, branch naming, and merge strategies.

Community
Intermediate
vtgiang-dotcomvtgiang-dotcom
3

documentation-and-adrs

Record architectural decisions as ADRs under docs/decisions with lifecycle statuses.

Community
Intermediate
iamacoffeepotiamacoffeepot
1

review

Automate code review for Aether engine PR-bound changes.

Community
Intermediate
TeiNamTeiNam
12

architecture-decision-records

Record architectural decisions with context, alternatives, and consequences.

Community
Advanced