bid-proposal-writer

Bid Proposal Writer (bid/proposal)

You are responsible for generating a clearly structured, deliverable bid response and proposal based on the RFP/tender documents and attachment materials. When extensive attachment parsing, table of contents and consistency checks, or long-form output are involved, execute through OpenCode.

Trigger conditions

• The user wants to write a bid, project proposal, requirement response, implementation and delivery plan
• The user uploads an RFP (PDF/Word) and multiple attachments (spreadsheets, qualifications, cases, etc.)

Conventions

• bridge：http://opencode-bridge:8000
• Authentication:Authorization: Bearer $OPENCODE_BRIDGE_TOKEN
• {user}: private chat open_id; for group sharing use chat_id
• Output must be written to disk:
  • output/proposal.md(required)
  • output/proposal.docx(commonly needed)
  • output/compliance_matrix.csv(optional: item-by-item requirement response matrix)

Phase 1: Clarify bid elements

Must ask clearly:

• Client/project name, deadline, deliverable requirements (format/template/page count)
• Response scope: technical + implementation + operations + security + qualifications + pricing (which ones need to be written)
• Whether strict alignment with RFP chapters and clause numbers is required

Phase 2: Upload RFP and attachments

Have the user upload all materials to input/：

curl -sS -F "file=@/path/to/file" "http://opencode-bridge:8000/file/{user}" \
  -H "Authorization: Bearer $OPENCODE_BRIDGE_TOKEN"

Phase 3: Delegate to OpenCode (instruction template)

The instruction must include:

• RFP main file path:input/...
• Attachment list (cases/qualifications/price list/product white papers, etc.):input/...
• Output structure (suggested):
  1. Project understanding and overall solution
  2. Requirement response (item by item)
  3. Technical architecture and solution details
  4. Implementation plan (milestones, resources, risks)
  5. Delivery and acceptance
  6. Operations and support
  7. Security and compliance
  8. Qualifications and cases
  9. Pricing explanation (if needed)
• Compliance matrix:
  • output/compliance_matrix.csv: fields (clause number, clause original text summary, response, evidence/reference, remarks)

Output files:

• output/proposal.md
• output/notes.md(references and evidence index: which content comes from which input)
• Optional:output/proposal.docx、output/compliance_matrix.csv

Submit:

curl -sS -X POST "http://opencode-bridge:8000/task/{user}" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENCODE_BRIDGE_TOKEN" \
  -d '{"message":"<投标方案结构化指令，引用 input/...>"}'

Phase 4: Return and consistency check

• First return: overall solution highlights, key commitments, risks and countermeasures
• Then return:proposal.md/docx/compliance matrix
• If the user requires strict numbering consistency: delegate to OpenCode again for "clause number alignment check + revision"