# Read a known task from the terminal

Illustrative planning brief; no automatic product import.

Illustrative case: a colleague mentions TB-120 in a handoff. Its priority or description may have changed since that message.

## Decision

Read the scoped current task and compare its boundary with the handoff before starting.

## Owned work

- Resolve the task
  - Owner role: Engineer
  - Acceptance evidence: The known key returns the intended task in the selected organization.
- Inspect the current boundary
  - Owner role: Engineer
  - Acceptance evidence: The description and current status are checked against the handoff.
- Record the next question
  - Owner role: Delivery owner
  - Acceptance evidence: Any mismatch is clarified with the owner before implementation.

## Workflow

1. Establish the intended organization.
2. Read the known key and inspect current detail.
3. Link the verified task reference in your work brief; do not invent a task URL.

## Judgment

TB-120 is an example key. A successful lookup shows current data, not historical state at the time of a handoff.


## Illustrative lookup review

Reference: replace TB-120 with the known task.
Compare: current scope, status and owner context versus the handoff.
Decision: proceed only with the clarified current boundary.


## Illustrative commands (not executed)

```text
teamboost tasks get TB-120 --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### Can I use a UUID instead?

The source CLI accepts task UUIDs, numbers and TB-style keys for task detail.

### What if the task differs from the handoff?

Ask the responsible owner to reconcile scope before treating the old note as the current commitment.

## Product connection

The TeamBoost CLI task-read example supports checking a known reference; inspect the returned record before drawing a status conclusion.

Confirm account availability before adopting this manual outline.