state-management

Track project backlog and workflow state in Markdown by consolidating context into a FLOW.md file and individual item records into ITEM-XXX.md files. This pattern replaces multiple tracking files with two human-readable patterns for easy auditing.

Resume interrupted work by using per-item checkpoint files. The state-management approach captures automatic checkpoints within ITEM-XXX.md files, enabling reliable resumption of multi-item workflows from the exact phase of interruption.

Yes, you can hand-edit project workflow state safely. State is stored entirely in plain Markdown formats like FLOW.md, ensuring human-readable state that supports easy manual editing, auditing, and direct review without breaking the structure.

Initialize a state-managed workflow by creating a single FLOW.md file for project context and backlog tracking, then generate individual ITEM-XXX.md files for each item. This supports initialization, item creation, and phase transitions across the workflow.

Yes, this Markdown workflow state approach tracks context usage. It includes context budget awareness features that monitor and report context usage across items, helping teams coordinate multi-item workflows within defined limits.

Use a single FLOW.md file when you need a minimal footprint for backlog tracking. This pattern replaces nine or more separate files, reducing maintenance overhead while providing checkpoint-based resume and per-item decision history.