# Give the task a finish line.

Name the outcome, the relevant input and what must stay unchanged. Start with one deliverable you can check.

Use in: Codex or Claude Code

Reviewed: 2026-10-09

## Before you start

- The observed problem and the expected behavior.
- A relevant file, screenshot or reproduction.

## How to use it

1. Describe the issue in one sentence.
2. Name what must stay unchanged and ask for a small fix.
3. Agree on one check before expanding the work.

## Prompt to copy

Investigate why the checkout button does not respond. Read the checkout component and its event handler first. Keep the payment flow and styles unchanged. Propose the smallest fix and one check that reproduces the problem and verifies the result. Ask for missing evidence before making changes.

## A practical example

Illustrative scenario, not a measured case study.

A checkout button stops responding. Investigate its event handler first; keep payment behavior and visual styling unchanged.

## Check the result

- The proposed fix addresses the reported symptom.
- The agreed check covers the original failure.
- Unrelated files and features remain outside the scope.

INMC example. A clearer scope can reduce avoidable rework; no fixed usage saving is promised.

## Official reference

[Claude Code · Best practices](https://code.claude.com/docs/en/best-practices)



[Back to the library](https://ineedmycredits.com/smarter-usage)

Canonical HTML: https://ineedmycredits.com/smarter-usage/scope