flow-gap-analyst

Identify gaps, edge cases, and questions in feature specs.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/raydocs/antiflowskills --skill flow-gap-analyst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-gap-analyst
Source: https://github.com/raydocs/antiflowskills/tree/main/.factory/skills/flow-gap-analyst
Command: npx skills add https://github.com/raydocs/antiflowskills --skill flow-gap-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gap analysis identifies missing information, ambiguities, and risks in feature specs before coding starts.

Core Features & Use Cases

  • Surface gaps and edge cases from briefs and findings.
  • Generate concrete questions, owners, and follow-up items to resolve ambiguities.
  • Use Case: At project kickoff, analyze a spec to prepare a complete task list and acceptance criteria.

Quick Start

Run a gap analysis on the provided feature spec to surface ambiguities and missing requirements before implementation.

Frequently Asked Questions about flow-gap-analyst

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

FAQPage Schema
How do I identify gaps and edge cases in a feature spec before coding?▼

Gap analysis identifies missing information and ambiguities in feature specs by mapping flows, states, and dependencies to surface risks and generate concrete follow-up items before coding starts.

What is feature spec gap analysis and when do I need it?▼

Feature spec gap analysis is the process of finding missing requirements and edge cases. You need it at project kickoff to prepare a complete task list, assign owners, and define acceptance criteria.

How do I surface ambiguities and missing requirements from project briefs?▼

To surface ambiguities from briefs, analyze the provided feature spec to map dependencies and states, which generates concrete questions and actionable follow-up steps to resolve the missing requirements.

Can I use gap analysis on findings from repository and documentation scouting?▼

Yes, gap analysis can be applied to findings from repo-scout, practice-scout, and docs-scout to map flows and surface ambiguities, ensuring complete requirements before the implementation phase.

What is the best way to assign owners and track risks for feature ambiguities?▼

The best way to track risks is to run a gap analysis on the spec to document concrete owner assignments, identify risks, and generate actionable follow-up items that guide the implementation phase.