Productivity
Commit versus what closed
Commit versus what closed turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
The prompt
Commit versus what closed guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information 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: Compare commit at {{lockTime}} to closed-won in {{period}} from {{forecastView}}. List flips after lock. Do not edit forecast categories. Sources: {{crmForecastView}}, lock snapshot if you have one, closed-won in the window. 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 change commit, best case, or pipeline category. Deliverable: Commit, actual, gap, flips with before/after, links. Review point: I change categories if they were wrong.
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt1012 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: Compare commit at a specific lock time to closed-won in a specific period from a specific forecast view. List flips after lock. Do not edit forecast categories. Sources: a specific crm forecast view, lock snapshot if you have one, closed-won in the window. 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 change commit, best case, or pipeline category. Deliverable: Commit, actual, gap, flips with before/after, links. Review point: I change categories if they were wrong.
Useful structure, room to move.
Commit versus what closed guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information 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
Closed-lost without a reason
Closed-lost without a reason turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Coverage versus quota by segment
Coverage versus quota by segment turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Duplicate opportunity pack
Duplicate opportunity pack turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Lifecycle versus opportunity mismatch
Lifecycle versus opportunity mismatch turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini