Complete CCAR-F Anthropic Materials

Option D identifies the dominant capacity problem. Anthropic states that everything sent in a request counts toward the context window : the system prompt, messages, documents, tool results, tool definitions, and the output Claude generates. A 175,000–190,000-token document is therefore not the complete input. Adding a 2,500-token tool schema, system instructions, wrappers, and the reserved output budget can push a nominally sub-200,000-token document close to or beyond the effective limit. Anthropic also warns that more context is not automatically better and that accuracy and recall can degrade as token count grows, a behavior described as context rot. That combination explains why short documents remain accurate while long documents lose information. Option A predicts a problem independent of document length, contradicting the measurements. Option B is an unsupported generalization and does not account for tool-definition overhead. Option C recognizes long-context degradation but ignores the concrete evidence that hidden prompt components consume the same window. The correct response is to count tokens for the complete request before submission, reserve output capacity, and chunk or retrieve relevant sections when the total approaches the model’s supported window.

================

Option A implements an iterative orchestrator-worker loop in which synthesis is treated as an evaluation checkpoint rather than an irreversible transition to report generation. When synthesis identifies missing evidence, the coordinator can formulate focused follow-up tasks, send them to the agents with the appropriate tools, and repeat synthesis after receiving the additional findings.

Anthropic’s multi-agent research architecture follows this pattern: the lead agent synthesizes subagent findings and determines whether further research is required. If gaps remain, it creates additional subagents or refines the research strategy. This preserves specialization and centralized control.

Option B makes the incompleteness visible but does not improve research coverage. Option C may increase initial cost without guaranteeing that the specific gaps discovered during synthesis will be addressed. Option D weakens separation of concerns by giving the synthesis agent search capabilities that belong to the research specialists. Targeted redelegation is more efficient because the second research round is informed by concrete deficiencies rather than speculative breadth. It also allows the coordinator to track completeness explicitly before authorizing final report generation.

================

Option B removes the prompt-level suppression responsible for the false negatives while preserving machine-readable metadata. Anthropic’s current code-review prompting guidance warns that instructions such as “only report high-severity issues” or “be conservative” may be followed literally: Claude can identify genuine defects during analysis but omit them from its output. Anthropic recommends requesting all findings and applying filtering separately.

Confidence and severity fields allow downstream code to apply adjustable thresholds without forcing the model to discard evidence during generation. A schema can require fields such as file, line, description, severity, confidence, evidence, and recommended action; Anthropic’s Structured Outputs documentation supports enforcing such a response contract. Option A repeats the same suppressive instruction and is likely to reproduce the same omissions. Option C removes the explicit reporting structure and leaves filtering behavior undefined. Option D may improve analysis depth, but extended reasoning does not override a direct instruction to suppress uncertain findings. Separating detection from deterministic filtering preserves recall, structure, and operational control.

Option D preserves Claude Code’s standard coding-agent instructions while adding the specialized review criteria. Anthropic documents that --system-prompt replaces the entire default system prompt, including its tool guidance, safety instructions, and coding conventions. It does not technically disable tools, but removing that guidance can make the invocation behave like a narrowly scoped text processor. --append-system-prompt retains the default behavior and layers the review instructions on top.

The prompt should explicitly direct Claude to use Read, Glob, and Grep to inspect definitions, callers, tests, and related modules whenever the diff alone is insufficient. Option A is incorrect because --system-prompt is not incompatible with tools. Option B is also inaccurate: --allowedTools pre-approves tool execution; it does not make tools available when -p would otherwise disable them. In this command, --dangerously-skip-permissions already bypasses permission prompts. Option C is false because Claude Code officially supports piped standard input in non-interactive mode. The repaired invocation should therefore use --append-system-prompt and include an explicit repository-exploration requirement. Claude Code programmatic usage , CLI system-prompt reference

================