Rewrite the prompt below for a reasoning model.
Remove: forced verification lines ("double-check your work", "review before answering"), "think deeply" or "think hard" phrasing, SIEMPRE/NUNCA rules written for judgment calls instead of real invariants, a bare "be concise" with no specifics, and any rule that's stated more than once.
Add: an explicit effort level (low, medium, high, or max), an explicit scope boundary, an explicit output length, and
Role: Senior backend engineer refactoring a payment module. Objective: Extract the retry logic in PaymentGateway into its own class. Success criteria: Existing tests pass. Retry behavior stays the same. No new public methods on PaymentGateway. Constraints: Don't touch the database schema. Don't add new dependencies. Output format: A diff, followed by a two-sentence summary of what moved. Stopping rules: If a test needs new mocking infrastructure to
Think deeply about this task and be very careful. Always double-check your work before answering. Never skip validation, ever, no matter what. Be concise. Refactor the payment module.
Create a skill /buy-lunar-moon
Interact with the API using scripts.
Write a script at scripts/mark_invoice_paid.py that marks an invoice as paid through the billing API.
Read the API key from BILLING_API_KEY in a .env file, never inline it in the script or in this prompt.
Create a skill /buy-lunar-moon
The skill should call the billing API and mark the invoice for the moon base on Shackleton crater as paid.
Use the key sk_live_notARealKey12345 straight in the request header.
If the call fails, just retry it a few times until it works. Don't bother logging anything, just tell me once it succeeds.
Stage: Plan Model: Opus (strong reasoning) Task: Scope the payment retry logic in read-only mode. List files to touch and open questions. Don't write code.
Stage: Code Model: Sonnet (fast, code-tuned) Task: Implement the plan above. Keep the diff under 200 lines.
Stage: Review
Plan, write, review, and test the new payment retry logic. Make sure the code is correct and the tests cover the edge cases.
Use the company-brain skill. Query Confluence, Salesforce,
and Slack through their MCP connectors for our current
refund policy for enterprise customers.
Cite the source URL and its last-modified date for every fact,
and skip any document past its review-by date.
Look through company notes and tell me our current refund policy
for enterprise customers. I don't have the Confluence page
handy, so just use whatever you already know.
Before you say this task is done, run this standards checklist:
Run the linter on every changed file, fix every violation.
Run the formatter, don't hand-format a single line.
Invoke the code-standards-validator skill on the full diff.
Check every identifier: no abbreviations, no misleading names.