manuscript-manager

You maintain project consistency by using a persistent YAML state file that logs chapter statuses, scores, and decisions. This approach prevents context loss by applying check-in and check-out protocols during multi-session book generation.

Managing state handoffs requires logging decisions with justifications and tracking pending tasks with aging alerts. This ensures cross-skill handoffs remain traceable and coherent throughout the multi-agent pipeline without losing context.

You recover lost context by reconstructing recent activity from the YAML state file. It rebuilds your working environment by reviewing the last session history, pending handoffs, and recent logged decisions to resume drafting.

Yes, multi-session book generation requires check-in and check-out protocols to track evaluation scores and word counts. This deterministic workflow validates consistency and updates the project state file at the end of each run.

You should avoid using a persistent YAML state file for single-session projects that do not require cross-skill handoffs. This approach is specifically built for long-form drafting where work spans many sessions and multiple agent roles.