What problem does it solve?
QA and drive workflows repeatedly re-derive how a user reaches each feature of an application, wasting verification runs on navigation discovery and known traps. This Skill builds and maintains a committed, user-point-of-view feature map at .flow/features/ so agents can drive features directly from documented routes.
Core Features & Use Cases
- Seed mode: Interviews the repo to detect surfaces (web, CLI, desktop), proves each route with one live drive, and writes an index plus one contract-shaped file per proven feature.
- Maintain mode: Audits the existing map against the live app with read-only source readers, live re-drives, and triage of findings into doc drift, harness gaps, or product bugs, shipping corrections as a single chore PR.
- Proof standards: Enforces doctor checks, action-plus-state evidence capture, real user paths only, and named verdicts (SEEDED, CLEAN, CHANGED, BLOCKED, REFUSED).
- Use Case: After shipping a new settings page, run the maintain mode to re-drive existing features, detect the unmapped surface, prove it live, and open a PR updating the feature map.
Quick Start
Ask the agent to run the flow-next features skill to seed the user-POV feature map for this repository.