[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B09M3HT2V5Y3CTKJ6CW8S0":3,"skill-same:01M7B09M3HT2V5Y3CTKJ6CW8S0":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7B09M3HT2V5Y3CTKJ6CW8S0","rfp-responder",null,"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 \u002F no-bid \u002F partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strategy moment. Surfaces GAP requirements explicitly — never invents claims. NOT free-form proposal narrative authoring, NOT contract redline, NOT marketing collateral.","Bhomik04\u002Fava-","Bhomik04","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110253138?v=4","01M7AZ8PC968MDM5Y1W13JHHBN","bhomik goyal","01M7AZ8PDERKY1AFG9VZ8J0WSX",0,"MIT","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rfp-responder\ndescription: \"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 \u002F no-bid \u002F partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strategy moment. Surfaces GAP requirements explicitly — never invents claims. NOT free-form proposal narrative authoring, NOT contract redline, NOT marketing collateral.\"\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [commercial, rfp, rfi, rfq, shipley, win-theme, proof-points, structured-response, bid-management]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# rfp-responder\n\n## Purpose\n\nHelp Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment:\n\n1. **What is this RFP actually asking?** (parse sections, tag every requirement MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints)\n2. **What is our true fit?** (proof-point matrix per requirement: STRONG \u002F PARTIAL \u002F GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark)\n3. **What is our win-theme strategy?** (Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets)\n4. **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)\n5. **Should we bid?** (deterministic verdict: BID \u002F PARTNER-BID \u002F NO-BID with named factors driving the call)\n\nThe skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid. **It never invents claims.**\n\n## When to use\n\n- A 30+ page RFP \u002F RFI \u002F RFQ has landed with a 7-14 day response deadline\n- A security questionnaire (SIG, CAIQ, custom-buyer) needs structured Q&A — not prose\n- The team is preparing a bid \u002F no-bid review and needs a defensible winrate estimate\n- Sales Engineering has a proof-point library but no system to map proofs to requirements\n- Leadership wants to see fit % (STRONG \u002F PARTIAL \u002F GAP) before committing pursuit budget\n- A late-entry opportunity needs honest assessment of the relationship deficit\n\n**Do not use for:**\n- Free-form proposal narrative authoring → `business-growth\u002Fcontract-and-proposal-writer`\n- Contract redline AFTER award → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Marketing collateral \u002F category content → `marketing-skill\u002F*`\n- Discount approval on the awarded deal → `commercial\u002Fdeal-desk`\n- Pricing-model design for a new product → `commercial\u002Fpricing-strategist`\n\n## Workflow\n\n### Step 1 — Parse the RFP\n\nDrop the RFP markdown \u002F text into `scripts\u002Frfp_parser.py`. Output: structured JSON listing every requirement, tagged MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE based on cue words (must \u002F shall = MANDATORY; should \u002F weighted scoring numbers = WEIGHTED; may \u002F preferred \u002F desired = NICE-TO-HAVE). Captures section structure, scoring criteria if disclosed, deadline, submission format constraints.\n\n```bash\npython scripts\u002Frfp_parser.py --input rfp.md --output json > parsed.json\n```\n\n### Step 2 — Score fit per requirement\n\nFill `assets\u002Frfp_intake_template.md` with your proof-point library (each proof tagged with type + verifiable source + which requirement-tags it covers) and proposed win-themes. Feed parsed RFP + intake into `scripts\u002Fresponse_drafter.py`. Output: proof-point matrix per requirement with STRONG \u002F PARTIAL \u002F GAP, win-theme injection, GAP audit.\n\n```bash\npython scripts\u002Fresponse_drafter.py --input draft_input.json --output markdown > matrix.md\n```\n\n**Hard rule:** GAP requirements are surfaced, never invented around. Leadership reads the GAP audit and decides: close the gap, partner-bid, or no-bid.\n\n### Step 3 — Apply win-theme strategy\n\nShipley method: 3-5 themes that span requirements. Each theme answers \"why us over the incumbent \u002F competitor on the criteria the buyer named.\" `response_drafter.py` shows which themes thread through which requirements — a theme appearing in \u003C2 requirements is decorative, not strategic, and gets flagged.\n\n### Step 4 — Estimate winrate\n\nFeed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) into `scripts\u002Fwinrate_predictor.py`. Output: Shipley-derived estimate 0-100% + confidence band + factor breakdown + BID \u002F PARTNER-BID \u002F NO-BID verdict.\n\n```bash\npython scripts\u002Fwinrate_predictor.py --input deal_context.json --profile enterprise-software --output markdown\n```\n\n**No-bid threshold:** estimate \u003C 20% triggers automatic no-bid recommendation.\n\n### Step 5 — Decide\n\nTake parsed RFP + proof-point matrix + GAP audit + winrate estimate into the go \u002F no-go review. Skill does not commit pursuit budget — leadership does.\n\n## Scripts\n\n- `scripts\u002Frfp_parser.py` — section + requirement extractor (regex + cue-word heuristics, stdlib only)\n- `scripts\u002Fresponse_drafter.py` — proof-point matrix + win-theme injection + GAP audit\n- `scripts\u002Fwinrate_predictor.py` — Shipley-derived factor model + bid\u002Fno-bid verdict, industry-profile-tuned\n\nAll scripts: stdlib only (argparse, json, sys, pathlib, re, collections, statistics). `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fshipley_method_canon.md` — Shipley Proposal Guide v6, Shipley Capture Guide, APMP BoK, Tom Sant, Tom Searcy + Henry DeVries, Strategic Proposals research, Larry Newman\n- `references\u002Frfp_strategy_canon.md` — FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behavior\n- `references\u002Frfp_anti_patterns.md` — Shipley failure modes, APMP cases, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline, Gartner\n\n## Assumptions\n\n- **The RFP is the ground truth.** If the buyer asked it, answer it — in the order they asked, in the format they specified. Re-organizing for narrative flow is for proposals, not RFPs.\n- **Proof points must be verifiable.** A claim is only as strong as the case study, certification, customer reference, or technical attestation backing it. Unsourced claims become GAPs.\n- **Win-themes are buyer-side, not seller-side.** \"We're the leader in X\" is a marketing claim; \"Your operations team reduces incident MTTR by 60% with the same headcount\" is a win-theme. Shipley canon, not optional.\n- **Winrate estimates are directional.** The model is a discipline tool to force honest pursuit-qualification — not an oracle. Confidence band always wider than the point estimate suggests.\n- **Industry profiles tune base rates** — government RFPs reward compliance discipline; enterprise SaaS rewards reference accounts; healthcare rewards regulatory + security depth.\n- **Late entry is a structural disadvantage.** Entering after the RFP issued, with no relationship history, drops base rate ~15%. The skill names this, doesn't hide it.\n\n## Anti-patterns\n\n- **Inventing a proof point to fill a GAP.** Hard rule violation. GAPs surface for leadership decision, not for prose-laundering. See `references\u002Frfp_anti_patterns.md`.\n- **Responding to every RFP.** Without a qualified bid \u002F no-bid gate, the team burns capacity on \u003C20% winrate pursuits and loses the 50%+ pursuits to lack of focus. Bain commercial-discipline research.\n- **Generic response with no win-theme.** A proposal that could be sent verbatim by any competitor is decorative. Shipley failure mode #1.\n- **Missing a mandatory disqualifier late.** FedRAMP \u002F HIPAA \u002F ISO 27001 \u002F SOC 2 \u002F on-shore data residency caught on Day 12 of a 14-day response = wasted pursuit. Parser surfaces these on Day 1.\n- **Answering the question YOU wanted asked.** RFP responder discipline: answer what they asked, in their words, in their order. Re-framing belongs in cover letters, not in the compliance matrix.\n- **No compliance matrix.** Every requirement should map to a response section + page number. Evaluators score on a matrix; respondents who don't provide one self-disqualify on traceability.\n- **Late-entry without acknowledging the relationship deficit.** Entering cold against an incumbent with a 3-year relationship and no champion = sub-20% winrate. Pretending otherwise wastes Sales Engineering capacity.\n- **Treating WEIGHTED requirements like MANDATORY.** Score-weighted requirements reward depth on the high-weight items, not uniform mediocrity across all. Shipley capture method.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — free-form narrative proposals where YOU set the structure (executive briefs, capability statements, unsolicited proposals). RFP-responder handles **buyer-dictated structured Q&A** where the buyer set the questions, sections, scoring criteria, and format. Different artifact, different decision logic.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — contract redline and IP\u002Frisk review AFTER award. RFP-responder operates BEFORE award, on the response strategy.\n- **`marketing-skill\u002F*`** — external marketing assets (web copy, content, ASO, SEO, brand voice) for many-to-many audiences. RFP-responder produces a **single-buyer artifact** with deterministic compliance requirements.\n- **`commercial\u002Fdeal-desk`** — per-deal discount routing on a closing opportunity. RFP-responder is pursuit-stage; deal-desk is close-stage.\n- **`commercial\u002Fpricing-strategist`** — pricing-model design for a new product. RFP-responder consumes existing pricing as input to the commercial-terms section.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time before any script runs. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your STRONG \u002F PARTIAL \u002F GAP split on the MANDATORY requirements?\"**\n   Recommended: STRONG ≥ 70% on MANDATORY before bidding. PARTIAL\u002FGAP on any MANDATORY = either close the gap pre-submission or no-bid.\n   Canon: Shipley *Proposal Guide v6* — capture-management discipline, \"Pgw (probability of win) is bounded by your weakest MANDATORY.\"\n\n2. **\"Is there an incumbent, and how strong is their position?\"**\n   Recommended: strong incumbent (3+ years, no displacement event) drops base winrate ~30%. Don't bid without a named displacement trigger.\n   Canon: Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.\n\n3. **\"Did you enter the conversation before or after the RFP issued?\"**\n   Recommended: late-entry (after RFP issued, no prior engagement) drops winrate ~15% and signals the RFP was scoped to someone else's strengths.\n   Canon: Tom Searcy + Henry DeVries *How to Win Big Business* — \"If you didn't help write the RFP, you're column fodder.\"\n\n4. **\"What are your 3-5 win-themes, and does each thread through ≥2 requirements?\"**\n   Recommended: themes that appear in only one requirement are decorative. Themes must ladder up across MANDATORY + WEIGHTED sections.\n   Canon: Shipley *Capture Guide* — win-themes are the buyer-side answer to \"why us\" across the evaluation criteria, not seller-side feature lists.\n\n5. **\"For every claim in the response, can you name the verifiable source?\"**\n   Recommended: every claim → case study \u002F certification \u002F customer reference \u002F technical attestation \u002F benchmark. Unsourced claims = GAPs.\n   Canon: APMP BoK — \"Substantiation: every assertion in a proposal must be backed by evidence the evaluator can independently verify.\"\n\n6. **\"What's the bid \u002F no-bid threshold you committed to BEFORE seeing this RFP?\"**\n   Recommended: pre-committed threshold (e.g., winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion). Post-hoc rationalization is how teams end up bidding 5% pursuits.\n   Canon: Bain RFP-win-rate studies — disciplined bid\u002Fno-bid gates lift win-rate from ~15% to ~35%.\n\n7. **\"What does the buyer's evaluation team actually score on?\"**\n   Recommended: if the RFP discloses scoring criteria, weight your response effort proportionally. If undisclosed, ask. If you can't ask, that itself is a relationship-deficit signal.\n   Canon: Strategic Proposals proposal-management research — evaluators score on the rubric they were given, not on your narrative.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `rfp_parser.py` → `response_drafter.py` → `winrate_predictor.py` in sequence. If question 6 lands on \"we don't have a threshold,\" set one now or no-bid.\n","# rfp-responder\n\n## Purpose\n\nHelp Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment:\n\n1. **What is this RFP actually asking?** (parse sections, tag every requirement MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints)\n2. **What is our true fit?** (proof-point matrix per requirement: STRONG \u002F PARTIAL \u002F GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark)\n3. **What is our win-theme strategy?** (Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets)\n4. **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)\n5. **Should we bid?** (deterministic verdict: BID \u002F PARTNER-BID \u002F NO-BID with named factors driving the call)\n\nThe skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid. **It never invents claims.**\n\n## When to use\n\n- A 30+ page RFP \u002F RFI \u002F RFQ has landed with a 7-14 day response deadline\n- A security questionnaire (SIG, CAIQ, custom-buyer) needs structured Q&A — not prose\n- The team is preparing a bid \u002F no-bid review and needs a defensible winrate estimate\n- Sales Engineering has a proof-point library but no system to map proofs to requirements\n- Leadership wants to see fit % (STRONG \u002F PARTIAL \u002F GAP) before committing pursuit budget\n- A late-entry opportunity needs honest assessment of the relationship deficit\n\n**Do not use for:**\n- Free-form proposal narrative authoring → `business-growth\u002Fcontract-and-proposal-writer`\n- Contract redline AFTER award → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Marketing collateral \u002F category content → `marketing-skill\u002F*`\n- Discount approval on the awarded deal → `commercial\u002Fdeal-desk`\n- Pricing-model design for a new product → `commercial\u002Fpricing-strategist`\n\n## Workflow\n\n### Step 1 — Parse the RFP\n\nDrop the RFP markdown \u002F text into `scripts\u002Frfp_parser.py`. Output: structured JSON listing every requirement, tagged MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE based on cue words (must \u002F shall = MANDATORY; should \u002F weighted scoring numbers = WEIGHTED; may \u002F preferred \u002F desired = NICE-TO-HAVE). Captures section structure, scoring criteria if disclosed, deadline, submission format constraints.\n\n```bash\npython scripts\u002Frfp_parser.py --input rfp.md --output json > parsed.json\n```\n\n### Step 2 — Score fit per requirement\n\nFill `assets\u002Frfp_intake_template.md` with your proof-point library (each proof tagged with type + verifiable source + which requirement-tags it covers) and proposed win-themes. Feed parsed RFP + intake into `scripts\u002Fresponse_drafter.py`. Output: proof-point matrix per requirement with STRONG \u002F PARTIAL \u002F GAP, win-theme injection, GAP audit.\n\n```bash\npython scripts\u002Fresponse_drafter.py --input draft_input.json --output markdown > matrix.md\n```\n\n**Hard rule:** GAP requirements are surfaced, never invented around. Leadership reads the GAP audit and decides: close the gap, partner-bid, or no-bid.\n\n### Step 3 — Apply win-theme strategy\n\nShipley method: 3-5 themes that span requirements. Each theme answers \"why us over the incumbent \u002F competitor on the criteria the buyer named.\" `response_drafter.py` shows which themes thread through which requirements — a theme appearing in \u003C2 requirements is decorative, not strategic, and gets flagged.\n\n### Step 4 — Estimate winrate\n\nFeed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) into `scripts\u002Fwinrate_predictor.py`. Output: Shipley-derived estimate 0-100% + confidence band + factor breakdown + BID \u002F PARTNER-BID \u002F NO-BID verdict.\n\n```bash\npython scripts\u002Fwinrate_predictor.py --input deal_context.json --profile enterprise-software --output markdown\n```\n\n**No-bid threshold:** estimate \u003C 20% triggers automatic no-bid recommendation.\n\n### Step 5 — Decide\n\nTake parsed RFP + proof-point matrix + GAP audit + winrate estimate into the go \u002F no-go review. Skill does not commit pursuit budget — leadership does.\n\n## Scripts\n\n- `scripts\u002Frfp_parser.py` — section + requirement extractor (regex + cue-word heuristics, stdlib only)\n- `scripts\u002Fresponse_drafter.py` — proof-point matrix + win-theme injection + GAP audit\n- `scripts\u002Fwinrate_predictor.py` — Shipley-derived factor model + bid\u002Fno-bid verdict, industry-profile-tuned\n\nAll scripts: stdlib only (argparse, json, sys, pathlib, re, collections, statistics). `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fshipley_method_canon.md` — Shipley Proposal Guide v6, Shipley Capture Guide, APMP BoK, Tom Sant, Tom Searcy + Henry DeVries, Strategic Proposals research, Larry Newman\n- `references\u002Frfp_strategy_canon.md` — FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behavior\n- `references\u002Frfp_anti_patterns.md` — Shipley failure modes, APMP cases, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline, Gartner\n\n## Assumptions\n\n- **The RFP is the ground truth.** If the buyer asked it, answer it — in the order they asked, in the format they specified. Re-organizing for narrative flow is for proposals, not RFPs.\n- **Proof points must be verifiable.** A claim is only as strong as the case study, certification, customer reference, or technical attestation backing it. Unsourced claims become GAPs.\n- **Win-themes are buyer-side, not seller-side.** \"We're the leader in X\" is a marketing claim; \"Your operations team reduces incident MTTR by 60% with the same headcount\" is a win-theme. Shipley canon, not optional.\n- **Winrate estimates are directional.** The model is a discipline tool to force honest pursuit-qualification — not an oracle. Confidence band always wider than the point estimate suggests.\n- **Industry profiles tune base rates** — government RFPs reward compliance discipline; enterprise SaaS rewards reference accounts; healthcare rewards regulatory + security depth.\n- **Late entry is a structural disadvantage.** Entering after the RFP issued, with no relationship history, drops base rate ~15%. The skill names this, doesn't hide it.\n\n## Anti-patterns\n\n- **Inventing a proof point to fill a GAP.** Hard rule violation. GAPs surface for leadership decision, not for prose-laundering. See `references\u002Frfp_anti_patterns.md`.\n- **Responding to every RFP.** Without a qualified bid \u002F no-bid gate, the team burns capacity on \u003C20% winrate pursuits and loses the 50%+ pursuits to lack of focus. Bain commercial-discipline research.\n- **Generic response with no win-theme.** A proposal that could be sent verbatim by any competitor is decorative. Shipley failure mode #1.\n- **Missing a mandatory disqualifier late.** FedRAMP \u002F HIPAA \u002F ISO 27001 \u002F SOC 2 \u002F on-shore data residency caught on Day 12 of a 14-day response = wasted pursuit. Parser surfaces these on Day 1.\n- **Answering the question YOU wanted asked.** RFP responder discipline: answer what they asked, in their words, in their order. Re-framing belongs in cover letters, not in the compliance matrix.\n- **No compliance matrix.** Every requirement should map to a response section + page number. Evaluators score on a matrix; respondents who don't provide one self-disqualify on traceability.\n- **Late-entry without acknowledging the relationship deficit.** Entering cold against an incumbent with a 3-year relationship and no champion = sub-20% winrate. Pretending otherwise wastes Sales Engineering capacity.\n- **Treating WEIGHTED requirements like MANDATORY.** Score-weighted requirements reward depth on the high-weight items, not uniform mediocrity across all. Shipley capture method.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — free-form narrative proposals where YOU set the structure (executive briefs, capability statements, unsolicited proposals). RFP-responder handles **buyer-dictated structured Q&A** where the buyer set the questions, sections, scoring criteria, and format. Different artifact, different decision logic.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — contract redline and IP\u002Frisk review AFTER award. RFP-responder operates BEFORE award, on the response strategy.\n- **`marketing-skill\u002F*`** — external marketing assets (web copy, content, ASO, SEO, brand voice) for many-to-many audiences. RFP-responder produces a **single-buyer artifact** with deterministic compliance requirements.\n- **`commercial\u002Fdeal-desk`** — per-deal discount routing on a closing opportunity. RFP-responder is pursuit-stage; deal-desk is close-stage.\n- **`commercial\u002Fpricing-strategist`** — pricing-model design for a new product. RFP-responder consumes existing pricing as input to the commercial-terms section.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time before any script runs. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your STRONG \u002F PARTIAL \u002F GAP split on the MANDATORY requirements?\"**\n   Recommended: STRONG ≥ 70% on MANDATORY before bidding. PARTIAL\u002FGAP on any MANDATORY = either close the gap pre-submission or no-bid.\n   Canon: Shipley *Proposal Guide v6* — capture-management discipline, \"Pgw (probability of win) is bounded by your weakest MANDATORY.\"\n\n2. **\"Is there an incumbent, and how strong is their position?\"**\n   Recommended: strong incumbent (3+ years, no displacement event) drops base winrate ~30%. Don't bid without a named displacement trigger.\n   Canon: Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.\n\n3. **\"Did you enter the conversation before or after the RFP issued?\"**\n   Recommended: late-entry (after RFP issued, no prior engagement) drops winrate ~15% and signals the RFP was scoped to someone else's strengths.\n   Canon: Tom Searcy + Henry DeVries *How to Win Big Business* — \"If you didn't help write the RFP, you're column fodder.\"\n\n4. **\"What are your 3-5 win-themes, and does each thread through ≥2 requirements?\"**\n   Recommended: themes that appear in only one requirement are decorative. Themes must ladder up across MANDATORY + WEIGHTED sections.\n   Canon: Shipley *Capture Guide* — win-themes are the buyer-side answer to \"why us\" across the evaluation criteria, not seller-side feature lists.\n\n5. **\"For every claim in the response, can you name the verifiable source?\"**\n   Recommended: every claim → case study \u002F certification \u002F customer reference \u002F technical attestation \u002F benchmark. Unsourced claims = GAPs.\n   Canon: APMP BoK — \"Substantiation: every assertion in a proposal must be backed by evidence the evaluator can independently verify.\"\n\n6. **\"What's the bid \u002F no-bid threshold you committed to BEFORE seeing this RFP?\"**\n   Recommended: pre-committed threshold (e.g., winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion). Post-hoc rationalization is how teams end up bidding 5% pursuits.\n   Canon: Bain RFP-win-rate studies — disciplined bid\u002Fno-bid gates lift win-rate from ~15% to ~35%.\n\n7. **\"What does the buyer's evaluation team actually score on?\"**\n   Recommended: if the RFP discloses scoring criteria, weight your response effort proportionally. If undisclosed, ask. If you can't ask, that itself is a relationship-deficit signal.\n   Canon: Strategic Proposals proposal-management research — evaluators score on the rubric they were given, not on your narrative.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `rfp_parser.py` → `response_drafter.py` → `winrate_predictor.py` in sequence. If question 6 lands on \"we don't have a threshold,\" set one now or no-bid.\n",{"name":5,"tags":24,"author":34,"context":35,"license":15,"version":36,"description":7,"compatible_tools":37},[25,26,27,28,29,30,31,32,33],"commercial","rfp","rfi","rfq","shipley","win-theme","proof-points","structured-response","bid-management","claude-code-skills","fork","2.8.0",[38,39,40,41,42,43],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","decebbc662d2b278167b2a17d949479cf4cad66d","skills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-","https:\u002F\u002Fgithub.com\u002FBhomik04","2026-08-23 16:08:45",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Bhomik04\u002Fava- --skill rfp-responder",{"tool":56,"command":57},"bunx","bunx skills add Bhomik04\u002Fava- --skill rfp-responder",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Bhomik04\u002Fava- --skill rfp-responder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002FSKILL.md",true,[64,70,76,80,84,90,94],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Frfp_intake_template.md","ASSET","资产文件",4612,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Fassets\u002Frfp_intake_template.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Frfp_anti_patterns.md","REFERENCE","参考文档",9055,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Freferences\u002Frfp_anti_patterns.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Frfp_strategy_canon.md",5862,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Freferences\u002Frfp_strategy_canon.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fshipley_method_canon.md",5758,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Freferences\u002Fshipley_method_canon.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fresponse_drafter.py","SCRIPT","脚本",12493,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Fscripts\u002Fresponse_drafter.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Frfp_parser.py",10731,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Fscripts\u002Frfp_parser.py",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fwinrate_predictor.py",9111,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fcommercial\u002Fskills\u002Frfp-responder\u002Fscripts\u002Fwinrate_predictor.py",[99,106,113,120,127,134],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7B1YZ6EW9K9QQX1VYBXKKWH","spotify-dj","Intelligent music DJ that curates playlists, selects tracks based on mood, analyzes genres, and manages playback queues.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fspotify-dj\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7B1YWTNAF22PTEWNDGXQD9G","software-engineer","Autonomous software engineering, AST refactoring, Git worktree isolation, and self-healing test execution.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fsoftware-engineer\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7B1YS4HDDEFEJXBB8KW4T3K","obsidian-curator","Curates, organizes, links, and summarizes notes and research in the local Obsidian vault.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fobsidian-curator\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7B1YPJYQGB10P4EQ4SFEBFM","document-analysis","Parses, reads, extracts data, and summarizes multi-format documents (PDF, DOCX, Markdown, Text).","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocument-analysis\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7B1YJPE6J8PEWQRSRSHJ03C","docker-ops","Inspects, monitors, starts, stops, and diagnoses Docker containers and swarms via Named Pipe.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocker-ops\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7B1YEG3JESA4JPJNMVM1556","deep-research","Conducts multi-step autonomous research, source cross-verification, and structured literature synthesis.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdeep-research\u002FSKILL.md",[],[]]