# Build a task summary from structured CLI results

Illustrative planning brief; no automatic product import.

Illustrative case: a weekly summary needs counts by current status and a few decision requests, not every description and member detail.

## Decision

Use scoped aggregate/read evidence and disclose the observation window and unavailable fields.

## Owned work

- Choose the evidence
  - Owner role: Report author
  - Acceptance evidence: The report names its organization, requested filters and observation point.
- Select useful facts
  - Owner role: Analyst
  - Acceptance evidence: The summary includes status evidence and decisions without unnecessary private details.
- Label interpretation
  - Owner role: Reviewer
  - Acceptance evidence: Inferred risk is distinguished from a saved task fact.

## Workflow

1. Use JSON on structured commands.
2. Check success/error evidence before summarizing data.
3. Write a brief decision-oriented summary with explicit limits.

## Judgment

Missing fields may mean unavailable rather than zero or unassigned. Do not infer the cause of delay from status alone.


## Illustrative structured-report outline

Scope: one verified organization and the stated filters.
Observed: summarize supported current-status evidence.
Interpretation: explain any inferred risk separately.
Next decision: name the role that can resolve the pending condition.


## Workflow questions

### Should I paste raw JSON into a stakeholder update?

Usually no. Select the evidence the decision requires and omit unnecessary personal or task detail.

### Are aggregates historical snapshots?

Use the documented semantics; a current aggregate is not proof of a past sprint state.

## Product connection

The TeamBoost CLI JSON example supplies observed records for a report; the delivery-risk interpretation remains your review decision.

Confirm account availability before adopting this manual outline.