observe-before-editing

Verifying logs before editing code prevents incorrect changes caused by assuming execution failures. By checking actual system outputs in directories like `.maestro/cache/`, you identify the true root cause instead of relying on assumptions.

To troubleshoot execution failures with log analysis, check the `.maestro/cache/learnings/` directory for generated files and review `.maestro/cache/*.log` files to find the specific errors causing the feature to fail.

The best way to debug without immediately changing code is manual execution and output verification. Run commands manually to observe real-time errors and confirm the existence of expected files in the `.maestro/cache/` directory.

To check if previous operations generated expected output files, verify the contents of the `.maestro/cache/learnings/` directory. This output verification confirms whether files were successfully created before you attempt any code modifications.

You should avoid immediate code edits during troubleshooting when a feature fails, because assumed execution failures can lead to incorrect changes. Instead, perform output verification and log analysis first to understand the actual failure.