# Task brief — replace the example with your project's facts

## Goal
Export rows matching the user's current dashboard filters.

## Scope
- Same filters, sorting and server-side permission rules as the visible list.
- Agreed columns, character encoding and date/time convention.
- Explicit behavior for empty results and large exports.

## Non-goals / protected boundaries
- No unrelated billing, authorization or dashboard changes.
- No production-data edits, secret-file access or deployment.

## Relevant context
- Implementation entry point:
- Shared schema / API contract:
- Downstream consumers:
- Existing tests:
- Known constraints:

## Acceptance evidence
- Authorized versus unauthorized export tested.
- Changed filters, empty results, non-ASCII text and CSV escaping tested.
- Spreadsheet-formula handling and data-volume limits reviewed.
- Actual project test command:
- Actual lint/type-check command:
- Current revision / worktree fingerprint:
- Example output inspected:

## Execution route and limits
- Direct work or delegation, and why:
- Files each worker may change:
- Independent work that may run in parallel:
- Retry / time / cost budget:
- Required reviewer and unresolved findings:

## Stop and ask
- Ambiguous authorization, contract changes, production effects or destructive steps.

## Completion record
- What actually ran and its exit status:
- What was not run:
- Changes since verification:
- Remaining risks / next action:

This is an original illustrative template accompanying Fouad Salkini's article.
It is not an executed test suite or a ready-made security guarantee.