prd-loop

To persist project orchestration loop state across sessions, you externalize cycle metadata into a LOOP-STATE.md file at the project scope, allowing implement-validate-learn-apply phases to decouple from individual user conversations.

Tracking technical debt counters during a build process involves reading and updating a centralized loop state file, which maintains debt metrics alongside batch pointers and decision queues to ensure continuity.

To initialize loop state for stepwise workflow orchestration, create a LOOP-STATE.md file at the project scope with the required skeleton, enabling the system to track impl, validate, learn, apply, and commit phases.

You can read and update fan-out registry and decision queue state without losing context by externalizing the data into LOOP-STATE.md, which sustains the workflow orchestration loop beyond a single session.

You need to externalize workaround signatures and batch pointers when starting orchestration cycles or when sub-skills read and write state, ensuring that cycle metadata and work signatures persist continuously.

This state management approach produces a summary line after every state update, allowing users to quickly query and understand the current loop position across all tracked build cycle items.