Page Budget Editor

The problem

Proposals and SOWs often exceed strict page limits, forcing developers and proposal leads to manually prune text. The risk of accidentally deleting a mandatory requirement ("shall") or failing to account for graphic real estate leads to non-compliant submissions.

What it does

• Calculates precise page counts using word density, table row counts, and graphic placeholders.
• Inventories every document block to map narrative evidence to specific SOW/PWS identifiers.
• Ranks potential cuts by priority, targeting redundant intros and culture padding first.
• Relocates overflow narrative to appendices with cross-reference pointers to maintain compliance.
• Generates a dropped-vs-kept log to audit every change against the original draft.

Why this beats prompting it yourself

Generic LLM prompts often "hallucinate" page counts or drop technical requirements to hit a length target. This skill enforces a rigid inventory-first procedure that treats mandatory requirements as immutable, ensuring the cut draft remains 100% compliant with the solicitation.

Use cases

• Reducing a three-page technical section to a two-page limit without losing mandatory claims.
• Moving non-essential worked examples to an appendix to make room for required figures.
• Auditing a draft to identify "padding" like slogans or restated win themes that consume budget.
• Ensuring all SOW identifiers are mapped to narrative blocks before and after document compression.

Known limitations

This skill requires an already coherent draft. It will not fix disjointed structure, write new content, or adjust document margins and font sizes to bypass limits.