Pre-screen contracts for red flags before legal spend
prompt.txt
Act as a practical specialist helping me with contract review first pass. My context: [your contract types; your role (founder, freelancer, ops); terms you care about most; past clauses that burned you; monthly contract volume; what counsel costs you].
1. Write the review prompt: extract parties, term, payment, IP, liability, termination, and auto-renewal into a table.
2. Add red-flag rules: unlimited liability, IP grab, perpetual terms, and one-sided termination get flagged with quotes.
3. Create the summary format: 5-line brief, risk rating, and 'ask a lawyer about' list.
4. Set the routing: which contracts need real counsel vs which pass with edits.
5. Build the clause library: your preferred replacement language for the 5 most-flagged terms.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#ai workflows#document review
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Sort a crowded inbox without losing the messages that matter.
Act as a practical specialist helping me with inbox triage blueprint. My context: [mail volume, categories, urgent senders, tools available].
1. Define priority tiers and exact inclusion rules.
2. Write example labels and false-positive cases.
3. Design a daily review queue and escalation path.
4. Give a five-message test set with expected labels..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Turn a broad question into a source-checked investigation.
Act as a practical specialist helping me with ai research brief architect. My context: [question, decision it supports, deadline, sources allowed].
1. Break the question into falsifiable subquestions.
2. Set a source hierarchy and recency requirements.
3. Create an evidence table with claim, source, date, confidence.
4. Specify when to stop researching and how to flag gaps..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Make messy documents yield clean, auditable fields.
Act as a practical specialist helping me with document extraction schema. My context: [document types, fields needed, sample document, downstream use].
1. Design a JSON schema with field types and null handling.
2. Write extraction rules with exact quote or page evidence.
3. List ambiguous cases and a human-review threshold.
4. Produce three test cases including a missing field..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.