rfp-responder
Use when an RFP, RFI, RFQ, security questionnaire, vendor questionnaire, or proposal request arrives and the team needs a structured response — parsing multi-section buyer-dictated requirements (MANDATORY vs WEIGHTED vs NICE-TO-HAVE), building a Shipley-method proof-point matrix mapping each requirement to a verifiable proof point, articulating 3-5 win-themes that ladder up across requirements, and producing a Shipley-derived winrate estimate that informs a bid / no-bid / partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strat
Profile →npx skills add alirezarezvani/claude-skills --skill rfp-responder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# rfp-responder ## Purpose Help Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment: 1. **What is this RFP actually asking?** (parse sections, tag every requirement MANDATORY / WEIGHTED / NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints) 2. **What is our true fit?** (proof-point matrix per requirement: STRONG / PARTIAL / GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark) 3. **What is our win-theme strategy?** (Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets) 4. **What is our realistic winrate?** (Shipley-derived factor model: fit, incumbent, relationship strength, decision-criteria alignment, late-entry, competitor count, deal size — produces estimate + confidence band) 5. **Should we bid?** (deterministic verdict: BID / PARTNER-BID / NO-BID with named factors driving the call) The skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid. **It never invents claims.** ## When to use - A 30+ page RFP / RFI / RFQ has landed with a 7-14 day
- Purpose
- When to use
- Workflow
- Step 1 — Parse the RFP
- Step 2 — Score fit per requirement
- Step 3 — Apply win-theme strategy
- Step 4 — Estimate winrate
- Step 5 — Decide
- Scripts
- References
- Assumptions
- Anti-patterns
- Distinct from
- Forcing-question library (Matt Pocock grill discipline)
python scripts/rfp_parser.py --input rfp.md --output json > parsed.json python scripts/response_drafter.py --input draft_input.json --output markdown > matrix.md python scripts/winrate_predictor.py --input deal_context.json --profile enterprise-software --output markdown
What does the rfp-responder skill do?
Use when an RFP, RFI, RFQ, security questionnaire, vendor questionnaire, or proposal request arrives and the team needs a structured response — parsing multi-section buyer-dictated requirements (MANDATORY vs WEIGHTED vs NICE-TO-HAVE), building a Shipley-method proof-point matrix mapping each requirement to a verifiable proof point, articulating 3-5 win-themes that ladder up across requirements, and producing a Shipley-derived winrate estimate that informs a bid / no-bid / partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strat
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill rfp-responder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.