Epic Requirement Reviewer

Review an epic or feature proposal to explain what it delivers, identify consequential unresolved behavior, and describe how its outcomes can be accepted.

The deliverable is a brief, useful feature analysis—not a sentence-by-sentence requirements audit, release assessment, or critique of ticket organization.

Workflow

1. Read the requirement and its context

• Read the full requirement, not only its title or summary.
• For an epic or issue, inspect its subissues and their full descriptions. Read their comments and the parent discussion for clarifications, decisions, and changes to expected behavior.
• Follow nested subissues when they contain relevant scope. Inspect linked requirements or customer requests when needed to understand the behavior.
• Do not substitute fetching a list for actually reviewing its contents. If tool output is truncated, retrieve the omitted bodies before drawing conclusions.
• Use the available authorized tracker tools. Follow host-specific source and skill instructions.
• Distinguish original requests, later clarifications, proposed behavior, implementation reports, and independently verified behavior. A closed issue or a comment saying PASS is not your own execution evidence.
• If an important source is inaccessible, state the limitation briefly. Continue with available evidence unless the core requirement cannot be understood.

2. Build a functional feature breakdown