# Preview a project boundary before creating it

Illustrative planning brief; no automatic product import.

Illustrative case: a team proposes “Reporting Improvements,” but the actual agreed outcome is a bounded timezone clarification.

## Decision

Confirm whether the work needs a separate project or belongs in an existing one before previewing creation.

## Owned work

- Check existing context
  - Owner role: Organizer
  - Acceptance evidence: Discovery shows whether a suitable project already exists.
- Bound the proposed project
  - Owner role: Sponsor
  - Acceptance evidence: The proposed title and description express an agreed outcome and exclusions.
- Review the creation preview
  - Owner role: CLI user
  - Acceptance evidence: The preview identifies the new container proposal without reporting it as saved.

## Workflow

1. Compare the proposed timezone correction with existing reporting project outcomes and ownership.
2. Draft a separate project only if its outcome and exclusions cannot be represented clearly in the existing container.
3. Review the installed creation interface and its preview before any authorized apply; report the proposal as unsaved until readback confirms it.

## Judgment

Creating a container does not establish a delivery commitment or migrate existing tasks.


## Filled illustrative planning example

Synthetic proposal: clarify the timezone displayed on weekly reports. Existing reporting project already has the responsible owner and review path, so the work remains there. A new Reporting Improvements container is not created merely to hold the correction.


## Before / after

Before: Create a broad new project immediately because a task request sounds important.

After: Resolve existing context, agree a bounded outcome and preview the proposed container.


## Workflow questions

### Does a preview save the project?

No. The source CLI requires --apply for the write.

### Should every task need its own project?

Use the smallest structure that clarifies ownership and scope; a new container should solve a real coordination need.

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