Requirement Generation
Intelligent Requirements can generate requirements from an initial scope description, business goal, problem to solve, or supporting documentation. The AI uses this input together with the selected knowledge bases to create a first structured version of the backlog.
The level and naming of generated items depend on the selected provider. In Jira, this can include initiatives, epics, stories, and subtasks. In providers such as BusinessMap, names and structures can vary, but the goal remains the same: turn context into organized work items.
When to use
- Use generation when a team needs a first backlog draft from project context.
- Use it when requirements need to reflect documents or knowledge bases already prepared for the project.
- Use it to expand an existing set of generated items as the demand evolves.
- Use it before review, refinement, saving, or publication.
Before you start
- Confirm the active organization and project.
- Open the workspace that should contain the generated requirements.
- Select the knowledge bases that should guide generation.
- Confirm the provider model that defines the backlog structure.
- Prepare the scope, goal, problem, or supporting documentation.
Step by step: generate requirements
- Open the workspace for the initiative.
- Confirm the selected project, knowledge bases, and provider.
- Add the initial scope, goal, problem, or supporting documentation.
- Start the generation flow.
- Review the generated backlog structure.
- Generate additional items when the demand needs to be expanded.
- Continue to review and refinement before saving or publishing items.
Expected result
You should have a structured set of generated requirements that can be reviewed, edited, saved to a knowledge base, or published to the selected provider.