Build premier landscape PDF proposals for Metis Strategy business development. Use whenever the user asks to create, build, draft, rebuild, refine, or iterate on a proposal, BD follow-up document, pitch document, or client-facing document to be sent to an external prospect after a discovery call. Output is a 16:9 landscape PDF (13.33" x 7.5") combining full-bleed photography, branded graphic devices, and coordinate-based ReportLab layout. Do NOT use for PowerPoint decks (use metis-pptx), whitepapers (use metis-whitepaper), one-pagers or internal reports (use metis-pdf-creator), or SOWs/MSAs (use metis-legal-drafting).
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Mechanical QA (overlap checks, content rules, render) tells you whether the document is structurally sound. The polish pass tells you whether it lands. Both are required before shipping.
Do the polish pass after verify.py --mode all has passed. Three reads, in order. Do not shortcut.
Read the full deck once, cold, start to finish. Do not stop to fix anything. Ask:
If Pass 1 fails, stop. Fix the structure before cleaning up copy.
Read each page slowly. For every sentence:
content-rules.md for the full list.intent: field — the page's "so what?" Re-read the rendered copy against the intent. Does the copy actually do what the intent claims? If not, rewrite the copy or rewrite the intent.Pass 2 is about density. Dense writing reads fast and earns trust. Loose writing reads slow and signals a draft.
Read the page titles only, in sequence. Skip the body copy. Ask:
Run python scripts/verify.py --print-titles <pdf> to extract the title list automatically.
If Pass 3 fails, the problem is structure, not copy. Fix the sketch, not the prose.
The polish pass is where a serviceable deck becomes a persuasive one. It is also where most consultants stop early. Do not stop early.