# Find the current and next sprint in context

Illustrative planning brief; no automatic product import.

Illustrative case: an engineer asks what they should prepare next, but a calendar week alone does not identify the active sprint.

## Decision

Use owner-scoped sprint context and verify the returned lifecycle state before planning the next action.

## Owned work

- Identify the owner
  - Owner role: Participant
  - Acceptance evidence: me is used only when the request concerns the authenticated user.
- Read sprint context
  - Owner role: CLI user
  - Acceptance evidence: Current/next sprint evidence is returned within the intended organization.
- Choose the next action
  - Owner role: Sprint owner
  - Acceptance evidence: The plan uses actual lifecycle status rather than an assumed date transition.

## Workflow

1. Confirm whether the question concerns the authenticated user or another named owner.
2. Read scoped sprint context and retain the actual lifecycle states and returned sprint references.
3. Prepare only the next outcome supported by those states; report an absent current or next context rather than inventing a sprint.

## Judgment

An absent current sprint is not proof that the owner has no tasks. Lifecycle status and dates are different evidence.


## Filled illustrative planning example

Synthetic context: Sprint A is active; Sprint B is planned. Preparation may collect Sprint B candidates while Sprint A acceptance remains open. If no next reference is returned, the planning question stays unresolved. This example does not execute a transition.


## Illustrative commands (not executed)

```text
teamboost sprints context --owner me --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### Is owner optional?

The documented context command defaults to me; make the subject explicit when coordinating another owner.

### Can I filter sprints list by status?

The packaged command map does not advertise a status filter on sprints list.

## 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.