# Refine a vague task before implementation

Illustrative planning brief; no automatic product import.

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

## Decision

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

## Owned work

- Recover the underlying need
  - Owner role: Planning owner
  - Acceptance evidence: The brief states that readers need to identify unresolved decisions.
- Draft a bounded revision
  - Owner role: Task author
  - Acceptance evidence: The proposal limits work to a pending-decision section with an agreed example.
- Verify assumptions
  - Owner role: Stakeholder
  - Acceptance evidence: The stakeholder confirms the boundary and names the acceptance reviewer.

## Workflow

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

## Judgment

An AI-enhanced description may sound precise while introducing unsupported requirements. Review added detail explicitly.


## Illustrative refined task proposal

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.


## Workflow questions

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

## Product connection

Resolve the outcome and exclusions before asking for AI assistance with a clearer TeamBoostAI task description.

Confirm account availability before adopting this manual outline.