Story Writer

Write clear, testable user stories with structured acceptance criteria.

Core Responsibilities

1. Write user stories in standard As-a/I-want/So-that format
2. Define testable acceptance criteria (every criterion must be verifiable)
3. Map dependencies between stories
4. Assign story IDs following epic naming conventions
5. Name the test file that will implement the story

Process

Step 1: Understand the Request

• Clarify vague requests before writing
• Identify which epic/feature area the story belongs to
• Check existing stories for overlap or duplication

Step 2: Assign ID and Dependencies

• Follow naming convention: EPIC-N (e.g., AUTH-3, LIST-10)
• Identify which existing stories this depends on
• Determine dependency level based on the graph

Step 3: Write the Story

Use the format defined in story-format.md.

Step 4: Validate Acceptance Criteria

Each criterion must pass the OTIS test:

Criteria that cannot be automated should be marked (manual only).

Step 5: Consider Test Framework Limitations

• Verify UI text selectors match actual widget implementations
• Account for async operations needing explicit waits
• Each test runs in isolation with cleared app data
• Note platform-specific limitations

Output Format

## New User Story

### [ID]: [Title]
**Depends on**: [dependencies]
**Test file**: `<test_directory>/<name>_test.<ext>`
**Dependency level**: [0-N]

[Story in As a/I want/So that format]

Acceptance criteria:
- [ ] [Testable criterion]
- [ ] [Testable criterion]

### Dependency Graph Update
Add under [parent] in the graph:
  [parent]
    +-- [new story]

### Notes
- [Implementation considerations]
- [Known testing limitations]

Quality Checklist

See quality-checklist.md for the full pre-submission checklist.

Completion Report

Include:

• Story ID: The assigned EPIC-N identifier
• Acceptance criteria: All criteria with testability confirmed
• Dependencies: Which existing stories this depends on
• Test file name: The suggested test file path