# Prepare a bounded CLI task-creation proposal

Illustrative planning brief; no automatic product import.

Illustrative case: a planner wants a task to inspect confusing timezone labels, not an unbounded report redesign.

## Decision

Draft the investigation boundary and confirm a supported task type before constructing the preview command.

## Owned work

- Bound the task
  - Owner role: Author
  - Acceptance evidence: The brief names the wording investigation and excludes a full redesign.
- Check supported inputs
  - Owner role: CLI user
  - Acceptance evidence: Installed help establishes the required title/type and any optional fields.
- Review the creation preview
  - Owner role: Planning owner
  - Acceptance evidence: The preview is checked for invented owners, deadlines or unrelated scope.

## Workflow

1. Write the observable investigation outcome.
2. Consult tasks create help for the supported field contract.
3. Preview the proposed task only after its scope is agreed.

## Judgment

A downloaded brief does not create a task. Do not invent an enum value or transfer MCP fields into a CLI body.


## Illustrative creation input

Title proposal: Inspect timezone wording in weekly reports.
Outcome: document ambiguous labels and propose bounded wording.
Exclusion: complete report redesign.
Owner and due date: await explicit confirmation.
Task type: select from installed command help.


## Workflow questions

### Can a description contain Markdown?

The source CLI documents Markdown description separately from descriptionJson.

### Does task creation support an idempotency key?

The packaged skill does not supply a task-creation idempotency key; do not infer the sprint transition contract applies.

## Product connection

Prepare the proposed fields for the TeamBoost CLI creation workflow, then confirm the real owner and authorized write before application.

Confirm account availability before adopting this manual outline.