- name
- decision-recorder
- description
- 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.
Decision Recorder
Record decisions in a structured format so they can be searched, reviewed, and improved over time.
Core capabilities
- Detect decision-oriented text
- Create structured decision records
- Search and filter past decisions
- Review decision details
- Analyze decision patterns
- Update or delete stored decisions
Commands
Record a decision
decision-recorder record
decision-recorder rList decisions
decision-recorder list
decision-recorder lsSearch decisions
decision-recorder search <keyword>
decision-recorder s <keyword>Analyze patterns
decision-recorder analyze
decision-recorder aView a specific decision
decision-recorder view <id>
decision-recorder v <id>Update or delete a decision
decision-recorder update <id>
decision-recorder u <id>
decision-recorder delete <id>
decision-recorder d <id>Detect decision keywords
decision-recorder detect "We decided to use Node.js"
decision-recorder keywordsCommon filters
# Filter by tag
decision-recorder list --tag=important
# Filter by date range
decision-recorder list --from=2024-01-01 --to=2024-12-31Programmatic usage
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();Decision record format
{
"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"]
}Data location
Decision records are stored under:
~/.decision-recorder/Each decision is stored as a JSON file.
Recommended use cases
- Architecture and technology choices
- Product tradeoff decisions
- Team decisions after discussion
- Operational decisions and retrospectives
- Personal planning and career decisions
Good practice
- Record decisions soon after they are made.
- Capture reasoning, not just outcomes.
- Use tags consistently.
- Review decisions periodically.
- Compare similar decisions over time.
Notes
- Requires Node.js 14 or later.
- Uses local JSON files for storage.
- Works best when reasoning and context are written clearly.
License
MIT