se-work-loop

Multi-unit plan execution across fresh contexts preserves progress by persisting durable local state under the project context directory. This approach runs each implementation unit in a new session while maintaining state to avoid chat bloat and ensure continuity.

A per-unit verification gate is a file-level check enforced during plan execution to validate that an implementation unit meets specific criteria before proceeding. It works with a final loop verification to determine overall plan completion.

You can resolve the verification command flexibly using CLI flags, YAML frontmatter in the plan file, or in-plan handoffs. The loop execution system checks these sources to determine the correct verification command for the workflow.

Automated implementation loops support both attached and background runtimes. You can use status and management commands to monitor background loop execution and track progress across multiple implementation units.

The plan execution loop stores durable local state under the project context directory at .context/software-engineering/se-work-loop. This ensures progress is preserved across multiple implementation-unit iterations and fresh child sessions.