Record, review, search, and analyze decisions from technical work, product work, team discussions, and personal planning. Use when the user wants to capture why a decision was made, compare options, store rationale, track outcomes, or revisit past decisions by keyword, date, or tag.
Record decisions in a structured format so they can be searched, reviewed, and improved over time.
decision-recorder record
decision-recorder r
decision-recorder list
decision-recorder ls
decision-recorder search <keyword>
decision-recorder s <keyword>
decision-recorder analyze
decision-recorder a
decision-recorder view <id>
decision-recorder v <id>
decision-recorder update <id>
decision-recorder u <id>
decision-recorder delete <id>
decision-recorder d <id>
decision-recorder detect "We decided to use Node.js"
decision-recorder keywords
# Filter by tag
decision-recorder list --tag=important
# Filter by date range
decision-recorder list --from=2024-01-01 --to=2024-12-31
const dr = require('decision-recorder');
const record = dr.createDecision({
question: 'Which backend stack should we use?',
options: ['Node.js', 'Python', 'Go'],
reasoning: 'Node.js has the best fit for fast iteration and ecosystem support.',
result: 'Node.js',
context: 'New product launch',
tags: ['architecture', 'backend']
});
const matches = dr.searchDecisions('architecture');
const analysis = dr.analyzeDecisions();
{
"id": "unique-id",
"timestamp": "ISO-8601 timestamp",
"question": "Decision question",
"options": ["Option A", "Option B"],
"reasoning": "Why this choice was made",
"result": "Final choice",
"context": "Background",
"tags": ["tag-a", "tag-b"]
}
Decision records are stored under:
~/.decision-recorder/
Each decision is stored as a JSON file.
MIT