Preserve each constraint
Owner role · Agent
Evidence: The requested status, owner and project remain explicit.
Make the operation boundary visible
Scope planning matrixIllustrative request: show blocked work owned by one named teammate in a specified project.
| Boundary | Evidence needed | Decision if missing |
|---|---|---|
| Requested set | Status/owner/project constraints preserved | Reject a silently broadened or narrowed answer |
| Name resolution | Exact or unique supported match | Ask about ambiguous candidates |
| Coverage | Tool limits and result boundary understood | Label partial or unavailable evidence |
Resolve names safely
Owner role · User
Evidence: Ambiguous candidates are clarified before a scoped filter is interpreted.
Assess coverage
Owner role · Reviewer
Evidence: Limits and unavailable conditions are stated rather than silently omitted.
Decision to make: Resolve names and apply supported attributes; clarify ambiguity rather than choosing a convenient match.
Filled illustrative decision
Invented planning text. Adapt it to your evidence and confirmed owners.
In the synthetic request, two workspace members share a similar display name. The operator resolves the intended member using approved membership evidence and then scopes the task query to the agreed project and state. A broad semantic match is kept as a candidate until identity is confirmed.
Questions about this workflow
Can an agent choose the first matching person?
No. Clarify ambiguous identity before attributing work.
What if a filter is unsupported?
State the limitation and discuss an explicit alternative instead of pretending the condition was applied.
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
- Write the requested attributes separately from topic wording.
- Use the structured tool contract and verified name resolution.
- Explain any unsupported constraint and coverage limit.
From a useful outline to team work
Explore TeamBoostAI for your team
Use the TeamBoost MCP exact-filter example for an attribute question, with semantic retrieval reserved for a separate meaning-based question. 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.