# Review an agent task proposal before an MCP write

Illustrative planning brief; no automatic product import.

Illustrative request: turn two agreed investigation actions into tasks, while a redesign idea remains unapproved.

## Decision

Confirm two bounded actions and reject the redesign commitment before using the source creation tool.

## Owned work

- Extract agreed actions
  - Owner role: Facilitator
  - Acceptance evidence: The outline distinguishes the two decisions from the uncommitted idea.
- Review generated fields
  - Owner role: User
  - Acceptance evidence: Titles, scope, owner suggestions and dates are checked against the source request.
- Authorize the specific operation
  - Owner role: Task lead
  - Acceptance evidence: The chosen creation action is explicit and saved outcomes will be checked afterward.

## Workflow

1. Write the proposed actions in a manual brief first.
2. Resolve unsupported assumptions with the decision owner.
3. Invoke a creation tool only within the approved scope and inspect its returned outcome.

## Judgment

tb_create_task is a write tool. The source does not establish a CLI-style dry-run stage for its call.


## Illustrative pre-write proposal

Agreed action A: inspect current timezone wording.
Agreed action B: review an example weekly report with the stakeholder.
Unapproved idea: redesign the entire reporting interface.
Before a write: confirm scope and owners for A/B; omit the redesign.


## Workflow questions

### Does the MCP tool use --apply?

No. That flag belongs to the native CLI contract, not this tool call.

### Should one suggestion always become one task?

Only distinct agreed work items should become tasks; reject invented commitments and redundant splits.

## Product connection

The source-backed TeamBoost MCP create call is a direct write. Review and authorize the proposal before calling it; this page executes nothing.

Confirm account availability before adopting this manual outline.