Command-line workflows / Sprint planners

Decision ledger

Inspect canonical sprint task membership and order

Use the saved sprint task sequence to review membership and rank before proposing a planning change.

Project visibility, sprint membership and saved sprint rank answer different questions. Keep the authoritative membership read beside any current task enrichment.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Keep the reason with the decision

Illustrative decision record

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

Decision 01

Saved membership

Rationale and evidence: Returned task references establish which work belongs to the selected sprint.
Revisit condition: Revisit when the saved membership changes.

Decision 02

Saved rank

Rationale and evidence: Returned rank puts API contract before UI integration in the synthetic example.
Revisit condition: Revisit after an authorized ordering decision is saved.

Decision 03

Current detail

Rationale and evidence: Task status enrichment is current state, separate from sprint membership.
Revisit condition: Refresh current detail without rewriting the saved sequence.

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

Resolve the sprint

Owner role · Planner

Evidence: The intended sprint UUID is verified from scoped discovery.

Read canonical membership

Owner role · CLI user

Evidence: sprints tasks returns saved membership and rank evidence.

Separate enrichment

Owner role · Reviewer

Evidence: Any later task-detail reads are labelled current state, not historical sprint membership.

Filled illustrative planning example

Invented planning text. Adapt it to your evidence and confirmed owners.

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.

Put the outline to work

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

Questions about this workflow

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.

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.

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