Check existing context
Owner role · Organizer
Evidence: Discovery shows whether a suitable project already exists.
Command-line workflows / Project organizers
Decision deskPreview a project boundary before creating it
Review a proposed project’s scope and identity before a CLI creation workflow introduces a new container.
Choose a container because it clarifies a distinct outcome and ownership boundary. A narrow reporting correction may fit an existing project without another project hierarchy.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Decision desk
Decide before adding more work
Decision to make: Confirm whether the work needs a separate project or belongs in an existing one before previewing creation.
Illustrative case: a team proposes “Reporting Improvements,” but the actual agreed outcome is a bounded timezone clarification.
Bound the proposed project
Owner role · Sponsor
Evidence: The proposed title and description express an agreed outcome and exclusions.
Review the creation preview
Owner role · CLI user
Evidence: The preview identifies the new container proposal without reporting it as saved.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
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.
Compare the planning boundary
Before
Create a broad new project immediately because a task request sounds important.
After review
Resolve existing context, agree a bounded outcome and preview the proposed container.
Questions about this workflow
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.
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.
Put the outline to work
- Compare the proposed timezone correction with existing reporting project outcomes and ownership.
- Draft a separate project only if its outcome and exclusions cannot be represented clearly in the existing container.
- Review the installed creation interface and its preview before any authorized apply; report the proposal as unsaved until readback confirms it.
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
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.