Illustrative example

By Specship · Last updated May 26, 2026 · Synthetic example, not a customer case study

CSV export ticket to PR example.

A billing team needs CSV export on an invoices table. This walkthrough shows how a bounded request becomes criteria, tests, implementation constraints, and PR evidence.

Direct answer: a reviewable AI coding agent output should contain the request, acceptance criteria, failing tests, scoped implementation notes, and PR evidence a human can verify.

Acceptance criteria

  • Export includes every filtered row, not only the current visible page.
  • Only billing admins can export invoice data.
  • Large exports stream without request timeout.
  • The PR includes a test for filtered export serialization.

Tests before code

  • Unit test for filter query serialization.
  • Integration test for streamed CSV response.
  • Permission test for a non-admin billing user.
  • Regression test for empty export state.

Implementation notes

  • Reuse the existing invoices table toolbar instead of adding a new pattern.
  • Route export through the server endpoint so permissions stay centralized.
  • Add a progress state for long-running export generation.

PR review evidence

  • Reviewer can verify filters in the test fixture.
  • PR body lists commands run and coverage delta.
  • Follow-up comments should update the same branch.