manual page/ Examples

Feature from ticket

sourceSource: suspec/docs/examples/feature-from-ticket.mdModified: 2026-08-19

example.txt

file

WEB-123

Add a "Download CSV" button to the report page.
It should export the currently filtered rows.

Spec

~/.agents/artifacts/reports-app/report-csv-spec.md:

example.md

file

---
type: spec
id: SPEC-report-csv
title: Report CSV export
status: ready
owner: reporting-team
sources:
  - WEB-123
---

# Report CSV export

## Intent

Users can export the rows currently visible in the report.

## Non-goals

- No scheduled exports.
- No export of hidden or unfiltered rows.

## Requirements

### AC-001 - Export visible rows
- When: a user exports the report
- Then: the report page MUST export the currently filtered rows as CSV
- Verify with: `npm run test:e2e -- report-csv-export`

## Affected areas

- `app/reports/`
- `test/e2e/`

suspec check ~/.agents/artifacts/reports-app/report-csv-spec.md

One requirement and one worker need no task. Splitting nothing still produces nothing.

Review

A non-implementer judges AC-001 on the native PR against:

example.txt

file

npm run test:e2e -- report-csv-export
1 passed

The checker confirms spec structure. The human accepts on the PR. The implementer cannot accept. No durable lesson emerged. Good. The code and test retain the value, so close the transient files.

Need a starting point? Install the skills