How Golden Thread helps every role

One plugin, every role

Golden Thread sits between you and Claude Code. On the left, the people it serves. Then the one-tap actions each role gets, the protection around every step, the memory every session shares, and the reach into your other tools.

Pick your role at install and gt shapes itself around you.

On the stage: Everyone and everything gt connects, left to right.

A developer's day

Tap Plan this change: you get a phased plan to approve before any code is written. Build the plan works one phase at a time, tests first.

Commit when green only commits once every check passes. The plan itself is saved with the project.

On the stage: Plan, build test-first, and commit only when green.

A product or project manager's week

Your projects start with a status board, a roadmap and a stakeholders list. Ask for your Jira issues and they come through LOTR, without filling your session with raw data.

Draft a stakeholder update from what is already in the notes.

On the stage: Status board in the notes; Jira issues fetched through the gateway.

An executive's one page

Tap One-page brief: the outcome sought, where it stands, what it costs and what is at risk, written from the project's own decisions and research.

A decisions needed list shows what is waiting on you.

On the stage: The project's notes become one page for the executive.

Operations, DBA and network

Each gets the files people in the role keep: an incident and change log, an escalation list, a migration log, a device inventory and an IP/VLAN map.

Log an incident asks what happened and files it. Anything still open becomes a handoff.

On the stage: An incident is logged into the project; open items carry forward.

Rules that stick

Your 10 Core rules are re-asserted for every response, so they never drift out of mind in a long session.

Every finished reply is checked too: one that would leak a secret is sent back before you see it.

On the stage: The rules travel with every response; every reply is checked.

Your fingerprint for what matters

With gt unlock on, sensitive actions wait for you: a gateway call to GitHub, Jira or Microsoft 365, a push, a stored credential.

Approve with Touch ID, Windows Hello or an authenticator code. An agent cannot do it for you.

On the stage: You approve with your fingerprint before the gateway or a push goes through.

Nothing is lost between sessions

At the close, gt files what was learned: findings and decisions into the project, what holds everywhere into the shared wiki, and open items into a handoff.

Next morning, Start my day ranks what is waiting across every project.

On the stage: The close files everything; the next morning starts from the ranked list.

It watches your allowance

LOTR keeps tool schemas and large results out of your context: about half the tokens in typical use, up to 90% with a specialised agent.

The usage meter shows your 5-hour and weekly allowance and what gt saved. Calibrate keeps every agent on the right model.

On the stage: Savings flow into the meter you can see; calibration keeps costs right-sized.

All together

Every role gets one-tap actions. Every step is protected, every session shares one memory, and every outside call goes through a gateway you control.

On the stage: Back to the whole picture: people, actions, protection, memory and reach.