Skip to main content
Human guide: work with your agent → Use Claude Code to produce one checked, reviewable pilot. Ask for an outcome and evidence, not an unexplained sequence of provider calls.

​
Before you start

Install the plugin or use the coding-agent setup. Work inside the intended project folder.
Confirm the workspace before processing the file.

​
1. State the input and acceptance rule

The requested output is your review contract. It does not change a prebuilt’s schema or create an automatic approval system.

​
2. Require discovery before execution

Ask Claude to search and describe the current Play or tool. For example:
Compare required fields and header mappings with the actual file. For custom source, require deepline plays check <file> before a run. A successful check validates supported structure, not business accuracy.

​
3. Review a bounded pilot

Use Batch CSV enrichment to select records without breaking quoted CSV fields. Ask Claude to explain which rows represent difficult cases. After the pilot, inspect the saved run, exported rows, and scoped usage. A useful review reconciles every source ID to a result or explicit exception.
The intended person and company match. Unresolved rows remain visible. The selected output fields and recorded usage support the scale decision.

​
4. Repeat only the approved method

If the Play, input mapping, or acceptance rule changes, check the changed method. Do not expand an unreviewed route because a small run merely completed. Ask Claude why a specific row was accepted or held. Use its evidence to correct the rule before processing the full file. See Design for agents for the reasoning behind these boundaries.