adr-log

スター0

フォーク0

更新日2026年7月17日 23:11

Record significant architecture or execution decisions so their reasoning survives the session. Trigger on requests like record this decision, write an ADR, capture the trade-off, or supersede the old decision.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

kiku-jw

kiku-jw/codex-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

ADR Log

Metadata

Trigger when: the task is to capture one real stack, schema, workflow, boundary, or vendor decision with durable rationale.
Do not use when: the choice is a tiny implementation detail or the decision is still too fuzzy to commit.

Skill Purpose

Capture one expensive-to-rediscover decision so the chosen path, rejected alternatives, and revisit conditions survive beyond the current chat session.

Instructions

Gate the decision first. Confirm what was chosen, what was rejected, and why this is worth preserving. If the choice is still fuzzy, route to $product-council or $spec-bundle instead. Read /Users/nick/.codex/skills/adr-log/references/storage-rules.md only when you need the storage surface and /Users/nick/.codex/skills/adr-log/references/entry-template.md only when you need the exact entry shape.
Record one entry in the right durable place: repo ADR file when the decision belongs to code, GitHub issue summary when issue state is canonical, or both when the project already uses $issue-control-loop.
Validate the record. Make sure it names context, options, chosen path, trade-offs, consequences, revisit conditions, and whether this entry supersedes an older decision.

Non-Negotiable Acceptance Criteria

One entry covers one real decision.
Rejected alternatives and trade-offs are explicit; they are not optional filler.
If the rationale was reconstructed after the fact, label it as reconstructed instead of pretending it was captured live.
Superseded decisions are marked as superseded, not silently overwritten.

Output

The written ADR or issue summary saved to its durable destination.
A short summary of the chosen path, the main trade-off, and the revisit trigger.
The destination path or issue location so the decision can be reopened later.

このリポジトリの他の Skills

同じリポジトリ

github-seo

kiku-jw/codex-skills

Audit and improve a public GitHub repository's discoverability and any linked canonical site without confusing repository presentation with website SEO. Use for repository SEO, GitHub discoverability, topics/homepage/README optimization, GitHub Pages SEO, AEO, or agent-friendly public documentation.

2026-07-230

spreadsheet

kiku-jw/codex-skills

Create, edit, analyze, or format spreadsheets (`.xlsx`, `.csv`, `.tsv`) with `openpyxl` and `pandas`, especially when formulas, references, and formatting must survive the change. Use when spreadsheet integrity matters more than ad hoc CSV hacking.

2026-07-180

spreadsheet-tabular-analysis

kiku-jw/codex-skills

Analyze and reshape spreadsheet, CSV, or TSV data with `pandas` and stable output files. Use when the job is aggregation, filtering, joins, metrics, or tabular transformations rather than workbook-style editing.

2026-07-180

spreadsheet-xlsx-edit

kiku-jw/codex-skills

Create or edit `.xlsx` workbooks while preserving formulas, references, formatting, and layout. Use when workbook integrity matters more than raw data analysis.

2026-07-180

transcribe-basic

kiku-jw/codex-skills

Produce a fast plain-text transcript with the bundled CLI using the light transcription model. Use when speaker diarization is not needed.

2026-07-180

transcribe-diarize

kiku-jw/codex-skills

Produce a speaker-aware transcript with diarization and optional known-speaker hints using the bundled CLI. Use when the user explicitly needs speaker labels.

2026-07-180

ADR Log

Metadata

Trigger when: the task is to capture one real stack, schema, workflow, boundary, or vendor decision with durable rationale.

Do not use when: the choice is a tiny implementation detail or the decision is still too fuzzy to commit.

Skill Purpose

Capture one expensive-to-rediscover decision so the chosen path, rejected alternatives, and revisit conditions survive beyond the current chat session.

Instructions

Gate the decision first. Confirm what was chosen, what was rejected, and why this is worth preserving. If the choice is still fuzzy, route to $product-council or $spec-bundle instead. Read /Users/nick/.codex/skills/adr-log/references/storage-rules.md only when you need the storage surface and /Users/nick/.codex/skills/adr-log/references/entry-template.md only when you need the exact entry shape.

Record one entry in the right durable place: repo ADR file when the decision belongs to code, GitHub issue summary when issue state is canonical, or both when the project already uses $issue-control-loop.

Validate the record. Make sure it names context, options, chosen path, trade-offs, consequences, revisit conditions, and whether this entry supersedes an older decision.

Non-Negotiable Acceptance Criteria

One entry covers one real decision.

Rejected alternatives and trade-offs are explicit; they are not optional filler.

If the rationale was reconstructed after the fact, label it as reconstructed instead of pretending it was captured live.

Superseded decisions are marked as superseded, not silently overwritten.

Output

The written ADR or issue summary saved to its durable destination.

A short summary of the chosen path, the main trade-off, and the revisit trigger.

The destination path or issue location so the decision can be reopened later.

name	adr-log
description	Record significant architecture or execution decisions so their reasoning survives the session. Trigger on requests like record this decision, write an ADR, capture the trade-off, or supersede the old decision.