AI Cockpit Intelligent Requirements Overview
AI Cockpit Intelligent Requirements is the AI Cockpit application for creating, organizing, reviewing, and evolving requirements with AI support. It helps product, business, and technology teams turn ideas, documents, goals, and project context into backlog items ready for review, refinement, and publication to providers such as Jira and BusinessMap.
The application reduces manual effort in requirement writing, accelerates backlog detailing, and keeps generated items connected to the real context of each project.
What you see depends on the active organization, the selected project, configured knowledge bases, available providers, adapters, workflows, and the permissions assigned to your account.
When to use
- Use Intelligent Requirements to create a structured backlog from project context.
- Use it to refine generated requirements before publishing them to a provider.
- Use it to keep requirements connected to Lens knowledge bases.
- Use it to reuse Lens workflows for requirement creation and editing.
- Use it when a product, squad, client, or initiative needs its own requirements workspace.
Before you start
- Confirm the active organization.
- Create or select the project that groups the work context.
- Prepare the Lens knowledge bases that should provide context to the AI.
- Confirm that the provider and adapter needed for publication are available.
- Confirm which Lens workflows are configured for requirement generation and editing.
Step by step
- Open Intelligent Requirements from AI Cockpit.
- Confirm the active organization.
- Select or create the project that represents the product, squad, client, or initiative.
- Open or create a workspace for the work context.
- Select the Lens knowledge bases that should support generation.
- Choose the provider where backlog items can be published when needed.
- Generate, review, refine, save, or publish requirements according to the flow.
Understand the application
| Area | What it means |
|---|---|
| Workspaces | Organizes the project, knowledge bases, and provider used for a requirements flow. |
| Projects | Groups workspaces and knowledge bases by product, squad, client, or initiative. |
| Knowledge Bases | Uses Lens knowledge bases as context for generation and as a destination for generated requirements. |
| Requirement Generation | Creates structured backlog items from an initial description, business goal, problem, or supporting documentation. |
| Review and Refinement | Lets users edit generated cards manually or ask AI to improve them before publication. |
| Saving to the KB | Saves generated requirements back into a project knowledge base. |
| Integrations | Connects generated requirements to work management providers through adapters. |
| AI Flow Configuration | Uses Lens workflows to define how AI creates and edits requirements. |
Core building blocks
| Building block | Role in Intelligent Requirements |
|---|---|
| Workspace | Operational environment that combines one project, selected knowledge bases, and a provider. |
| Project | Organizational grouping for workspaces and knowledge bases. |
| Knowledge base | Lens context source used by AI and optional destination for generated requirements. |
| Requirement | Generated backlog item that can be reviewed, refined, saved, or published. |
| Provider | Work management destination such as Jira or BusinessMap. |
| Adapter | Organization-level connection that lets Intelligent Requirements communicate with a provider. |
| Workflow | Lens flow that defines how AI generates or edits requirements. |
Typical workflow
- Choose the project that represents the work context.
- Create or open a workspace.
- Select the knowledge bases that should guide the AI.
- Add the initial scope, goal, problem, or supporting documentation.
- Generate the requirements.
- Review and refine the generated cards.
- Save the selected items to a knowledge base when the project should keep the generated knowledge.
- Publish the approved items to the provider when the backlog is ready.
Expected result
After configuring the project, workspace, knowledge bases, provider, adapters, and workflows, you should be able to generate requirements that reflect the project context, review them with the team, and move approved backlog items to the right destination.