A lightweight decision-journal tool for PM, product, strategy, and operator workflows.
Early working CLI.
This repository supports creating Markdown decision entries, recording a review outcome, and listing entries whose review date is due. It does not yet provide calibration analytics, expected-versus-actual scoring, or advanced review workflows.
Decision journals help teams and individuals improve decision quality by recording what was decided, why it was decided, how confident the decision-maker was, and when the outcome should be reviewed.
This repository provides a small local workflow for:
- capturing decisions consistently
- recording confidence at the time of decision
- assigning a review date
- maintaining a queue of open decisions due for review
- recording outcomes and lessons after review
- creates Markdown-based decision entries
- stores confidence and review date in each entry
- provides a
duecommand for open entries ready for review - provides a
reviewcommand for recording one outcome and lesson set - stores real entries outside the repository by default
- uses a reusable journal template
python -m pip install -e .
decision-journal new "Delay launch by two weeks" --confidence 0.72 --review-date 2026-05-15
decision-journal due
decision-journal review "Delay launch by two weeks" \
--outcome "The fictional launch delay reduced avoidable rework." \
--lessons "Use the same review trigger for similar decisions."decision-journal due excludes entries that already contain a recorded review. Use --include-reviewed only when you want to inspect past-due history as well as the open queue.
templates/decision-entry.md reusable entry template
entries/examples/ fictional examples safe to publish
src/ lightweight CLI logic
skills/decision-journaling reusable decision-journaling skill
agents/decision-journaler agent instructions for decision capture and review
Decision journals can contain sensitive business, career, financial, health, relationship, or personal information. If this repository is public or shared, do not commit real decision entries.
Recommended pattern:
- keep real entries outside the repository
- use
entries/examples/only for fictional examples - avoid naming real employers, customers, partners, vendors, colleagues, or confidential projects
- remove private reasoning, negotiation details, and internal risk assessments before sharing
This early CLI does not yet provide:
- calibration scoring over time
- expected-versus-actual variance analysis
- forecasting metrics dashboards
- automated review summaries
- statistical quality measurement for decision quality
- multiple reviews or outcome-history edits for one entry
To support stronger decision-quality analysis, this repository should add:
- structured comparison between expected and actual results
- simple calibration summaries over time
- tests for entry parsing and richer review workflows
- public-safe fictional examples showing the full lifecycle from decision to review
- an explicit edit or follow-up model for reviewed decisions
This repository is shared in a personal capacity. It is not legal, financial, medical, employment, or psychological advice. It is not a substitute for professional judgment, qualified review, or formal organizational decision processes.
AI-generated decision summaries should be treated as drafts. Validate facts, assumptions, risks, constraints, and outcomes before using them for important decisions.
Maintained by Sima Bagheri.