adr

What it does

/cl-dev:adr captures a significant architectural decision as an Architecture Decision Record (ADR): a short, durable note that says what was decided, the context around it, and why. It works through a brief interview with you to pin down the decision and the reasoning, then writes the record into your project's knowledge base so the choice, and the thinking behind it, stays discoverable long after the moment has passed.

Not every decision warrants a record. The skill first checks that a decision is actually worth capturing (one that is significant and hard to reverse) before writing anything. If it isn't, the skill will say so rather than adding noise.

When to use it

Reach for /cl-dev:adr when a genuinely consequential, hard-to-undo choice has been made and you want it on the record: a foundational technology, a data model, a boundary between systems, a security or compliance stance. Two moments are typical:

• On purpose, when you've just settled a weighty decision and want it documented before the context fades.
• In passing, when a decision lands while you're doing other work (during design or implementation) and you want to capture it without losing your place.

It sits alongside the main build workflow rather than inside it. /cl-dev:consolidate may surface decisions worth recording after a feature ships; /cl-dev:adr is how you turn one of those into a record.

How to invoke it

Run the command inside your coding agent, in the target repository:

/cl-dev:adr

You can start it bare and describe the decision when prompted, or lead with a one-line summary, for example, "we're standardizing on Postgres for all tenant data." Either way, the skill interviews you to fill in the context and consequences before writing the record.

One thing to have in place first: the repository is set up with CodeLantern and has a knowledge base to write into. If you haven't done that yet, run /cl-dev:init.