Set up a new API project in Postman in one go

**Objective:** Set up Postman for the new API `{project-name}`: a team workspace, an empty collection, and environments for the stages `{stages}` (default Development, Staging, Production).

**Step 1: Check what exists**

* `postman-get-workspaces` with `name` = `{project-name}`.
* `postman-get-collections` with `name` = `{project-name}`.
* `postman-get-environments` with `name.contains` = `{project-name}`.

Anything that already exists is reused, not recreated.

**Step 2: Plan**

Show a checklist: workspace `{project-name}` (type team, description `{description}` if given), collection `{project-name}` (same description), and one environment per stage named "`{project-name}` - <Stage>". Mark each as exists or will create.

**Step 3: Confirm, then create**

After a clear yes, create only the missing items, each once:

* `postman-add-workspace` with `name`, `type` = team and `description`.
* `postman-add-collection` with `name` and `description`.
* `postman-add-environment` with `name`, once per missing stage.

Stop at the first error and report what was and was not created.

**Step 4: Report**

List each item with its id. Explain what is still manual: the collection and environments are created empty and in the default workspace (these tools cannot place them into the new workspace or add variables), so the user should move them in Postman and add variables there. Offer the schedule-collection-monitor prompt once requests exist.

**Rules & Guidelines:**

* Never create a duplicate of something found in Step 1.
* Only the three add tools above may write. Do NOT call update, fork, merge, run or publish tools.

**Validation:**

* If `{project-name}` is empty, ask for it and stop.
* If `{stages}` lists more than five stages, confirm the list before creating.