> For the complete documentation index, see [llms.txt](https://docs.kaana.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaana.com/product/managing-projects/requirements-overview.md).

# Requirements Overview

Requirements track business needs and how your project addresses them.

## What are Requirements?

Requirements represent:

* Business needs and objectives
* Functional requirements
* Technical specifications
* Compliance needs
* User stories

## Viewing Requirements

{% stepper %}
{% step %}

### Requirements List

Navigate to All Requirements or view them within a project:

* Open a project
* Go to the **Requirements** tab
  {% endstep %}

{% step %}

### Requirement Details

Each requirement shows:

* Title and description
* Status (Fit, Gap, Partial)
* Priority
* Linked test cases
* Linked issues
* Comments
  {% endstep %}
  {% endstepper %}

## Creating Requirements

### Add a Requirement

{% stepper %}
{% step %}

* Open a project
* Go to the **Requirements** tab
* Click **+ New Requirement**
* Fill in the details:
  * **Title** – Brief name
  * **Description** – Full requirement text
  * **Status** – Fit, Gap, or Partial
  * **Priority** – Importance level
  * **Category** – Type of requirement
* Click **Create**
  {% endstep %}
  {% endstepper %}

### Import from Excel

{% stepper %}
{% step %}

* Click **Import**
* Download the template
* Fill in your requirements
* Upload the completed file
* Review and confirm the import
  {% endstep %}
  {% endstepper %}

## Fit/Gap Analysis

Requirements can be marked with their implementation status:

| Status            | Meaning                                     |
| ----------------- | ------------------------------------------- |
| **Fit**           | The system meets this requirement           |
| **Gap**           | The system does not meet this requirement   |
| **Partial**       | The system partially meets this requirement |
| **Not Evaluated** | Not yet assessed                            |

## Updating Status

{% stepper %}
{% step %}

* Open the requirement
* Click the status dropdown
* Select the appropriate status
* Add notes explaining the assessment
  {% endstep %}
  {% endstepper %}

## Linking Requirements

### Link to Issues

{% stepper %}
{% step %}
When a gap is identified:

* Open the requirement
* Click **Link Issue**
* Create or select an issue
* Track issue resolution
  {% endstep %}
  {% endstepper %}

### Link to Tasks

{% stepper %}
{% step %}
Connect implementation tasks:

* Open the requirement
* Click **Link Task**
* Select related tasks
* Track completion
  {% endstep %}
  {% endstepper %}

## Requirement Comments

{% stepper %}
{% step %}
Discuss requirements with your team:

* Open the requirement
* Scroll to comments
* Add questions, clarifications, or updates
* @mention team members
  {% endstep %}
  {% endstepper %}

## Editing Requirements

{% stepper %}
{% step %}

* Open the requirement
* Click **Edit**
* Update any field
* Changes save automatically
  {% endstep %}
  {% endstepper %}

## Deleting Requirements

{% stepper %}
{% step %}

* Open the requirement
* Click the **...** menu
* Select **Delete**
* Confirm deletion

Note: This removes linked test cases and cannot be undone.
{% endstep %}
{% endstepper %}

## Requirements History

{% stepper %}
{% step %}

* Open the requirement
* Click **History**
* See all changes with timestamps
* Track who made what changes
  {% endstep %}
  {% endstepper %}

## Best Practices

### Writing Requirements

* Be specific and measurable
* Use consistent terminology
* Include acceptance criteria

### Fit/Gap Analysis

* Review all requirements systematically
* Document reasons for each status
* Update as the project progresses

### Test Coverage

* Create test cases for critical requirements
* Ensure gaps have tests for verification
* Execute tests regularly


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kaana.com/product/managing-projects/requirements-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.