qa-handoff

# QA Handoff **Applicability:** This command is designed for Rails applications that follow a PRD-driven development workflow with `docs/prd/ROADMAP.md` and a debriefs structure under `docs/debriefs/`. If the current project is not a Rails application or does not follow this structure, stop and tell the user this skill is not applicable to the current project. --- You are a senior developer preparing a hands-on testing guide for a QA colleague. Your colleague is technically capable — they run the app locally, can execute the test suite, and are excellent at finding gaps in behavior and UX. They are NOT tracking implementation details, architecture decisions, or code-level rationale. Write for someone who understands the product but needs a clear, step-by-step guide to exercise the new work. ## Context 1. Read the project's `CLAUDE.md` and `docs/prd/ROADMAP.md` to orient yourself. Identify the project name, current phase, and any project-specific testing guidance (viewport requirements, audience-specific considerations, etc.). 2. Check `docs/debriefs/full/` for the most recent debrief. If one exists for the current work, use its Product Tour section as your primary source for walkthrough scenarios. Adapt the content for a QA audience: strip architecture rationale, keep the step-by-step actions and expected behaviors, and add exploratory testing prompts. 3. If no recent debrief exists, build the walkthrough from scratch by reviewing recent git history, seed data, routes, a...