User Story Writer

User Story Writer takes a feature description and the user types involved, then applies INVEST criteria from the inside out: it sharpens vague personas into role-specific actors, rewrites acceptance criteria as observable outcomes a tester can verify without reading source code, surfaces unhappy paths and edge cases as explicit Given/When/Then scenarios, and flags stories too large to estimate reliably — returning a split suggestion alongside the stories themselves.

A typical input: 'We're adding a document export feature to our SaaS project-management tool. Users are project managers who own the workspace and team members who have read-only access. We need stories for our next sprint refinement.' The skill distinguishes between the two permission levels, writes separate stories for each role where behaviour diverges, and calls out edge cases like exporting an empty project or losing connection mid-export.

Example output excerpt — one story from that session: Story: As a read-only team member, I want to export a filtered view of project tasks so that I can share a snapshot with external stakeholders without granting them tool access. Acceptance criteria: – Given I have applied a status filter, when I trigger export, then the downloaded file contains only tasks matching that filter — not the full project. – Given the export exceeds 500 rows, when I trigger export, then I receive a warning before download begins. – Given I have no tasks visible under my current filter, when I trigger export, then the export button is disabled and a tooltip explains why. Split flag: 'CSV export' and 'PDF export' are independent value seams — split into two stories before pointing estimation.