For project managers - in development
Stop your project plan and status report drifting from what the client asked for.
When a requirement changes mid-project, the Golden Thread shows what it touches - which tasks, which milestone, and what to tell the client - so your plan and your weekly update stay in step.
Free early look. No payment, no card.
Change request CR-07Example
The client said, in Tuesday's call:
"The CSV export also needs the audit fields."
- RequirementR2 - CSV export changed
- Tasks2 tasks reopened, 1 added - Sam
- MilestoneBeta: Oct 30 → Nov 3 +3 days
- Status reportLine added for Friday:CR-07 approved: audit fields added to export. Beta moves to Nov 3.
The change itself is never the problem
Changes are normal. The trouble is that the spec, the plan and the status report are three separate documents, and only one of them gets updated.
What usually happens
- The client asks for a change on a call.
- Someone updates the spec. The plan stays as it was.
- Two weeks later, the team has built against the old version.
- Friday's status report says "on track" because nobody connected the two.
With the Golden Thread
- You log the change once, against the requirement it affects.
- You see the tasks and the milestone it touches.
- The plan is updated where it matters, not everywhere by hand.
- Friday's report already has the line the client needs to read.
How it works
Four steps. You stay in charge; it keeps the links.
- Start from the spec.Paste the requirements document and get a clean, numbered list of requirements.
- Link each requirement to the work.Tie every requirement to its tasks, owner and milestone - or map in the plan you already have.
- Log changes against the requirement.When the client changes something, record it once and see exactly what it affects.
- Write the status report from it.Your weekly update reads from the same record, so it matches what is actually being built.
| Requirement | Task | Owner | Milestone | Status |
|---|
| R1 - Single sign-on | Build login flow | Dana | Beta | Done |
| R2 - CSV export | Add audit fields | Sam | Beta | Changed - CR-07 |
| R3 - Audit log | Write event hooks | Priya | Launch | In progress |
The record behind it all: every requirement traced to the work, the milestone and its real state.
Why not just ask ChatGPT or Claude?
You can, for one document on one afternoon. An AI assistant will turn a spec into a plan in a minute.
The hard part comes in week six, after the twelfth change. Each answer from a chat stands on its own, and nothing remembers which requirement a task came from or what the client agreed last Tuesday. The Golden Thread is that memory: one record that links the spec, the plan, the changes and the report, and stays current as the project moves.
Who's behind it
I'm Gilbert Sekamanya, a project manager and delivery lead. I've spent about ten years shipping software, and I've fought this drift on nearly every project. I'm building the Golden Thread with a small group of project managers. You can reach me directly at
gilbert@patterlabs.ai.
Get an early look
Leave your email and I'll send you an early version before anyone else. No payment, and no mailing list - just a note from me when it's ready.
Thank you - you're on the list.
I'll email you when the early version is ready. If you ticked the call box, I'll write separately to find a time.
Straight answers
Is it ready? Not yet. I'm building it now, and early-look people get it first.
Is it a new app I have to learn? No. It runs on tools you already use - Notion and the AI assistant you already have.
Does the early look cost anything? No.
Who is it for? Project and delivery managers on software and tech projects - in-house, agency or freelance - who keep a spec, a plan and a status report and are tired of reconciling them by hand.