What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Ticket to PR

When to use

• You have a queue of well-defined tickets (bug fixes, small features) and not enough developer hours
• Routine development work eats most of your day and you want a pipeline: ticket → branch → code → draft PR
• Review comments keep bouncing back for the same classes of issues and you want an automated fix loop
• A team wants to try an AI coding pipeline without giving the agent merge rights
• You need consistent test and security checks on every change before human review

Workflow

Grab assigned tickets on a schedule and split them: clear enough to build, or needs clarification. Unclear tickets get a drafted reply for a human to send — the agent never starts coding on guesswork.

1. Pull and triage tickets (input: ticket tracker → output: actionable vs. unclear list)

Read the ticket, map the relevant repo files and related history. Assign risk: low (fix in one module), medium (new behavior), high (auth, payments, migrations). High-risk work gets human direction before any code is written.

1. Classify risk and route (input: actionable ticket → output: risk level + build plan)

Write the minimal change that satisfies the ticket, on a fresh branch. No refactors, no extras, no "while I'm here" improvements. Small diffs get reviewed and merged; big ones rot.

1. Implement the smallest change (input: ticket + context → output: working code on a new branch)

Run the test suite, lint, type checks, and build. Then review the diff independently — looking for regressions and missing tests, the way a teammate would. Failures bounce back to the implementer. Cap the loop (e.g. three rounds) so it can't spin forever on a design problem.

1. Test and self-review (input: code → output: passing checks or bounce-back)

Scan for leaked secrets, auth issues, and dependency problems — the things tests can't see. Flag anything suspicious in the PR notes rather than fixing it silently.

1. Security pass (input: passing code → output: security notes)

Open a draft pull request only. Never merge, never push to the main branch. The PR summarizes what changed, what was tested, the security notes, and the open questions a human should double-check.

1. Open a draft PR (input: reviewed code → output: draft PR)

Output spec

• One draft PR per ticket: ticket link, risk level, change summary, test results, security notes, open questions for the reviewer
• Triage log: which tickets were built, which were drafted-as-questions and why
• Draft-only is the hard line: the agent never merges and never pushes to the main branch
• Companion template.md skeleton — fill in the blanks and use it

Good vs. bad examples

• ❌ Bad triage: agent codes from a vague ticket and invents the missing requirements — ships s

Download the full skill pack (ZIP)