User Story Writer

'As a user, I want to manage my settings so that I can manage my settings' — the tautological user story is so common it has become a running joke, and it's only the most visible symptom. Acceptance criteria written as implementation instructions ('the button should be blue') tell engineers what to build, not what done looks like. This skill writes user stories where the job-to-be-done is specific enough to distinguish this feature from a hundred similar ones, the acceptance criteria are observable outcomes a tester can verify without reading the source code, and edge cases are surfaced as explicit scenarios rather than discovered in review. It also flags stories that are too large to estimate reliably and suggests the split. Describe the feature and the user; get back stories your team can estimate, build, and test without a follow-up conversation.