What problem does it solve? Long-running agent workflows lose track of task state across sessions: features get marked passing without proof, multiple tasks run in progress at once, and blocked items lack actionable reasons. This Skill enforces a single durable source of truth for feature status so state stays auditable across sessions. ## Core Features & Use Cases - Schema enforcement: Every feature in feature_list.json must carry id, priority, area, title, user_visible_behavior, dependencies, status, verification, evidence, and notes. - Status discipline: Enforces exactly one in_progress feature (WIP=1), requires evidence citing a gate report path and metric line for passing, and requires the failing metric with value and threshold for blocked. - Markdown task support: Reads task rows and checklists in .specs/features//tasks.md, agent-os/specs//tasks.md, and per-ticket files with Status and Blocked by lines. - Use Case: Before an Execute phase, run the audit checklist to confirm all features have required fields, exactly one task is in progress, and every passing feature cites verifiable evidence. ## Quick Start Audit the current feature_list.json and Markdown task files, then report any WIP violations or passing features missing evidence.
