Real-User QA Planner

Plan QA the way the product will actually be judged: as journeys real people walk, not as test cases that accumulate. This skill owns the project's living QA docs — one canonical tree that survives every QA round — and plans the persona-driven sessions that qa-execution runs.

Two rules define everything here:

1. Living docs, not round artifacts. All durable QA knowledge lives in one committed tree (<qa-docs-path>, default docs/qa/). Rounds append to it; they never create parallel trees, never reset ids, never overwrite history.
2. Sessions, not cases. The atomic planning unit is the session charter (persona + journey + tour + time-box), derived from journey flowcharts. Coverage means "every planned journey was walked by a persona this cycle" — never "every persona has N test cases".

Required Reading Router

Match your task to the row. Read the listed files in full before producing the deliverable. They are not appendices — they are the contracts the deliverable must conform to. Inline content in this SKILL.md is a pointer, not a substitute.