Refine a vague task before implementation

Rewrite a broad request into a bounded outcome while keeping unresolved assumptions visible for human review.

Treat clarity as a decision about scope, not a longer task description.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Prepare a brief for human review

Drafting workbench

Illustrative request: “make reports better.” A stakeholder explains that weekly readers cannot tell which tasks need a decision.

Recover the underlying need

Owner role · Planning owner

Evidence: The brief states that readers need to identify unresolved decisions.

Draft a bounded revision

Owner role · Task author

Evidence: The proposal limits work to a pending-decision section with an agreed example.

Verify assumptions

Owner role · Stakeholder

Evidence: The stakeholder confirms the boundary and names the acceptance reviewer.

Decision to make: Propose a report section for pending decisions; ask the stakeholder to approve that boundary before implementation.

Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.

Illustrative refined task proposal

Invented planning text. Adapt it to your evidence and confirmed owners.

Original request: make reports better.
Observed need: weekly readers cannot identify unresolved decisions.
Proposed outcome: a pending-decision section states the decision, its owner and the evidence needed.
Boundary: no redesign of the entire reporting interface is implied.
Acceptance question: can the reviewer identify the pending decision from an invented report example?
Unresolved: stakeholder approval of this scope and confirmation of the acceptance reviewer.

Put the outline to work

Ask what a reader or user should be able to do after the change.
Draft one observable outcome and list any assumptions added during rewriting.
Confirm scope with the requester before treating the revised text as an approved task.

From a useful outline to team work

Explore TeamBoostAI for your team

Resolve the outcome and exclusions before asking for AI assistance with a clearer TeamBoostAI task description. 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.

Questions about this workflow

When is a task still too vague?

When an owner cannot identify what to demonstrate or a reviewer cannot decide whether the result meets the request.

Should refinement include a solution?

Only if that solution is already agreed or necessary to bound the work. Otherwise keep it as a proposal, not an imposed implementation.

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.