# Review a task filter document before automation

Illustrative planning brief; no automatic product import.

Illustrative case: a request combines creator and project scope. An agent suggests a body field copied from a different API.

## Decision

Use the packaged filtering contract and verified IDs; reject unsupported fields instead of silently dropping constraints.

## Owned work

- Resolve the constraints
  - Owner role: Author
  - Acceptance evidence: The brief lists each requested relationship and status restriction.
- Check the filter contract
  - Owner role: CLI user
  - Acceptance evidence: Each JSON predicate is supported by the installed task-filter interface.
- Review the evidence
  - Owner role: Reviewer
  - Acceptance evidence: The answer explains any unsupported constraint and does not pretend the request was fully applied.

## Workflow

1. Write the requested creator relationship and verified project scope as separate constraints.
2. Match each constraint to the installed filtering documentation and valid references; reject write-body properties that are not read predicates.
3. Review the complete document before the scoped read and report any unsupported constraint with an explicit alternative.

## Judgment

Do not copy an MCP argument, backend body field or advanced write property into a CLI filter without contract evidence.


## Filled illustrative planning example

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.


## Workflow questions

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

## Product connection

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 account availability before adopting this manual outline.


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