Chain-of-thought (CoT) prompting asks an AI model to break a complex problem into smaller intermediate steps before reaching a conclusion or selecting an action. This decomposition is presented as a way to improve accuracy without additional model training, and as a foundation for reasoning within agent workflows. section 2.3.1
Arithmetic decomposition
For a cake with eight slices, give away two slices twice, then receive one back: 8 − 2 = 6, 6 − 2 = 4, and 4 + 1 = 5. The intermediate operations make the final answer traceable rather than a detached generated number. section 2.3.1
In a ReAct-style agent, CoT belongs in planning: it reasons from objectives, the agent’s current knowledge, defined boundaries, hypotheses, and operational or security posture to choose a reconnaissance strategy. Planning should lead to explicit actions, followed by observation and durable recording rather than an untracked stream of model output. section 4.2.2 section 2.3.1
Use CoT as a controlled planning stage in an agent pipeline:
- Supply the objective, components under evaluation, authorized boundaries, relevant hypotheses, and security posture. section 4.2.2
- Translate the plan into specific, bounded tool actions rather than treating reasoning as action itself. section 2.3.1 section 4.2.2
- Interpret returned data, then save outputs and context in artifacts so later sessions can retrieve essential findings. section 4.2.2 section 2.3.1
- Keep recon actions safe and authorized; even low-impact requests can appear in a target’s logs. section 4.2.2
Table 4.1. The ReAct pipeline summary
|
Stage
|
Purpose
|
What our passive recon agent does
|
|
Plan
|
Decide what to examine.
|
Generate a small list of likely subdomains for the target.
|
|
Act
|
Gather data safely.
|
Resolve DNS and send a single HEAD / request.
|
|
Observe
|
Interpret results.
|
Extract headers and capture lightweight TLS hints.
|
|
Record
|
Preserve context.
|
Append a JSONL artifact to
recon.jsonl
with timestamps and notes.
|
The ReAct pipeline places chain-of-thought reasoning in Plan and connects it to bounded data gathering, interpretation, and JSONL recordkeeping. section 4.2.2




























