worklog

Worklog tracking is automated by creating a single Markdown file per task in .worklogs, tied to your current feature branch. It enforces a standard frontmatter schema with date, branch, task, and status, appending structured progress entries that provide a portable audit trail picked up during squash merges.

The best way to maintain a portable audit trail is using a per-task Markdown worklog with standard frontmatter. This approach ties documentation to the feature branch, structuring progress entries in a single-page file that travels with the code and archives automatically upon squash-merge completion.

You create a worklog by running the /maymust:worklog command on your feature branch. This generates or opens a single-page Markdown file under .worklogs, scoped to your active branch, allowing you to immediately begin documenting tasks and adding structured progress entries.

Yes, worklog tracking is designed for branch-based workflows using squash merges. It ties a single-page audit trail to the current feature branch and automatically archives the worklog when the branch is squash-merged to main, ensuring progress logs are preserved for PR summaries.

Yes, you can enforce a standard frontmatter schema in Markdown files for task tracking. The schema includes date, branch, task, and status fields, appending progress logs in a structured format to maintain a concise and consistent audit trail across the team.

When a feature branch is squash-merged to main, the task tracking worklog is automatically archived team-wide. This ensures the single-page Markdown audit trail, including all progress entries and completion status, is preserved without manual intervention.