foxctl-room-agile

To manage long-running agile workflows across multiple sessions, you need durable state orchestration that structures epic intake, milestone proposals, and story validations. This approach replaces ephemeral chat by maintaining cross-session state via persistent epic artifacts.

The best way to track milestone review verdicts and story validation evidence is through evidence-driven reviews. You record verdicts, write synthesis as durable milestone summaries, and attach proof via work-pack mirroring for later semantic retrieval.

To structure epic intake and promote proposals, you orchestrate a durable epic to milestone to story lifecycle. You intake, shape, and checkpoint an epic, then promote proposals into milestones and stories to define explicit execution scope.

Yes, running durable agile workflows requires a base room protocol. You must use room-level commands for lifecycle orchestration within an existing room, enforcing room protocol assumptions to properly maintain cross-session state.

Work-pack sync handles cross-session state by mirroring persistent epic artifacts. It maintains a delivery log and keeps local file mirrors in sync, ensuring high-signal artifacts are promoted into ContextWiki drafts for semantic retrieval.

You should not use ephemeral chat for agile project management when handling long-running objectives that span many sessions. If your work requires explicit acceptance criteria, proof evidence, and work-pack mirroring, you need durable state orchestration.