Extract agreed actions
Owner role · Facilitator
Evidence: The outline distinguishes the two decisions from the uncommitted idea.
Agents and MCP / AI task planners
Drafting workbenchReview generated task scope, owner assumptions and distinct items before invoking TeamBoost’s task-creation tool.
Perform the proposal review before the write call; do not import CLI preview semantics into MCP.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Illustrative request: turn two agreed investigation actions into tasks, while a redesign idea remains unapproved.
Owner role · Facilitator
Evidence: The outline distinguishes the two decisions from the uncommitted idea.
Owner role · User
Evidence: Titles, scope, owner suggestions and dates are checked against the source request.
Owner role · Task lead
Evidence: The chosen creation action is explicit and saved outcomes will be checked afterward.
Decision to make: Confirm two bounded actions and reject the redesign commitment before using the source creation tool.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Invented planning text. Adapt it to your evidence and confirmed owners.
Agreed action A: inspect current timezone wording. Agreed action B: review an example weekly report with the stakeholder. Unapproved idea: redesign the entire reporting interface. Before a write: confirm scope and owners for A/B; omit the redesign.
From a useful outline to team work
The source-backed TeamBoost MCP create call is a direct write. Review and authorize the proposal before calling it; this page executes nothing. Confirm the workflows available in your account before adopting this outline.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
No. That flag belongs to the native CLI contract, not this tool call.
Only distinct agreed work items should become tasks; reject invented commitments and redundant splits.
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.