Common Phase Instructions

To keep workflow agents consistent, standardize their behavior by enforcing safe file I/O operations, requiring absolute paths, and mandating a single source-of-truth workflow state file for tracking status across iterations.

Agent orchestration file operations fail when using shell commands and tilde paths because the standardized approach prohibits brittle shell manipulation and requires absolute paths derived from the home directory alongside native Read/Write/Edit tools.

The best way to manage codebase context loading for multi-step phase agents is to apply context efficiency constraints, directing agents to read only relevant sections with offset and limit parameters rather than embedding full codebase context into subagent prompts.

Standardize workflow state updates across build, review, and test agents by enforcing a repeatable pattern that marks status as in-progress or completed and logs errors directly into the single source-of-truth workflow state file.

Agent orchestration does work without context compaction issues by enforcing context efficiency constraints, directing agents to read only relevant sections with offset and limit reads, and coordinating work across iterations without embedding full codebase context.

You need to enforce deterministic state update patterns for workflow automation when running multi-phase agent execution, ensuring that reading codebase context files and updating workflow state remain predictable and the workflow doesn't drift across iterations.