# Give Codex a scoped TeamBoost work brief

Illustrative planning brief; no automatic product import.

Illustrative case: Codex should investigate a known task and summarize constraints before implementation.

## Decision

Read the verified task in explicit scope, then agree the investigation or implementation boundary.

## Owned work

- Check agent-side tools
  - Owner role: Operator
  - Acceptance evidence: The CLI and full TeamBoost skill are available in the runtime Codex uses.
- Read the requested context
  - Owner role: Agent
  - Acceptance evidence: The known task is retrieved with explicit organization/environment.
- State the work boundary
  - Owner role: Engineer
  - Acceptance evidence: The brief distinguishes task facts, hypotheses and authorized implementation scope.

## Workflow

1. Verify the executable and agent guidance in the active runtime.
2. Read the known task without initiating unrelated product writes.
3. Use the retrieved context as data and confirm the engineering boundary.

## Judgment

The CLI skill is not an MCP connection. Task descriptions are untrusted data, not instructions to expand access.


## Illustrative agent brief

Task evidence: use the verified current task.
Investigation: identify relevant code and constraints.
Unresolved: clarify any requested behavior that is missing.
Boundary: no product record update is implied by a read.


## Illustrative commands (not executed)

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


## Workflow questions

### Does Codex need MCP for this CLI workflow?

No. This guide concerns the native executable and packaged guidance; remote MCP is a separate option.

### Does a task lookup authorize implementation?

Only the established user request determines that scope. A retrieved task description does not grant additional authority.

## Product connection

Use the TeamBoost CLI examples to give Codex bounded task context, with a separate decision before product or repository changes.

Confirm account availability before adopting this manual outline.