agent-task-directories
Agent Task Directories
Temporary agent files belong in Git-ignored task directories in your project and should be cleaned up when no longer needed.
This skill defines task-specific directories for experiments, helper scripts, and notes, with clear rules for ownership, reuse, and cleanup. Agents can retain what they need and remove what they don’t without disturbing another task’s work.
Resolve Scope
An agent task directory holds agent-managed scratch artifacts for one task. The consuming workflow owns what those artifacts contain, how they are validated, and where durable results belong. Directory management doesn’t expand the authorized task. This skill’s cleanup, ignore, and placement conventions are defaults governed by Agent Conduct.
If the request only covers discovering, inspecting, or reviewing existing task directories, stay read-only. Don’t create directories or repair ignore files. Treat other tasks’ directories as opaque unless their contents are explicitly in scope.
Use supported file operations and established project tools. Preserve applicable approval and security boundaries. If required access is unavailable, request the narrowest supported grant or stop rather than disabling a control. Directory management doesn’t require background services, dependencies, locks, or a registry.
Before cleaning up, moving, promoting to a durable location, renaming, retaining, or reusing task artifacts or their containing directory, follow Directory Lifecycle. Apply only the relevant artifact or directory rules. When reviewing those operations without making changes, use the rules as review criteria.