| name | rfp-response-extraction |
| description | Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with each item categorized, flagged for mandatory status, source-traced, and ready for owner assignment and tracking. Handles addenda by letting later versions override earlier ones.
|
RFP Extraction Skill
Firm Profile (REQUIRED — fill in before use)
These values define who your firm is and how it writes. See SETUP.md.
- FIRM NAME: [FIRM NAME]
- WHAT THE FIRM DOES: [one sentence]
- ROLE BOUNDARY: [what the firm will NOT claim to do — leave blank if none]
- VENDOR STANCE: [vendor-neutral OR resells/implements specific products]
- SPECIALIZATION: [domains the firm credibly claims]
- VOICE: [3–5 adjectives]
Purpose
Parse an RFP stored in SharePoint and populate a structured RFP Tracker
List with every actionable item, each broken out by category, flagged mandatory
or not, traced to its source location, and given tracking columns for owner
assignment and progress monitoring.
Prerequisites
- The RFP document (PDF, Word, etc.) must be accessible in SharePoint.
- The agent must have permission to create Lists and List items in the target site.
- If the package includes addenda, attachments, or a referenced Q&A document,
those should also be accessible. Flag any that are missing in the summary.
Step 1 — Read the RFP Document
- Locate the RFP file in SharePoint using the path/URL provided. If the package
has multiple documents (RFP body, SOW, attachments, addenda, Q&A), list every
one and capture filename, page count, and document type.
- Extract the full text of each document.
- If a document is long, process it in sections but treat it as one document for
extraction.
