Resolve the constraints
Owner role · Author
Evidence: The brief lists each requested relationship and status restriction.
Command-line workflows / Automation authors
Drafting workbenchReview a task filter document before automation
Prepare a supported JSON task filter while preserving the requester’s constraints and avoiding guessed body fields.
Treat a filter document as a contract to review, not a place to guess API fields. Preserve every requested constraint and make unsupported predicates visible.
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: a request combines creator and project scope. An agent suggests a body field copied from a different API.
Check the filter contract
Owner role · CLI user
Evidence: Each JSON predicate is supported by the installed task-filter interface.
Review the evidence
Owner role · Reviewer
Evidence: The answer explains any unsupported constraint and does not pretend the request was fully applied.
Decision to make: Use the packaged filtering contract and verified IDs; reject unsupported fields instead of silently dropping constraints.
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.
Synthetic review: creator is Morgan; project is the confirmed reporting project. Both constraints must survive the filter review. A property copied from a task-update body is rejected unless the installed filter contract documents it. This brief is not an executable JSON schema.
Review constraints without guessing fields
Inspect the installed filtering contract before assembling a body file.
Creator relationship
- Evidence needed
- Supported creator predicate and verified subject.
- If evidence is missing
- State the unsupported constraint rather than substituting ownership.
Project scope
- Evidence needed
- Verified project reference and supported predicate.
- If evidence is missing
- Resolve project ambiguity before the read.
Complete request
- Evidence needed
- Every requested constraint is either applied or explicitly unresolved.
- If evidence is missing
- Do not report a narrower query as a complete answer.
Put the outline to work
- Write the requested creator relationship and verified project scope as separate constraints.
- Match each constraint to the installed filtering documentation and valid references; reject write-body properties that are not read predicates.
- Review the complete document before the scoped read and report any unsupported constraint with an explicit alternative.
From a useful outline to team work
Explore TeamBoostAI for your team
This manual brief helps an authorized TeamBoost CLI user keep identity, query scope and review evidence explicit. Check the installed interface and account access before using a source-backed command. 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
Can the filter come from stdin?
The source supports --filters-file - for a JSON filter document.
What if a requested filter is unsupported?
State the gap and provide an explicit alternative; never silently omit it.
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.