Guides
How to review your issue pack
The first output is a draft. A good review turns that draft into something your team can trust, reject, or improve.
You should know how to move every item from draft to a clear review outcome.
Start with the source-backed items
Check SOPs, decision rules, gaps, conflicts, and macros against the source snippets and your team's real operating policy.
Use the review states deliberately
- Approve items that are usable or only need minor formatting later.
- Mark Needs Edit when the item is directionally useful but wrong, incomplete, or too vague.
- Reject items that are unsupported, misleading, duplicate, or not useful for the issue.
- Leave review notes for anything that future users may question.
What to check
- Does the SOP describe the actual trigger, required context, steps, exceptions, and response guidance?
- Are decision rules concrete enough for a teammate to apply?
- Do gaps and conflicts point to real cleanup work?
- Do macros match the policy and tone your team would use?
- Would approved items be used this week?
Before finalization
Resolve all Draft and Needs Edit items. Finalization includes approved items as usable output and excludes rejected items from the usable sections.