# Inspect canonical sprint task membership and order

Illustrative planning brief; no automatic product import.

Illustrative case: a planner sees a task in a project list and assumes it is the first item in an upcoming sprint.

## Decision

Read the sprint’s saved task membership and rank before discussing order or carry-over.

## Owned work

- Resolve the sprint
  - Owner role: Planner
  - Acceptance evidence: The intended sprint UUID is verified from scoped discovery.
- Read canonical membership
  - Owner role: CLI user
  - Acceptance evidence: sprints tasks returns saved membership and rank evidence.
- Separate enrichment
  - Owner role: Reviewer
  - Acceptance evidence: Any later task-detail reads are labelled current state, not historical sprint membership.

## Workflow

1. Resolve the requested sprint reference from scoped discovery.
2. Read its complete saved task membership and retain the returned rank values and page coverage.
3. Compare a proposed discussion order with that saved sequence; label current task detail separately and leave any write as a distinct proposal.

## Judgment

The source order command requires the complete current membership. This guide only prepares a read/review.


## Filled illustrative planning example

Synthetic membership: rank 1 API contract, rank 2 UI integration. The UI task also appears in the project list, which does not change its sprint rank. Current status enrichment is recorded in a separate column; no reorder is performed.


## Working artifact

- Saved membership / Returned task references establish which work belongs to the selected sprint. / Revisit when the saved membership changes.
- Saved rank / Returned rank puts API contract before UI integration in the synthetic example. / Revisit after an authorized ordering decision is saved.
- Current detail / Task status enrichment is current state, separate from sprint membership. / Refresh current detail without rewriting the saved sequence.


## Workflow questions

### Does tasks get show historical rank?

No. Current task detail can enrich a review but does not replace canonical sprint membership.

### Should a proposed order omit an inconvenient task?

No. Review the complete current membership and use the documented planning contract.

## Product connection

This manual brief helps an authorized TeamBoost CLI user keep identity, query scope and review evidence explicit. Check the installed interface and account access before using a source-backed command.

Confirm account availability before adopting this manual outline.