When a ticket is labeled 'tech-design', read it and any existing requirements, then post a technical design proposal covering approach, data model, API surface, risks, and alternatives considered.
- Identifier
generate-technical-design-proposal- Version
- 1.0.0
- Steps
- 2
- Triggers
- 1
- tickets
- design
- architecture
- automated
When it runs
ticket.labeled- Settle delay
- 5s after the event
Only when all hold
- ticket.addedLabel equals tech-design
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.
- 01Ticket Labeled tech-design
triggerThe event that starts the run.
- 02Generate Tech Design
agent.runOne agent works the task with its toolkit.
The agent
Technical Design Author
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 25
- Tools
- 3
Tickets · 3
read_ticketRead Ticket · readread_ticket_commentsRead Ticket Comments · readadd_comment_to_ticketAdd Comment to Ticket · write
Related playbooks
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.
Break Down Ticket
Decomposes a labeled ticket into a concrete set of proposed sub-tasks.
Create PR from Design
Turns a spec-bearing issue labeled ready-for-implementation into a working, convention-following PR.