Deliver the supplied work through a verified merge.
Explicitly invoking /factory authorizes merging only the supplied work after
all gates pass. Automatic skill selection does not grant merge authority; leave
the PR open unless the user explicitly authorizes merging. Deployment and release
publication require separate authority.
Read required skills directly from their SKILL.md files as instructions for this workflow. Do not invoke them through a skill command that the client blocks.
Process
- Read the source and repository instructions. The spec is the ticket; reuse it rather than creating separate product and technical specs.
- Follow
/task-to-pr, including tests, fresh independent review, CI, and the full repair loop. Pass the scoped merge authority when it exists. Keep the same quality standard. - Use its merge gates. If a required approval, decision, or check is unavailable, report the blocker and leave the PR open. Never bypass a gate to finish unattended work.
- Confirm the merge on GitHub and update the original issue when one exists. Follow
/task-to-prworktree cleanup rules.
Return
Report the merged PR and proof, or the open PR and exact merge blocker.