작업 범위 문서 쓰는 프롬프트
무엇을 하고 무엇을 안 하는지를 같은 비중으로 씁니다.
| 분류 | 사무 › 제안서·사업계획 |
|---|---|
| 태그 | 초안작성체크리스트소상공인 |
Write a statement of work. ***Give what is excluded the same weight as what is included.*** **Nearly every dispute comes from something that was never written down as excluded.** 1. **Deliverables** — what is handed over and when. **Down to format and quantity** 2. **What is included** — specifically 3. **What is not included.** ***Start with what the client would assume is included.*** **If this section is short, the document is not doing its job** 4. **Revisions: how many and of what scope.** **Where the line falls between a revision and new work — in a sentence** 5. **What the client provides, and by when.** **State explicitly that late material moves the schedule** 6. **How additional requests are handled** — how they are received and how they are priced. ***Leave it undecided and it becomes a negotiation at the worst moment*** 7. Schedule and milestones, with the approval condition for each stage 8. **Completion criteria** — what has to be true for this to be finished **Output** - The scope document - ***The three items most likely to be disputed***, and why - Anything left as `[decision needed]` because I did not specify it - What the client will ask after reading this **Rules** - ***Do not invent amounts, durations, or counts I did not give you*** - ***Do not leave "to be agreed later". That is the future dispute.*** Mark it as a decision item instead - ⚠️ **Do not judge contractual validity or legal enforceability.** Refer that to a professional
붙여 넣으면 맨 아래에 채울 칸(맡을 일 · 고객 상황 · 기간·금액 조건)이 나옵니다
어떤 프롬프트인가
범위 분쟁은 "안 하는 것"이 안 적혀 있어서 생긴다. 이 프롬프트는 포함 항목만큼 제외 항목을 구체적으로 적고, 추가 요청이 들어올 때의 처리도 미리 정한다.
같은 분류의 프롬프트
| 이미지·사업 설득 지원 프롬프트 | |
| Product Manager 역할 프롬프트 | |
| 스타트업 공동창업자 역할을 맡기는 프롬프트 | |
| 에이전시 성장 병목 진단 프롬프트 | |
| 카지노 목록 수익 시뮬레이션 프롬프트 |