# Resolve a project name before task filtering

Illustrative planning brief; no automatic product import.

Illustrative case: two projects contain “Platform” in their title, but the task request concerns only one.

## Decision

Confirm the intended project candidate, then use its identifier for the task read.

## Owned work

- Search project titles
  - Owner role: Contributor
  - Acceptance evidence: The project list returns candidate names and references in the selected workspace.
- Resolve the ambiguity
  - Owner role: Requester
  - Acceptance evidence: The intended project is confirmed using its context, not list position.
- Carry scope into the read
  - Owner role: CLI user
  - Acceptance evidence: The task request retains the verified project ID and original filters.

## Workflow

1. Search Platform in the intended organization and retain each candidate name and stable reference.
2. Ask the requester to distinguish Platform API from Platform Operations using the project purpose; stop with an unresolved question if neither can be confirmed.
3. Use only the confirmed reference in the subsequent task read, keeping owner and status constraints unchanged.

## Judgment

A topic resembling a project title does not automatically authorize a project restriction.


## Filled illustrative planning example

Synthetic candidate A: Platform API, purpose contract delivery. Candidate B: Platform Operations, purpose service maintenance. Request: review the API contract backlog. Resolution: A, after requester confirmation. ORGANIZATION_ID in the displayed command is a placeholder to replace with verified context.


## Illustrative commands (not executed)

```text
teamboost projects list --search Platform --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### Does title search guarantee an exact match?

No. Inspect candidates and the documented title-search behavior.

### What if no project fits?

Report the missing match; do not silently substitute a similarly named project.

## Product connection

This manual brief helps an authorized TeamBoost CLI user keep identity, query scope and review evidence explicit. Check the installed interface and account access before using a source-backed command.

Confirm account availability before adopting this manual outline.


## Resolve the candidate before reading tasks

Illustrative project names demonstrate the choice; actual references come from scoped discovery.

### One confirmed project

Next action: Carry its verified identifier into the task read.

Evidence to revisit: The requester agrees the project purpose and scope.

### Several plausible projects

Next action: Ask which purpose matches the request; do not choose the first result.

Evidence to revisit: A confirmed candidate is still missing.

### No matching project

Next action: Report the missing match before proposing any new container.

Evidence to revisit: The requester decides whether the intended project exists.