decision-trace

Record append-only decision logs for code changes in DECISIONS.jsonl.

20|3|Updated Apr 30, 2026

Search Tags:#decisions #evidence #traceability #code-review #audit-trail #decision-log #record

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill decision-trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-trace
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/decision-trace
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill decision-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records append-only decision logs for code changes to speed reviews and improve auditability by preserving the rationale, evidence, and assumptions behind each decision.

Core Features & Use Cases

Automatic decision recording via the decision-trace tool for edits, refactors, and API changes.
Rich entries including rationale, evidence, assumptions, alternatives considered, and risk/confidence levels to guide reviews and governance.
Query and inspect the DECISIONS.jsonl ledger to track decision history, superseded decisions, and accountability across the codebase.

Quick Start

Record a decision entry for a code change using the decision-trace tool.

Frequently Asked Questions about decision-trace

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

FAQPage Schema

How do I maintain an audit trail for code changes to speed up code reviews?▼

You can maintain an audit trail for code changes by recording append-only decision logs that capture rationale, evidence, and assumptions. This structured traceability speeds up reviews by providing reviewers with the full context behind edits and refactors.

What is the best way to track rationale and risk levels for refactoring decisions?▼

The best way to track rationale and risk levels for refactoring decisions is to log structured entries with fields for rationale, alternatives considered, risk level, and confidence level. This creates a persistent decision history that guides review and governance.

How do I record an append-only decision log for API changes?▼

You record an append-only decision log for API changes by applying the decision-trace tool to generate structured entries. These entries are stored in a DECISIONS.jsonl ledger, preserving the accountability and evidence for each API modification.

Can I track superseded decisions and alternatives considered across my codebase?▼

Yes, you can track superseded decisions and alternatives considered by querying the DECISIONS.jsonl ledger. Entries include an optional superseded_by field and an alternatives_considered field to maintain accountability and decision history across the codebase.

Does decision logging work for tracking assumptions and evidence during software development?▼

Decision logging works for tracking assumptions and evidence by requiring structured entries that explicitly record assumptions, evidence, and confidence levels. This ensures that every code edit or API change has a verifiable audit trail for future review.