Tagged user-stories

Track epics, user stories and sprints in plain files without a project tool

Write QA acceptance criteria and a manual validation plan with pass or fail evidence

Check the work of a team run against its acceptance criteria

Gather requirements, define acceptance criteria and store the spec in memory

Write product requirements documents with user stories, specs and risk analysis

Write INVEST user stories and plan sprints with backlog and velocity tracking

Write user stories, acceptance criteria and sprint plans for your backlog

Write specs and acceptance criteria before code and derive tests from them

Split one epic into implementable stories with acceptance criteria

Write job stories with motivations, outcomes and acceptance criteria

Write user stories with acceptance criteria that follow INVEST and the 3 Cs

Turn feature ideas into specs, user stories, EARS requirements and acceptance criteria

Plan a phase as a vertical MVP slice built from user stories and SPIDR splits

Write product specs covering goals, scope, user stories, rollout and open questions

Turn a PRD into a testable design doc with behavior, data and acceptance criteria

Break epics into user stories with split patterns so each piece can be delivered

Write user stories in Mike Cohn format with Gherkin acceptance criteria

Map a workflow's activities and tasks into release slices for an MVP

Run a user story mapping workshop that outputs backbone activities and release slices

Split large stories and epics into smaller deliverable stories with proven patterns

Turn a PRD or RFC into concrete, buildable tasks with observable acceptance criteria

Check finished work against acceptance criteria with mechanical and semantic reviews

Give a general QA verdict on any artifact against its acceptance criteria

Turn task acceptance criteria into executable checks before delivering results

Write product feature specs with acceptance criteria, scope and risks

Plan an MVP phase from a user story and split it with SPIDR

Write or revise an MVP requirements document with scope and acceptance criteria

Exercise a running product against acceptance criteria and report what you saw

Write repeatable QA regression tests from tickets and acceptance criteria

Check acceptance criteria in a live browser or recording with PASS or FAIL results

Write PRDs with user stories that feed ralph-tui beads or prd.json

Write requirements, acceptance criteria and scope so a team knows when it is done

Break Notion product specs into implementation tasks with acceptance criteria

Write user stories and check for duplicates in Linear, GitHub Issues or Jira

Write SPEC documents with EARS requirements and acceptance criteria

Orchestrate SPEC workflows from plan to run to sync with acceptance criteria

Check a submitted task's code against its acceptance criteria and run tests

Map user stories into a backbone, walking skeleton and first release slice