# Define technical links in a task-creation brief

Illustrative planning brief; no automatic product import.

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

## Decision

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

## Owned work

- Resolve the linked work
  - Owner role: Planner
  - Acceptance evidence: Each dependency refers to the intended task in the same verified context.
- State the dependency meaning
  - Owner role: Receiving owner
  - Acceptance evidence: The required deliverable and acceptance condition are explicit.
- Respect the write interface
  - Owner role: CLI author
  - Acceptance evidence: The creation brief follows prevTechDepIds/nextTechDepIds contract; update support is not assumed.

## Workflow

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

## Judgment

The packaged CLI documents these technical-link fields at creation and rejects them through tasks update.


## Filled illustrative planning example

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.


## Scope conditions

- 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


## Working artifact

- API contract predecessor / Reviewed response shape and error behavior. / UI owner confirms the contract is usable for integration.
- Proposed UI work / Verified predecessor reference in the reviewed creation proposal. / Creation-only contract is checked; existing-task edits are not assumed.


## Workflow questions

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

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