spec-flow-analyzer

Name: spec-flow-analyzer
Availability: InStock
Author: ybbms

Analyze product specifications to identify incomplete user flows and edge cases.

1|Updated Apr 4, 2026

Search Tags:#requirements validation #gap detection #spec analysis #pre-development review #user flow mapping #edge case identification

Ready to run

npx skills add https://github.com/ybbms777/compound-engineering --skill spec-flow-analyzer-ybbms777

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-flow-analyzer
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-spec-flow-analyzer
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill spec-flow-analyzer-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates costly rework caused by incomplete specifications, ambiguous requirements, and unhandled edge cases that are only discovered late in the development process.

Core Features & Use Cases

Codebase-Grounded Analysis: References existing patterns and conventions in your codebase to ensure feedback is relevant, not generic.
End-to-End Flow Mapping: Maps all user journeys from entry point to terminal state, including decision branches and happy paths.
Gap Identification & Prioritization: Surfaces missing unhappy paths, state transitions, permission boundaries, and integration seams, sorted by severity.
Use Case: When reviewing a new AI-powered comment summary feature spec, it flags missing flows like rate limit handling for the AI API and permission checks for different user roles before any code is written.

Quick Start

Use the spec-flow-analyzer skill to review the attached product review summary feature spec and identify all missing user flows and edge cases.

Frequently Asked Questions about spec-flow-analyzer

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

FAQPage Schema

How do I identify missing user flows and edge cases in product specifications?▼

Spec analysis identifies missing user flows and edge cases by mapping end-to-end user journeys, decision branches, and error states from product specifications, surfacing prioritized gaps before implementation begins.

What is pre-development spec review and why is it needed?▼

Pre-development spec review is the process of analyzing feature descriptions and technical plans to catch incomplete requirements and unhandled edge cases early, eliminating costly rework caused by ambiguous specifications discovered late in development.

How do I check spec requirements against existing codebase patterns?▼

You check spec requirements against existing codebase patterns by analyzing technical plans while referencing current conventions and integration points, ensuring gap detection feedback remains relevant and actionable rather than generic.

Does spec gap detection work for permission boundaries and API rate limits?▼

Spec gap detection works for permission boundaries and API rate limits by evaluating entry points and integration seams within user flows, flagging missing error states and unaddressed edge cases sorted by severity.

Can I use spec analysis tools for AI-powered feature integration plans?▼

You can use spec analysis for AI-powered feature integration plans to review feature descriptions, identifying missing flows like API rate limit handling and role-based permission checks before coding starts.