write-a-request-for-proposal
Draft a fair request for proposal with comparable responses and explicit evaluation rules. Use when an organization is inviting suppliers to propose a consequential product or service.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- write-a-request-for-proposal
- category
- write
- description
- Draft a fair request for proposal with comparable responses and explicit evaluation rules. Use when an organization is inviting suppliers to propose a consequential product or service.
# write-a-request-for-proposal
## Procedure
1. Confirm procurement route, authority, timetable, communications channel, and confidentiality rules.
2. Summarize the outcome, context, users, current state, scope, and exclusions.
3. Include testable requirements, service expectations, transition needs, data handling, and exit obligations.
4. Ask suppliers to state assumptions, dependencies, exceptions, evidence, pricing, and total lifecycle cost.
5. Publish the evaluation criteria, weighting, mandatory gates, and decision process.
6. Define question, amendment, submission, presentation, clarification, and award dates.
7. Make response instructions structured enough for like-for-like comparison.
8. Review for vendor bias, unnecessary barriers, ambiguity, and disclosure risk before release.
## Guardrails
- Do not promise award, volume, exclusivity, or contract terms without authority.
- Use approved legal and procurement language rather than inventing binding terms.
- Give material clarifications to all eligible bidders through the same controlled channel.
## Done
- An issued RFP package contains scope, requirements, response format, timeline, and evaluation method
- Review evidence shows mandatory gates and weighted criteria match the approved need
- Amendments, bidder questions, and release approval have an auditable record
GitHubで見る