app-user-story-qa

把全量功能审计转为可执行的用户故事与测试追踪流程。

把‘把每个功能都测一遍’这种大工程拆成可执行的用户故事和追踪表：把每个功能锚定到代码，记录期望行为到统一表格，然后逐条跑用户旅程并分类故障。适用于需要全面审计产品功能、复现并修复 UX 或逻辑缺陷的情况。特别在于有一份唯一的 canonical tracker（比如表格）来保证每个故事可追溯、可复测，不会丢失上下文。

# App User Story QA

## Purpose

Use this skill to turn a broad "test every feature in this app" request into a controlled loop with one source of truth. Anchor every feature to code, track expected behavior in a canonical spreadsheet, run tests against each user story, and classify failures. Apply fixes only when the current request explicitly authorizes them.

## Route

Use `plan_first` for most runs. Switch to `clarify_first` only when the app boundary, writable checkout, production risk, or acceptance criteria are unclear enough that a wrong assumption would waste substantial work.

Before editing:

1. Run a repo state snapshot: current path, branch, latest remote, dirty files, open PRs