An exploration agent may leave repository or specification material outside the repo for future agents
Source references: 1The optional exploration step explicitly requires Markdown notes outside the repository and makes them accessible to all future subagents. It sets no limits on note contents, location, retention, or cleanup.
If notes contain private code excerpts, internal architecture, issue contents, or other sensitive context, they create a persistent copy outside repository access controls and normal cleanup, with access broadened to later agents.
This is optional but actionable: an exploration agent may inspect repository files or external documentation and is told to save Markdown notes outside the repository for all future subagents. If those notes contain private code, specifications, or credential fragments, the unspecified location, audience, and retention period could broaden exposure. The text does not prove sensitive data will be written; users can require a bounded temporary directory, secret exclusion, task-only access, and cleanup.
2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.