Draft the next sprint from the backlog you have
A candidate list that people can argue with, ready before the meeting rather than during it. Built for a team that spends the first hour of planning finding the candidates.
Linear
Slack
4 steps2 integrationsRuns weekly
Planning starts by scrolling the backlog. What it costs while the work is still done by hand.
- 01Planning starts by scrolling the backlog.
- 02Carried-over work is remembered late.
- 03The list of candidates is different depending on who prepared it.
- Carried over9 issues · from last sprint
- Read backlogget_teams · top 24 issues
- Draft list18 candidates · 4 areas
- Share listpost_message · #eng-planning
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the carried-over work.Linear
- 02Read the top of the prioritised backlog.Linear
- 03Draft a candidate list grouped by area, with dependencies noted.ModuleX
- 04Share it before the planning meeting.Slack
The workflow is an editable graph. Reading runs freely; share it before the planning meeting waits for your opt-in approval until you loosen it. The graph is the receipt.
Candidates, ready to argue with. Paste this into ModuleX chat, or hit Use this workflow.
draft the next sprint from the backlog you have: read the carried-over work; read the top of the prioritised backlog; draft a candidate list grouped by area, with dependencies noted; share it before the planning meeting. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Draft the next sprint from the backlog you have. A candidate list that people can argue with, ready before the meeting rather than during it.
- linear · search_issues
- slack · post_message
A candidate list that people can argue with, ready before the meeting rather than during it.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Check database health without opening the dashboardA short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.
Put an external MCP server to workA tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.
Start the day knowing what moved in the repoA short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.
About this use case.
No. It prepares the candidates. The commitment is the team's.