omp-flow: Skill for Claude Code

OMP-Flow ADR

ADR here means Any Decision Record, as in MADR (Markdown Any Decision Records): the durable why behind how something is shaped. Records live in .omp-flow/wiki/decisions/. This Skill contains procedure only; decisions belong in the Wiki.

What deserves a record

Record a decision when its reasoning would be lost without it: a choice among real alternatives, an obvious approach that was rejected, a constraint, or a small design idea that a future agent would otherwise "simplify" back into a defect. Size does not matter; rediscovery cost does. Ask: if someone removed this tomorrow, would they know why it was there? A rejected idea also deserves a record, so it is not proposed again without new evidence.

Do not record restated code, Task progress, or an unconfirmed hypothesis.

Placement

.omp-flow/wiki/decisions/<context>--<question>--<YYYY-MM-DD>.md

<context> is the domain or bounded context and <question> is the stable problem the decision answers, both in kebab-case. The date comes last, so every record that has answered the same question sorts together. Do not number records; parallel branches would collide on the next number. Reuse an existing context and question name before inventing a new one.

Record

Write one decision per record. The four sections below are required, and each may be a single sentence. For a small decision, write in the spirit of a Y-Statement: in the context of , facing , we chose over to achieve , accepting .

---
type: "ADR"
title: "<question>: <choice>"
description: "<one sentence: under which constraint we chose what>"
tags: ["<context>", "<keyword>"]
status: "proposed"
date: "YYYY-MM-DD"
---

# <question>: <choice>

## Context and Problem Statement

## Considered Options

## Decision Outcome

Chosen option: "<option>", because <reason>.

## Confirmation

<The test, gate, or review that shows the decision still holds; write "none — relies on review"
when no mechanical check exists.>