# Preview a useful task comment before posting

Illustrative planning brief; no automatic product import.

Illustrative case: a reviewer needs a concise note explaining which behavior passed and which decision still blocks acceptance.

## Decision

Preview the comment on the verified task; post only when the communication is authorized.

## Owned work

- Write the relevant update
  - Owner role: Collaborator
  - Acceptance evidence: The note distinguishes checked behavior from the pending decision.
- Inspect the target and preview
  - Owner role: CLI user
  - Acceptance evidence: The preview identifies the intended task and complete comment content.
- Verify after an authorized post
  - Owner role: Task owner
  - Acceptance evidence: Saved comment evidence is read back before reporting it as published.

## Workflow

1. Read the current task and any relevant comments.
2. Preview the Markdown input and inspect its exact target.
3. Treat publication as a separate action and reconcile uncertain outcomes before retrying.

## Judgment

CLI comments are task-only in the documented package. This page does not post comments or notify teammates.


## Illustrative comment

The checked behavior is ready for review. The date-boundary decision remains unresolved; please confirm the intended rule before acceptance. Link actual evidence in the real task.


## Illustrative commands (not executed)

```text
teamboost comments list --task TB-120 --org ORGANIZATION_ID --environment production --json --no-input
teamboost comments add --task TB-120 --content "Acceptance evidence ready; boundary decision still pending." --dry-run --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### Can I pipe a note from stdin?

The source supports --content-file - for UTF-8 Markdown input.

### Are comments editable through this package?

The packaged command map does not supply comment edit, reply or delete commands.

## Product connection

Review the bounded update before using the TeamBoost CLI comment workflow; the example does not post a comment.

Confirm account availability before adopting this manual outline.