rfp-writinglisted

# Technical RFP Writing & Review Review or draft technical RFP documents. Enforces clear structure, eliminates redundancy, and maintains formal plain-language style (Traditional Chinese). ## Output Language Match the language of the user's request, and apply it to *all* user-facing output — option labels, generated-document headings, table column names — not just prose. If the user explicitly asks for another language, that wins. Language follows the request, not the source material. When the user writes in Chinese but the uploaded document, code, or reference is in English, output stays Chinese. If the request is in Chinese, use Traditional Chinese (Taiwan business usage) and keep established technical terms in English. The English in this file is structural labelling for you, not literal output. Never mirror this file's language into your response. ## When to Use Trigger only when the user's request explicitly names one of these artifacts: - RFP (Request for Proposal) — reviewing, drafting, or section editing - 需求規格書 / 需求規劃書 / 招標規格書 / 招標文件 - Vendor requirement specification being sent out for bidding ## When NOT to Use The following are adjacent but distinct — each has its own conventions that conflict with RFP rules: - Migration plans, test plans, deployment plans - Runbooks, SOPs, operational procedures - ADR / ARB / architecture decision records - Design docs, technical specifications (internal) - Meeting minutes, decision memos, stakeholder pre-reads - Gener