use-case-reviewer

Audit use cases and generate a structured issues report by dimension.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/bflandev/threadline-ai --skill use-case-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-case-reviewer
Source: https://github.com/bflandev/threadline-ai/tree/main/skills/use-case-reviewer
Command: npx skills add https://github.com/bflandev/threadline-ai --skill use-case-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit existing use cases to surface ambiguities, gaps, and structural problems before they become code bugs or design gaps. This skill helps teams catch issues early and improve downstream artifacts.

Core Features & Use Cases

It outputs a structured review with specific, actionable issues, evaluated across six dimensions. The review includes the dimension, location, problem, and a suggested resolution, and is intended to guide authors rather than rewrite the use case.

Quick Start

Provide a use-case document to the assistant and request a structured review.

Frequently Asked Questions about use-case-reviewer

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

FAQPage Schema
How do I review a use case for completeness and ambiguities before development?

Reviewing a use case for completeness involves auditing its structure to surface ambiguities, gaps, and structural problems before development. This process evaluates the document across six dimensions to produce a structured issues report with specific locations and resolutions.

What is the best way to audit requirements for gaps prior to code generation?

Auditing requirements for gaps prior to code generation requires analyzing the use case to identify missing elements and structural flaws. This skill outputs an actionable issues report detailing each problem by dimension, location, and recommended resolution to guide authors.

How do I validate use cases to catch structural problems before designing architecture?

Validating use cases to catch structural problems before designing architecture requires a targeted review of the existing document. The audit identifies ambiguities and gaps early, providing a structured report that lists each problem by dimension and suggests specific resolutions.

Does this use case audit provide actionable resolutions or does it rewrite the document?

The use case audit provides actionable resolutions rather than rewriting the document. It outputs a structured issues report intended to guide authors, detailing each identified gap, ambiguity, or structural problem by dimension, location, and recommended resolution.

When do I need to perform a use case quality audit?

You need to perform a use case quality audit when validating use cases prior to creating downstream artifacts such as code, tests, or architecture. This early audit catches ambiguities and gaps before they become code bugs or design gaps, improving overall output.