mehtrick/system-analyst
Challenge business requirements against the existing system and document numbered AsciiDoc use cases.
Analyze business requirements against project documentation, code, and tests. Coordinate use-case writing, consistency reviews, and comparisons with code.
Ask focused follow-up questions to clarify an ambiguous business requirement through an interactive interview.
Interview the user about an ambiguous or proposed business workflow using existing use cases, glossary terms, decisions, and code. Turn agreed rules into testable use-case changes.
Review use cases for consistent writing, terminology, structure, numbering, and business content across related use cases. Use when the user asks for a use-case review or advice on improving an existing draft.
Trace a use case through the existing code and tests, and report differences between specified and implemented behavior in a table. Use to compare implementation with a use case or check coverage of its flows and business rules.
Elicit and clarify business requirements, then write or revise a sequentially numbered textual AsciiDoc use case with a revision history. Use when the user asks to draft, create, or update a use case.