To QA

Use this skill when the user runs /to-qa <issue>.

For Beads, the issue can be a parent with child work, an older cumulative issue, a discovered-from source issue, or a completed standalone issue with no parent-child structure. For structured .scratch, the issue is normally a parent with child files.

This skill reads completed implementation work from the configured issue tracker and writes a local QA session to QA To Do. It does not mutate tracker issues, pass/fail state, checklist items, evidence, archive state, or deletion state.

Required Inputs

• An explicit source issue reference from the user.
• The current repository path.
• A configured issue tracker workflow in docs/agents/issue-tracker.md, or explicit source issue references from the user.
• Completed implementation source work only.
• Access to the qa-to-do MCP server.

Supported Paths