RF(x) Section Writer

The problem

Writing proposal sections that miss mandatory requirements or exceed page limits leads to disqualification. Maintaining compliance across hundreds of statement-of-work (SOW) items is labor-intensive and prone to human error.

What it does

• Maps every assigned SOW requirement to specific narrative subsections and inline compliance tags.
• Calculates real-time page estimates based on word count, tables, and graphic placeholders to enforce strict budget compliance.
• Generates a section-specific compliance matrix verifying how every "shall" and "must" is addressed.
• Identifies missing proof points or data gaps without inventing fictional past performance or metrics.
• Maintains a direct, declarative enterprise writing style devoid of marketing fluff or blog-style framing.

Why this beats prompting it yourself

General-purpose prompts often ignore strict page constraints or lose track of specific SOW IDs in long documents. This skill implements a systematic inventory and tagging procedure that ensures 1:1 coverage between the solicitation and the response, preventing the "hallucinated compliance" common in raw LLM outputs.

Use cases

• Drafting technical approach sections mapped to specific PWS/SOW IDs.
• Creating "pink team" drafts with integrated requirement tagging for evaluator review.
• Developing compliance-heavy subsections where every claim requires an explicit reference tag.
• Generating gap analysis reports for proposal sections where buyer-supplied proof points are missing.

Known limitations

This skill handles single sections only and does not generate book-level matrices, past performance volumes, or executive summaries. It requires pre-defined SOW items and page budgets to function.