> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/scenarios/management/organizing-scenarios.md).

# Organizing Scenarios

Keep your scenario library navigable as it grows.

## Naming Convention

Use the format: **\[Purpose] - \[Scope] - \[Version/Date]**

Examples:

* "Engineering Reorg - Flatten Structure - v2"
* "Q2 Hiring Plan - Commercial NA - 2026-02-15"
* "Budget Cut 10% - Option A"
* "VP Engineering Succession - Candidate A"

**Purpose (required)** — What the scenario does: "Hiring Plan", "Budget Cut", "Reorganization", "Succession"

**Scope (recommended)** — Which team, department, or geography is affected

**Version or date (situational)** — Use v1/v2/v3 for iterations, Option A/B/C for alternatives, or a date for chronological tracking

Never leave a scenario named "Untitled Scenario" or "New Scenario."

## Versioning

Create a new version when stakeholder feedback requires significant revisions, you're testing a completely different approach, or you want to preserve the previous version for reference. For minor corrections (typos, small salary tweaks), just update the existing scenario.

**Version naming options:**

* Numbered: "Plan v1", "Plan v2"
* Lettered: "Plan - Option A", "Plan - Option B"
* Descriptive: "Plan - Conservative", "Plan - Aggressive"
* Date-based: "Plan - Feb 15"
* Combined: "Plan v2 - Aggressive - Feb 15"

## Delete

**Delete when** - it was a test or mistake with no meaningful content.

**Cleanup cadence:**

* **Weekly (5 min)** — Rename any "Untitled" scenarios; delete obvious test scenarios
* **Monthly (30 min)** — Standardize names; export change logs before archiving

## Comparison Sets

When evaluating multiple approaches, create a named set:

1. Create a base scenario: "Reorg - Base Analysis"
2. Duplicate and name each option: "Reorg - Option A - Flatten", "Reorg - Option B - Add Layer", "Reorg - Option C - Hybrid"
3. Tag all with a shared label (e.g., "Q2 Reorg Comparison")
4. Use Scenario Comparisons to evaluate side-by-side

## Ownership

Assign a clear owner to each scenario — they're responsible for naming, cleanup, and archiving. For shared scenarios, designate one "scenario lead" to coordinate edits and maintain consistency.

## Related Resources

* [Tags](/scenarios/management/tags.md)
* [Basic Actions](/scenarios/management/basic-actions.md)
* [Scenario Management Overview](/scenarios/management.md)


---

# 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.agentnoon.com/scenarios/management/organizing-scenarios.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.