RFP Response Drafting with Claude Code: SKILL.md Template
A production playbook for RFP response drafting in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Sales engineering teams
The problem
Sales engineering teams need RFP response drafting to run repeatedly against RFP docs, product docs, security answers, and prior responses. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach RFP docs, product docs, security answers, and prior responses per run, and let Argo turn the folder into a repeatable Claude Code execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For RFP response drafting, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run RFP response drafting using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "rfp_response_drafting".
Run this on Argo