rfp-reverse-engineer

Reverse-engineer RFP documents to reconstruct the contracting officer's decision tree.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/BdM-15/capture-insights --skill rfp-reverse-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfp-reverse-engineer
Source: https://github.com/BdM-15/capture-insights/tree/main/skills/rfp-reverse-engineer
Command: npx skills add https://github.com/BdM-15/capture-insights --skill rfp-reverse-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, pandas, json, yaml, markdown, re, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill deciphers the intent behind federal RFPs by reconstructing the CO's hidden decision tree, revealing hot buttons, ghost language, and other critical insights.

Core Features & Use Cases

  • Reverse-Engineer RFPs: Reconstructs the contracting officer's hidden decision tree from the RFP text.
  • Identify Hot Buttons: Surfaces hidden preferences and discriminator opportunities.
  • Detect Ghost Language: Identifies ambiguous or unmeasurable requirements.
  • Missing Section Signals: Flags missing sections that could indicate potential issues.
  • Use Case: When a user has an RFP and wants to understand the CO's thinking, reverse-engineer the RFP to identify key areas to focus on in their proposal.

Quick Start

Use the rfp-reverse-engineer skill to reverse-engineer the attached RFP 'rfp_example.pdf'.

Frequently Asked Questions about rfp-reverse-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse-engineer an RFP to find hidden evaluation factors?

To reverse-engineer an RFP, you parse the document text to reconstruct the contracting officer's decision tree, surfacing hidden evaluation factors, ghost language, and missing section signals. This reveals the true intent behind the requirements.

What are ghost language and hot buttons in federal RFPs?

Ghost language refers to ambiguous or unmeasurable requirements in an RFP, while hot buttons are hidden preferences and discriminator opportunities. Identifying both helps reconstruct the CO's hidden decision tree to understand true evaluation priorities.

How do I extract a decision tree from an RFP document using Python?

You can extract a decision tree by processing the RFP text and cross-referencing it with a knowledge graph of requirements and deliverables. This process maps evaluation factors to reconstruct the hidden decision logic automatically.

Do I need a knowledge graph to analyze RFP evaluation factors?

Yes, reconstructing the decision tree and surfacing hidden preferences requires access to the RFP document alongside a knowledge graph of requirements, deliverables, and evaluation factors to accurately map the contracting officer's intent.

How do I detect missing section signals in an RFP?

Detecting missing section signals involves scanning the RFP structure to flag omitted sections that could indicate potential issues or hidden constraints. This analysis highlights critical gaps in the document that require further attention.