Review and Refinement
After requirements are generated, users can review each item before sending it to a provider. Each card can be edited manually or adjusted with AI support.
During AI refinement, users can request changes in natural language, such as making the text more objective, adding acceptance criteria, detailing the scope, changing the focus to business or technology, or rewriting the description in another format. The AI suggests a new version, and the user decides whether to accept it, discard it, or continue editing.
When to use
- Use review before publishing generated items to a provider.
- Use manual editing when the team needs direct control over the text.
- Use AI refinement when an item needs clearer language, more detail, acceptance criteria, or a different format.
- Use refinement to align generated requirements with the team's writing standard.
Before you start
- Generate the initial requirements.
- Review the workspace context and selected knowledge bases.
- Confirm the target provider if the item will be published.
- Decide whether the item should also be saved to a KB.
Step by step: refine a requirement
- Open the generated requirement card.
- Review the title, description, hierarchy, and related details.
- Edit the content manually when the change is straightforward.
- Use AI refinement when the item needs a rewritten or enriched version.
- Describe the requested adjustment in natural language.
- Review the AI suggestion.
- Accept, discard, or continue editing the content.
- Repeat the process until the item is ready to save or publish.
Expected result
Each requirement should be reviewed and adjusted before it becomes part of the project knowledge base or the work management provider.