Simplified state file management with consolidated FLOW.md (project) and ITEM-XXX.md (per-item) files
From flow-workflownpx claudepluginhub doubleslashse/claude-marketplace --plugin flow-workflowThis skill uses the workspace's default tool permissions.
templates.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
This skill provides techniques for managing workflow state through simplified, consolidated markdown files. The refactored structure uses just two file patterns: a single FLOW.md at project level and one ITEM-XXX.md per work item.
.flow/
├── FLOW.md # Project state + backlog (single file)
└── items/
├── ITEM-001.md # All state for work item 001
├── ITEM-002.md # All state for work item 002
└── ...
| File | Purpose | Contains |
|---|---|---|
FLOW.md | Project-level state | Vision, backlog, active item, capabilities cache |
ITEM-XXX.md | Per-item state | Phase, decisions, requirements, tasks, checkpoint |
The single project file contains:
See templates.md for the full FLOW.md template.
Each work item has a single consolidated file containing:
See templates.md for the full ITEM-XXX.md template.
Items progress through these phases:
| Phase | Description | Next Phase |
|---|---|---|
BACKLOG | Defined but not started | DISCUSS |
DISCUSS | Gathering requirements | PLAN |
PLAN | Creating task plan | EXECUTE |
EXECUTE | Implementing tasks | VERIFY |
VERIFY | Validating implementation | DONE |
DONE | Completed | (terminal) |
ON_HOLD | Paused intentionally | Previous |
BLOCKED | Waiting on dependency | Previous |
1. Create .flow/ directory if not exists
2. Create .flow/items/ directory
3. Scan for installed plugins
4. Detect project type from file patterns
5. Create FLOW.md with empty backlog + capabilities
/flow-workflow:start)1. Read FLOW.md to get next item number
2. Generate ITEM-XXX ID
3. Create .flow/items/ITEM-XXX.md with DISCUSS phase
4. Update FLOW.md backlog table
5. Set as active item in FLOW.md
1. Update checkpoint in current item's file
2. Update FLOW.md active item pointer
3. Load new item's context
1. Verify completion criteria for current phase
2. Update phase in ITEM-XXX.md
3. Create checkpoint snapshot
4. Initialize next phase section
1. Record current phase and task progress
2. Capture context budget percentage
3. List next recommended action
4. Add timestamp
1. Read FLOW.md to get active item
2. Read ITEM-XXX.md checkpoint section
3. Restore context from checkpoint
4. Identify next action
5. Continue workflow
Track context usage in FLOW.md and report:
## Context Monitor
- Current session: [X]% (limit: 50% before fresh agent)
- Last auto-spawn: [TIMESTAMP]
- Fresh agents this session: [N]
Before any phase transition, validate:
If legacy .flow/ structure detected (BACKLOG.md, ACTIVE.md, PROJECT.md, etc.):
.flow/legacy/State management integrates with:
/flow-workflow:goSee templates.md for full file templates.