Do Subtasks
Executes exactly one approved subtask at a time, then returns a conventional commit message suggestion for human review and commit. Use when the user wants strict one-task-at-a-time implementation with manual commit control and explicit "next task" prompts.
Qa
Generates a practical QA checklist from the current conversation and goals. Use when the user asks for QA tasks, test checklists, validation steps, or simple step-by-step testing guidance.
To Subtasks
Converts the current conversation context into an implementation-ready subtask plan with atomic, dependency-ordered steps and optional test pairing. Use when a planning/discovery conversation (including grill-me sessions) is complete and the next step is to break decisions into actionable subtasks for sequential implementation.
To Pr
Implements agreed subtasks into a new branch, commits each subtask, pushes when complete, and opens a GitHub PR. Use when subtasks from to-subtasks should be implemented end-to-end as a pull request, or when the user mentions to-pr, PR automation, branch-to-PR workflow, or implementing all subtasks into a GitHub pull request.