State saved facts
Owner role · Lead
Evidence: The brief cites the verified current task and reported behavior.
Agents and MCP / Engineering leads
Drafting workbenchWrite an agent context brief with evidence boundaries
Prepare a task-grounded brief that separates saved facts, hypotheses, missing information and the next authorized action.
An investigation brief should distinguish reported facts, possible explanations and missing acceptance evidence before an agent starts changing code.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Prepare a brief for human review
Drafting workbenchIllustrative case: an agent must investigate a reported export failure, but the reproduction and acceptance owner are incomplete.
Identify missing evidence
Owner role · Agent
Evidence: Reproduction gaps and unknown acceptance conditions are named explicitly.
Bound the next action
Owner role · User
Evidence: The request distinguishes investigation from code changes or product writes.
Decision to make: Ask for a bounded investigation that fills the evidence gaps before proposing implementation.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
Saved report: filtered export omits one category. Unknown: exact filter values and the person accepting the corrected result. Hypothesis: inspect category eligibility. Authorized next step: investigate and report; implementation and product writes require a separately agreed scope.
Put the outline to work
- Read the current export-failure task and retain the reported output and affected scope as saved facts.
- List the missing reproduction steps and acceptance owner; label suspected export boundaries as hypotheses.
- Request a bounded investigation with findings and clarification questions, then agree a correction scope only after evidence is available.
From a useful outline to team work
Explore TeamBoostAI for your team
Use this manual outline alongside scoped TeamBoost task or people discovery. Confirm the authenticated workspace and requested action; discovery does not authorize a product write. 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
What should a hypothesis look like?
A possible explanation tied to code or behavior, clearly labelled as unproven.
Can the agent fill missing acceptance conditions?
It can propose questions, but the responsible owner should agree the actual boundary.
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.