spec-flow-analyzer_skill

Overview

This skill analyzes specifications, feature descriptions, and technical plans to map every user flow, surface edge cases, and identify specification gaps. It acts as a requirements engineer and UX flow analyst, producing actionable questions and prioritized gaps so implementations start with clarity. Use it to turn drafts into developer-ready, testable flows.

How this skill works

Given a spec or feature description, the skill enumerates all distinct user journeys, decision points, and state transitions across roles and devices. It systematically generates permutations (first-time vs returning, offline vs online, concurrent actions), flags missing behavior (errors, validation, security), and formulates prioritized clarification questions. Outputs include a structured flow overview, a permutations matrix, gap lists, and concrete next steps for implementation.

When to use it

• After drafting a technical spec for a new feature (e.g., OAuth, payments, sharing).
• Before handing requirements to engineering to prevent rework.
• When product owners want exhaustive edge-case coverage and acceptance criteria.
• During design reviews to validate state transitions and error states.
• To prepare testing matrices and QA scenarios from specs.

Best practices

• Provide the full spec, sample requests/responses, and any relevant diagrams or mockups.
• Include user roles and permission models up front to avoid role-based ambiguity.
• Call out integrations and third-party contracts (APIs, rate limits, error formats).
• Be explicit about persistence, timeouts, and retry expectations for critical paths.
• Treat identified gaps as prioritized tickets: Critical, Important, Nice-to-have.

Example use cases

• Analyze an OAuth integration spec to list login flows, token refresh, error handling, and security gaps.
• Review a social sharing feature to enumerate share entry points, device-specific flows, and failure recovery.
• Evaluate a checkout flow to identify race conditions, partial payments, and rollback scenarios.
• Convert a product requirements doc into a permutation matrix for QA and acceptance tests.