hugoduncan A good feature triage will answer the following:
What is the request's intent? This is important because it captures what the requester is trying to achieve and provides the top-level orientation for the analysis.
What is the problem statement? An explicit problem statement clarifies what gap, pain, or missing capability the request is trying to address.
What is the scope? This prevents overreach during triage. It should identify what belongs inside the requested feature surface and what adjacent ideas are out of scope for this request.
What are the acceptance criteria? This should make clear what outcomes would demonstrate that the request has been satisfied from the user's point of view.
What closely related functionality already exists? Add a terse summary at the end of the triage that identifies nearby existing behaviour, features, or capabilities that overlap with or contextualize the request. This summary should stay brief and informational. It should not turn into implementation planning.
The triage should stay grounded in the issue as written. It should not invent implementation details, code changes, or delivery plans.
The level of detail should reflect the size and clarity of the request.