Command-line workflows / Technical planners

Dependency map

Define technical links in a task-creation brief

Plan a task’s upstream and downstream technical links using verified references and the CLI creation contract.

A dependency needs both a correct task reference and a receiving condition. Distinguish source-supported creation fields from an assumed ability to edit an existing relationship.

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.

Unblock the receiving work

Illustrative dependency map

Illustrative case: a proposed UI task depends on an API contract task. The planner wants that relationship recorded at creation.

API contract predecessor

Required input: Reviewed response shape and error behavior.
Receiving condition: UI owner confirms the contract is usable for integration.

Proposed UI work

Required input: Verified predecessor reference in the reviewed creation proposal.
Receiving condition: Creation-only contract is checked; existing-task edits are not assumed.

Decision to make: Verify both task references and use only the source-supported creation fields in a reviewed proposal.

Resolve the linked work

Owner role · Planner

Evidence: Each dependency refers to the intended task in the same verified context.

State the dependency meaning

Owner role · Receiving owner

Evidence: The required deliverable and acceptance condition are explicit.

Respect the write interface

Owner role · CLI author

Evidence: The creation brief follows prevTechDepIds/nextTechDepIds contract; update support is not assumed.

Filled illustrative planning example

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

Synthetic link: UI integration waits for the reviewed API response contract, not simply a task marked done. The creation proposal references the verified predecessor. No dependency edit is assumed for an already saved task.

Review the supported scope

Authored interface and planning boundaries
Condition	Supported scope	Boundary to preserve
Target tasks	Readback confirms the intended references	Clarify ambiguous or missing work
Dependency contract	Receiving owner states the required deliverable	Avoid unexplained graph arrows
Creation interface	Supported body fields and preview evidence	Do not transfer fields into unsupported updates

Put the outline to work

Resolve the API-contract predecessor and proposed UI outcome in the same verified context.
Agree which contract evidence the UI owner needs before integration can start.
Inspect the creation-body contract for prevTechDepIds and nextTechDepIds; keep existing-task dependency edits outside this proposal unless separately supported.

Questions about this workflow

Are they command-line flags?

No. The inspected skill documents body-file fields, not flags with those names.

Can I use a title as the link?

Resolve a stable task reference first; a similar title is not a verified dependency target.

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