devlog

Track monorepo architecture changes by writing plain-language devlog entries that capture what changed, why, and affected packages, maintaining a human-readable history of meaningful changes for your team.

To create a devlog entry, provide what changed, why it changed, affected packages, implications for downstream work, and whether a detailed report is needed. This generates the entry, updates the index, and optionally creates an architecture report.

Generate a detailed report in the reports directory when architectural or contract changes occur. Set the report_needed flag when providing your entry details to document significant structural modifications beyond routine updates.

Plain-language change tracking works for monorepos by capturing implications for downstream work in each entry. It updates a central index and generates detailed reports, helping teams understand the impact of architectural changes across packages.

The best way to maintain a human-readable change history is to log each meaningful change as a separate entry with reasons and implications, then update a central index file to ensure the development history remains accessible and organized.

Organize devlog entries by saving individual records in an entries directory and automatically updating a central index file. This structure ensures all meaningful changes are tracked chronologically and remain easy to navigate.