coding-feature-queue

Feature readiness and revalidation states are tracked using a durable feature queue that records draft, ready, revalidate, blocked, and done states directly in repository status files. This approach prevents burying requirements or proof details within the queue itself.

Managing multi-feature engineering workflows requires a durable queue that maintains deterministic next-item selection. The queue separates feature states and preserves contract authority, ensuring reliable selection of the next ready item without overriding completion integrity.

Overlap detection works by flagging completed features for revalidation when new work touches their proof or implementation boundaries. This mechanism ensures that overlapping changes trigger a status transition back to revalidate, preserving completion integrity.

JSON validation and safe repository-relative paths are required to maintain feature queue discipline. These constraints ensure status transitions respect proof and evaluator outcomes, keeping contracts authoritative while preventing the queue from storing behavior or progress calculations.

You should avoid using a feature queue if your repository does not require multi-feature tracking or deterministic next-item selection. It is not designed to store behavior, proof receipts, or progress calculations, so simpler workflows without overlap detection needs may not benefit.