Writing
Repeat close-date push-outs
Repeat close-date push-outs turns source material and intent into clear, purpose-built writing with clear constraints and an explicit output.
The prompt
Repeat close-date push-outs guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when drafting, rewriting, editing, or translating text and you want a response that is easier to evaluate and act on.
text prompt
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find deals in {{pipeline}} with {{n}}+ later close-date moves. Show each push. Do not change close dates. Sources: {{crm}} close-date history, notes, stage at each push. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not reset close dates. If history is missing, say so. Deliverable: Deal, push count, old vs new dates, note or none, suggested inspect question. Review point: I reset the date if it is fiction.
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt957 characters
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find deals in a specific pipeline with 5+ later close-date moves. Show each push. Do not change close dates. Sources: a specific crm close-date history, notes, stage at each push. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not reset close dates. If history is missing, say so. Deliverable: Deal, push count, old vs new dates, note or none, suggested inspect question. Review point: I reset the date if it is fiction.
Useful structure, room to move.
Repeat close-date push-outs guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when drafting, rewriting, editing, or translating text and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Brand Voice Extractor and Style Guide
Brand Voice Extractor and Style Guide turns source material and intent into clear, purpose-built writing with clear constraints and an explicit output.
ChatGPTClaudeGemini
Content Editor & Improver
Content Editor & Improver turns source material and intent into clear, purpose-built writing with clear constraints and an explicit output.
ChatGPTClaudeGemini
Customer FAQ Section Builder for Support Deflection
Customer FAQ Section Builder for Support Deflection turns source material and intent into clear, purpose-built writing with clear constraints and an explicit output.
ChatGPTClaudeGemini
Newsletter Issue Builder
Newsletter Issue Builder turns source material and intent into clear, purpose-built writing with clear constraints and an explicit output.
ChatGPTClaudeGemini