task-to-pr
Installation
SKILL.md
Task to PR
Deliver each task as one focused pull request with proof. The spec is the ticket; accept a Markdown spec, GitHub issue, or decided task with acceptance checks. Do not create a second work definition.
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.
Prepare
- Read the source, repository instructions, relevant requirements and architecture, code, and tests. Reuse an existing branch, worktree, and pull request when continuing work.
- Confirm the outcome, scope, decisions, and checks are sufficient. If a consequential choice is missing, return to
/specor report the needed decision before implementing. Do not write specs for small, decided work. - Split larger specs with
/planwhen useful. Each task delivers one working result. Identify dependencies and start independent work together when useful.