finalize

Evaluate completed implementations, generate ADRs, propose Patterns entries, and write commit messages.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/joelabrahamsson/devenv --skill finalize-joelabrahamsson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/joelabrahamsson/devenv/tree/main/claude-config/skills/finalize
Command: npx skills add https://github.com/joelabrahamsson/devenv --skill finalize-joelabrahamsson

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps assess whether an implementation warrants an Architecture Decision Record (ADR), proposes Patterns entries, writes commit messages, and cleans up plan files.

Core Features & Use Cases

  • Assess ADR Warrantiness: Evaluate if an implementation's complexity, constraints, and impact warrant an ADR.
  • Generate ADRs: Create detailed ADRs based on the implementation's Motivation & Context.
  • Propose Patterns Entries: Suggest Patterns entries for new canonical exemplars in project documentation.
  • Commit and Push Changes: Automate the commit and push process with informative commit messages.

Quick Start

Run the finalize skill with the path to your plan file, e.g., finalize /path/to/plan.md

Frequently Asked Questions about finalize

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

FAQPage Schema
How do I document completed software implementations and generate an ADR?

You can generate an Architecture Decision Record by running the finalize skill with the path to your plan file. It evaluates the implementation's Motivation & Context, determines ADR warrantiness, and creates the ADR documentation automatically.

When does a software implementation warrant an Architecture Decision Record?

An implementation warrants an ADR based on its complexity, constraints, and impact. This skill analyzes your implementation plans, behavioral contracts, and revision notes to determine if the architectural decisions require formal documentation.

How do I write commit messages and clean up plan files after a project implementation?

To write commit messages and clean up plan files after an implementation, this skill analyzes your revision notes and behavioral contracts. It then generates informative commit messages and removes temporary plan files to finalize your project.

What is the best way to propose Patterns entries for canonical exemplars in project documentation?

The best way to propose Patterns entries for canonical exemplars is to evaluate completed implementations against your project documentation standards. This skill suggests new canonical exemplars by analyzing your implementation plans and behavioral contracts.

Can I use this skill to automate commits and pushes with informative commit messages?

Yes, you can automate commits and pushes with this skill. It generates informative commit messages based on your implementation analysis and behavioral contracts, then cleans up plan files to complete the project finalization workflow.

Do I need implementation plans and behavioral contracts to assess ADR warrantiness?

Yes, you need implementation plans and behavioral contracts to assess ADR warrantiness. This skill requires these documents, along with revision notes, to evaluate implementation complexity and determine if an Architecture Decision Record is justified.