flow-completeness-auditor

Audit SaaS product interaction graphs for dead ends and missing states.

2|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/rakibulism/agent-skills-os --skill flow-completeness-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-completeness-auditor
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/flow-completeness-auditor
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill flow-completeness-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify that a product's user flows are fully wired, so buttons, menus, modals, forms, and routes do not lead to dead ends or missing states.

Core Features & Use Cases

  • Flow Inventory: Maps every interactive element and navigation path across screens.
  • Gap Detection: Flags missing destinations, unreachable states, incomplete modal behaviors, and inconsistent repeated patterns.
  • State Coverage: Checks for empty, loading, error, success, restricted, and zero-results states where they should exist.
  • Use Case: Use it before a launch to confirm that every visible action in a SaaS product leads somewhere defined and behaves consistently across screens.

Quick Start

Ask the skill to audit your product flow completeness using the available target and access method.

Frequently Asked Questions about flow-completeness-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find dead-end user flows and missing navigation states in a SaaS app?

You can audit a SaaS app for dead ends and missing modal states by providing screenshots, codebases, or Figma files to trace every interactive element and generate a severity-tagged gap report.

What is flow completeness auditing and when should I run it?

Flow completeness auditing is the process of inventorying every interactive element and verifying state coverage. Run it before launch to confirm all routes, forms, and modals behave consistently without dead ends.

Can I audit Figma files and codebases for missing UI states and unreachable routes?

Yes, you can audit Figma files and codebases to trace forward flows and check for unreachable screens, incomplete modal behaviors, and missing zero-results states to ensure full navigation path coverage.

What is the best way to check for missing empty, loading, and error states across SaaS screens?

The best way to check for missing empty, loading, and error states is to perform a state completeness audit that maps every route and modal, flagging inconsistent repeated patterns and UI coverage gaps with severity tags.

How do I trace navigation paths to detect unreachable screens and incomplete modal behaviors?

Trace navigation paths by inventorying all interactive elements and performing forward flow tracing to detect unreachable screens, incomplete modal behaviors, and inconsistent repeated patterns across the product.