A Long Report Turned Into a Decision Brief
Turn a contract, policy or tender into an obligations table with pages and exact wording, then hunt the clauses summaries always drop.
به چه درد می‌خورد
وقتی باید روی سند تصمیم بگیری - قرارداد، آیین‌نامه، مناقصه - خلاصه به دردت نمی‌خورد، جدول تعهدها می‌خورد. این متن جدولی می‌سازد با تعهد، طرف متعهد، مهلت، شماره صفحه و عین عبارت، و بعد جداگانه دنبال مبلغ‌ها، تاریخ‌ها، ارجاع به پیوست‌های نیامده و عبارت‌های کشدار مثل «به صلاحدید خود» می‌گردد. بندی مثل تمدید خودکار این‌طور از قلم نمی‌افتد.
خود اسکیل
Use this when you have to act on a document - a contract, a policy, a tender, a report - not merely understand it. Paste this after uploading: --- Read the whole document and build a table with one row per item and these columns: Item | What it requires | Who it binds | Deadline or trigger | Page | Exact wording. Include only items that create an obligation, a cost, a deadline, a condition, or a right to end the agreement. Use the document's own words in the last column. Write "not stated" in any cell the document does not fill - never infer it. List nothing that is not in the document. --- Then ask each of these as its own separate message: - Every amount, rate, fee, penalty and threshold, with its page. - Every date and every period, and what starts each clock running. - Every reference to another document, schedule, annex or standard that was not included in this file. - Every sentence containing "may", "at its sole discretion", "reasonable", "from time to time" or "subject to" - these are the places where the meaning gets decided later, by somebody else. - What a reader would assume this document covers that it does not. Finish by pulling the five rows that carry the most money or the hardest deadline, and opening every one of those pages yourself. The failure this prevents: a tidy summary that reads well in a meeting and leaves out the auto-renewal clause, because nobody asked the question that would have surfaced it.
نصبش چطور است
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.