Gear6

See what’s slowing the team down, and what to fix first.

Gear6 connects Slack, GitHub, and Jira to show the open decisions, stalled handoffs, and recurring dependencies behind delivery drag.

First six months free

What am I looking at?

Everything the team is running, and which of it stopped moving.

Gear6 Pulse: counters reading 6 regressed, 3 blocked five days or more, 5 went quiet, 18 closed out, above a list of milestones with status pills and 30-day activity sparklines.

What do I have to do about it?

What’s blocked, what’s today, what can wait.

The compact Gear6 window: 9 open actions for you, split into 2 blocked, 4 today, 3 later, with each item naming its milestone and source.

Says who?

Every item opens onto the conversation it was read out of.

Gear6 Inbox: an open unblock item about a gateway rejecting kind 44200, with the reason it is listed and the four-message Slack conversation it was derived from.

How does it actually work?

Nobody tags a message as a decision. Gear6 works it out.

One Tuesday, as it arrived

why is results an array if each entry has queryName?
✅
redis down 45m, querier failing in acme-prod
yes do it

What it became, by 6pm

DecisionQuerier V3 response shape · open 6d
HandoffShort-URL doc · clock started on a reaction, not a reply
ConstraintRedis outage · blast radius 3
Held backA bare approval, until its thread can be read

Read-only · Gear6 never posts, resolves, or assigns

Does it read my tools?

SlackGitHubJiraNotionConfluence nextLinear next

Help shape Gear6 around the work your team does.

Design partners get the first six months free.