tools-file-ops

Atomic file writes prevent corruption by writing to a temporary file and then renaming it. This approach ensures the target file is either completely updated or remains untouched, providing reliable script I/O.

The best way to ensure directories exist is to use an ensure_directory utility before writing. This verifies and creates the required base directory path structure, preventing write failures in CUI workflows.

Markdown metadata generation works by parsing existing content and constructing structured metadata blocks. This allows workflow scripts to inject and manage contextual data within plan files reliably.

Yes, you can use JSON output helpers to format data from file operations. These utilities structure script output into valid JSON, enabling downstream processes to consume the results of your file management tasks.

You configure a base directory path by setting a base directory variable and using path construction helpers. This ensures all file operations target the correct workflow directory, such as the .plan folder.

Workflow scripts fail writing to the .plan directory when it does not exist or lacks write permissions. Using directory management utilities to ensure the path exists before writing solves this issue.