Planning playbook
Generate Requirements
Turns a labeled ticket into a structured requirements document, posted as a comment.
When a ticket is labeled 'requirements', read it and post a structured requirements document as a comment: goal, scope, user story, acceptance criteria, and open questions.
- Identifier
generate-requirements- Version
- 1.0.0
- Steps
- 2
- Triggers
- 1
- tickets
- requirements
- planning
- automated
When it runs
Ticket
ticket.labeled- Settle delay
- 5s after the event
Only when all hold
- ticket.addedLabel equals requirements
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 requirements
triggerThe event that starts the run.
- 02Generate Requirements
agent.runOne agent works the task with its toolkit.
The agent
Requirements Author
- Base type
- Product Manager
- Temperature
- 0.2
- Max iterations
- 20
- Tools
- 3
Tickets · 3
read_ticketRead Ticket · readread_ticket_commentsRead Ticket Comments · readadd_comment_to_ticketAdd Comment to Ticket · write
Related playbooks
Break Down TicketDecomposes a labeled ticket into a concrete set of proposed sub-tasks.Ticket Estimate AssistantOn ticket creation, finds comparable closed tickets by semantic search and proposes an estimate anchored in actual cycle time.Blocked Ticket EscalatorTracks tickets that move to a blocked status and escalates with status updates at 3 days and to the board owner at 7 days.