AI coding agents can ship production-ready code in minutes. The problem isn't speed — it's what happens when nothing anchors that speed to the original intent.
Long-context AI sessions suffer from Semantic Noise and Middle Degradation. Strategic pivots made mid-session disappear quietly. The coding agent builds confidently — just not what you meant. This framework solves that by separating exploration from execution and anchoring every build decision to an immutable source of truth.
The Brain — Product Trio Agent
Three AI personas simulate a core product team — TPM, Design, and Engineering. They debate, challenge, and produce the Bedrock. They never touch code. You, the Senior PM, hold ultimate authority.
Meet the personas
| Persona | Role |
|---|
| AI TPM | Strategic Orchestrator. Translates vision into workflow. Authorized to push back on the PM. |
| AI Design (UX) | Advocates for user friction, adoption risk, and branding logic. |
| AI Engineering | Advocates for feasibility, architecture, and technical debt. |
Every major proposal gets a proactive response from at least two personas — friction points, technical debt, UX risks — without being asked. The Trio is a strategic partner, not a passive recorder.
The Bedrock — Four Immutable Pillars
The Bedrock is the source of truth. It is never edited by a coding agent. Every build decision traces back here. Changes are governed by the MACD Protocol — Move, Add, Change, Delete — with a confirmed receipt for every update. The Pillars are either [COMMITTED] or [UNDER AUDIT]. There is no in-between.
See the four Pillars
Pillar I
The Charter — The North Star
Mission, Constraints, User Personas, Domain Glossary, Problem Statement. Includes a C1 System Context diagram. Mandatory for any new feature.
Pillar II
The Specs — The Brain
Unified Strategic PRD, Technical Spec, and UX/Branding Logic. Includes a C2 Container diagram for any structural change. Where resolved decisions land after Sprint 0.
Pillar III
The Quality Gate — The Validation
BDD Scenarios (Given/When/Then) and the Validation/Testing Plan. The absolute Definition of Done. Focused on high-value differentiators and high-friction paths — not a checklist of obvious things.
Pillar IV
The Ledger — The Memory
Roadmap, Change History, Sprint 0 Tasks, and Strategic Dissent records. If the PM overrides the Trio, it's logged here — so The Hands understand why a non-standard path was chosen.
Pillar V — Triggered
The Amendment — The Tripwire
Not part of the Bedrock by default. Raised by The Hands when a technical blocker or superior path requires a fundamental deviation from the HLD. The formal mechanism for The Hands to signal that the HLD and Charter are recommended for update — so nothing drifts without a record.
The Hands — Implementation Agent
Three implementation personas read the Pillars, run a mandatory Sprint 0 to resolve every unknown before a line of code is written, and escalate formally — via a Pillar V Amendment — if the blueprint ever needs to change. Nothing deviates silently.
How The Hands work
| Persona | Role |
|---|
| TPM | Delivery Lead. Keeps implementation true to the Pillars. Flags Charter-level drift. |
| Tech Lead | Owns LLD decisions — library selection, file structure, component logic. Leads implementation. |
| QA Engineer | Owns validation against Pillar III BDD scenarios and any additional implementation tests. |
Sprint 0 is a Three Amigos session — all three personas plus the Senior PM — that runs automatically after the Pillars are read. Every LLD unknown is resolved or formally escalated. The PM signs off before implementation begins.
If The Hands hit a blocker or find a better path mid-build, they raise a Pillar V Amendment — the formal signal that the HLD and Charter are recommended for update. Nothing drifts without a record.
Install It
The Brain works in Claude.ai or Gemini Chat. The Hands run as a skill inside Claude Code or Gemini CLI. Both are in the repo.
Installation steps
The Brain — Claude.ai or Gemini Chat
Open product-trio-brain/system-prompt.md and paste the contents as a system prompt or into a Claude Project. Seed it with your product context — the Trio activates and begins building the Bedrock.
The Hands — Claude Code
Clone the GitHub repository and run:
cp -r the-hands-agent ~/.claude/skills/
The Hands — Gemini CLI
Copy the contents of the-hands-agent/SKILL.md into your GEMINI.md at the project root.
I'm genuinely excited for people to try this. If the drift problem resonates — try it, break it, tell me what you find. I'm always happy to collaborate, whether that's a quick question or a deeper conversation about how to adapt it to your stack.
