New Dev Decision

Generate lightweight developer decision records with context, rationale, and alternatives.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill new-dev-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: New Dev Decision
Source: https://github.com/beekeeper-lab/repomirrorkit/tree/main/.claude/skills/new-dev-decision
Command: npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill new-dev-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need to document small, implementation-level technical decisions that don't warrant a full Architecture Decision Record (ADR), preventing the loss of valuable context about "why" certain choices were made.

Core Features & Use Cases

  • Lightweight Decision Records: Captures implementation choices like library selection, algorithm approach, or data structure.
  • Searchable Log: Creates a cumulative, searchable log of developer decisions.
  • Use Case: When deciding to use dataclasses instead of TypedDict for DTOs, you can quickly create a decision record detailing the context, the chosen approach, and alternatives considered.

Quick Start

Create a new developer decision record with the title "Use dataclasses instead of TypedDict for DTOs", the context "We need a clear and concise way to represent data transfer objects that supports type hinting and immutability.", and the chosen decision "Chosen dataclasses for their built-in support for immutability and cleaner syntax compared to TypedDict.".

Frequently Asked Questions about New Dev Decision

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

FAQPage Schema
How do I record implementation choices for small technical decisions?

A developer decision record captures implementation-level technical choices that don't warrant a full Architecture Decision Record. It documents context, chosen decisions, and alternatives, preventing the loss of valuable rationale behind small coding choices.

What's the best way to document why I chose one library over another?

Create a developer decision record by providing a title, context, and chosen decision. You can optionally include alternatives considered, work IDs, and tags to categorize the entry within your searchable technical decision log.

Does this approach work for tracking implementation choices instead of full architecture decisions?

Yes, this method suits implementation-level choices like library selection or algorithm approaches. It requires a title, context, and chosen decision to generate a record, making it ideal for tracking smaller technical choices without full ADR overhead.

Can I search past technical decisions to find rationale for previous implementation choices?

Yes, the skill creates a cumulative, searchable log of developer decisions. You can query this log to retrieve the context, rationale, and alternatives considered for past implementation choices made during software development.

When should I not use a lightweight developer decision record?

Avoid using lightweight developer decision records for major architectural changes requiring comprehensive stakeholder review. This method is designed for small implementation-level choices like data structure selection, not for replacing formal Architecture Decision Records.