---
name: quotation-sow-drafter
description: Draft coherent quotations and statements of work that align scope, deliverables, milestones, assumptions, and commercial terms without blurring commitments and estimates. Use this whenever users ask for a quote, quote draft, pricing sheet, SOW, scope document, work order, implementation plan draft, 見積書, or 作業範囲定義; use it for pricing, scope, milestones, and acceptance terms, not for RFP questionnaires or evaluator-facing bid responses.
---

# Quotation SOW Drafter

## Overview

Create clear quotation and statement-of-work drafts that reduce ambiguity between commercial agreement and delivery expectations.

This skill is for:
- Quotes and pricing summaries
- Statements of work
- Scope and deliverables definitions
- Milestone-based implementation plans
- Commercial handoff documents

## Triggering Cues

Use this skill when user messages include:

- draft a quote
- create an SOW
- scope of work document
- pricing and deliverables
- implementation plan draft
- define project scope and milestones

## Input Requirements

Ask for or infer:

1. Scope in and scope out
2. Deliverables
3. Timeline or milestone expectations
4. Pricing model and payment assumptions
5. Acceptance criteria and dependencies

## Output Format

Always output:

1. **Scope Summary**
2. **Deliverables and Milestones**
3. **Timeline**
4. **Acceptance Criteria**
5. **Pricing and Payment Terms**
6. **Dependencies, Assumptions, and Change Control**

## Workflow

1. Separate commercial terms from delivery commitments.
2. Define scope boundaries explicitly.
3. Convert work into measurable deliverables and milestones.
4. Add acceptance logic to avoid ambiguity.
5. State assumptions and change triggers clearly.

## Examples

### Example 1
Input:
- Prepare a fixed-fee SOW for a 10-week onboarding and integration project.

Output style:
- Clear milestone breakdown
- Strong scope boundaries
- Acceptance criteria tied to deliverables

### Example 2
Input:
- Draft a quote for phased implementation with optional add-on work.

Output style:
- Separate base scope and optional items
- Commercially readable
- Easy for sales and delivery teams to align on

## Guidelines

- Distinguish commitments from estimates.
- Make scope exclusions explicit.
- Keep milestone definitions testable.
- Do not hide dependencies or approval gates.
