What problem does it solve? Regenerating an entire long document for every small correction wastes tokens and loses the audit trail of what changed. This Skill batches localized edits into a structured backlog so large documents evolve through discrete, traceable update entries rather than full rewrites. ## Core Features & Use Cases - Structured Update Entries: Records each change as a UPD-XXX entry with timestamp, type (correction, bounded replacement, or additive insertion), target line range, context, and dependencies. - Activation Guardrails: Applies only when a document is 100+ lines and the change affects under 30% of content, and defers to full regeneration for structural or tonal rewrites. - Sync Threshold Warnings: Flags the user at 5 unresolved entries and escalates at 8, recommending a vFinal integration pass without ever blocking new entries. - Use Case: While iterating on a 300-line product requirements document, you say "add to backlog: fix the pricing tier in section 4" several times across a session, then say "apply backlog" to generate a single vFinal integration prompt applying all pending updates. ## Quick Start Say "start a backlog for my requirements document" and then report each small change with "add to backlog" as you review the draft.
