When an issue is labeled 'ready-for-implementation', read the design spec, plan the change, implement it following repository conventions, and open a pull request linked back to the issue.
- Identifier
create-pr-from-design- Version
- 1.0.1
- Steps
- 3
- Triggers
- 1
- implementation
- design
- pull-request
- automated
When it runs
issue.labeled- Settle delay
- 10s after the event
Only when all hold
- issue.addedLabel equals ready-for-implementation
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Issue Labeled ready-for-implementation
triggerThe event that starts the run.
- 02Clone Repository
git.cloneShallow-clones the repository at the right ref.
- 03Implement Design
agent.runOne agent works the task with its toolkit.
The agent
Design Implementer
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 60
- Tools
- 12
Filesystem · 5
read_fileRead File · readlist_dirList Directory · readwrite_fileWrite File · writeedit_fileEdit File · writecreate_directoryCreate Directory · write
Git provider · 4
create_branchCreate Branch · writecreate_or_update_fileCreate or Update File · writecreate_pull_requestCreate Pull Request · writecreate_issue_commentCreate Issue Comment · write
Code search · 1
code_searchCode Search · read
Terminal · 1
run_terminal_cmdRun Terminal Command · write
Status · 1
update_statusUpdate Status · write
Related playbooks
Generate Technical Design Proposal
Produces a technical design proposal from a ticket and its requirements.
Auto Root Cause Analysis
Investigates bug-labeled issues, traces the root cause in code, and posts the analysis with a fix.
Blocked Ticket Escalator
Tracks tickets that move to a blocked status and escalates with status updates at 3 days and to the board owner at 7 days.