Identify the owner
Owner role · Participant
Evidence: me is used only when the request concerns the authenticated user.
Command-line workflows / Sprint participants
CLI walkthroughFind the current and next sprint in context
Read an owner’s current and next sprint context without inferring lifecycle state from calendar dates.
A sprint date does not prove a lifecycle transition. Read the requested owner’s actual current and next context before choosing preparation or carry-over work.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Work through the command boundary
Source-backed CLI examplesIllustrative case: an engineer asks what they should prepare next, but a calendar week alone does not identify the active sprint.
teamboost sprints context --owner me --org ORGANIZATION_ID --environment production --json --no-inputIllustrative commands, not executed here. Replace ORGANIZATION_ID, example task keys and UUID placeholders with verified values. Read help in your installed version.
Read sprint context
Owner role · CLI user
Evidence: Current/next sprint evidence is returned within the intended organization.
Choose the next action
Owner role · Sprint owner
Evidence: The plan uses actual lifecycle status rather than an assumed date transition.
Decision to make: Use owner-scoped sprint context and verify the returned lifecycle state before planning the next action.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
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.
Put the outline to work
- Confirm whether the question concerns the authenticated user or another named owner.
- Read scoped sprint context and retain the actual lifecycle states and returned sprint references.
- Prepare only the next outcome supported by those states; report an absent current or next context rather than inventing a sprint.
From a useful outline to team work
Explore TeamBoostAI for your team
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 the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Questions about this workflow
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.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.