ENGINEERING
Design-review action items to GitHub issues
Parses a finished Zoom architecture review for follow-up action items, then opens a labeled GitHub issue for each one with assignee and context so commitments made on the call…
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completed for review meetingZoom
- ActionFetch transcript from ZoomZoom
- ActionExtract action items with ownersOpenAI
- LogicFilter vague or duplicate items per loop
- OutputCreate labeled GitHub issue per action itemGitHub
What it does
Listens for completed Zoom architecture-review recordings and mines the transcript for concrete action items - the "someone needs to spike X" and "we'll benchmark Y" commitments. Each item becomes its own GitHub issue in the target repo, tagged and assigned, so the follow-ups don't evaporate when the call ends.
When to use it
Use it when design reviews generate plenty of TODOs that never make it into the tracker. Ideal for teams whose engineering work lives in GitHub and who want every spoken commitment to land as a trackable issue automatically.
How it works
- 1A Zoom recording-completed event triggers for the review meeting.
- 2Pull the transcript text from the Zoom API.
- 3An LLM extracts a list of action items, each with a suggested owner and one-line context.
- 4A logic loop iterates the extracted items, filtering out vague or duplicate statements.
- 5For each valid item, create a GitHub issue with an "architecture-review" label, the owner mapped to a GitHub handle, and a link back to the recording.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.