archive_work

You can archive completed work by generating structured markdown reports, plans, and conversation logs into a centralized repository. This enforces consistent save paths with timestamps and metadata for easy retrieval.

Generating a post-task work report involves capturing changes, tests, resolutions, and performance notes into a structured document. This ensures seamless handovers and audits by applying consistent metadata and timestamping.

Yes, you can store implementation plans and conversation logs together for knowledge transfer. You invoke the default work report and add the plan archive with a flag and the conversation log with another flag.

To add conversation logs to a work report archive, you invoke the archiving command and apply the conversation flag. This captures the logs alongside the default report into the designated docs directory.

Yes, the work report archiving process enforces timestamping and metadata capture. It applies consistent save paths and metadata to reports, plans, and conversation logs to simplify retrieval and compliance.

You need to archive implementation plans and logs for audits when completing tasks across projects. This centralized post-task reporting ensures consistent documentation, capturing changes, tests, and resolutions for compliance.