Skip to main content

Knowledge Bases

Intelligent Requirements uses Lens knowledge bases as context sources for AI generation. These KBs store documents and information such as scopes, meeting notes, specifications, business rules, technical files, and other materials that help the AI generate requirements aligned with the project.

Knowledge bases are organized by project. When a user creates or opens a workspace for a project, the selected KBs should belong to that same context.

The reverse path also exists: generated requirements can be saved back to a KB, individually, in batches, or automatically when publishing to the provider. Over time, the project knowledge base contains both the original context and the artifacts produced from it, strengthening the material used by AI in future flows.

When to use​

  • Provide reliable project context to requirement generation.
  • Keep generated requirements aligned with existing documents and rules.
  • Keep approved requirements as part of the project knowledge.
  • Automatically store in the KB the items created in the provider.

Before you start​

  • Prepare the documents or information that should guide the AI.
  • Confirm that the knowledge bases are available in Lens for the selected project.
  • Decide whether generated requirements should be saved back to a KB and whether that should happen automatically on publish.

Step by step: use KBs as context​

  1. Open or create the workspace for the selected project.
  2. Review the knowledge bases associated with that project.
  3. Select the KBs that should support generation.
  4. Generate or refine requirements using the selected context.

Step by step: save requirements to the KB​

  1. Review the generated requirements in the workspace.
  2. Select one item, some items, or all generated items.
  3. Choose the destination knowledge base and save.
  4. View or remove saved items directly from each card when needed.
  5. Enable automatic saving in the workspace when items created in the provider should also be saved to the KB.

Expected result​

The AI should use the selected KBs as project context, producing requirements that are more specific and easier for the team to review. The knowledge base should also accumulate the approved requirements the team decided to keep, saved manually or automatically.

See also​