Harness Suite
A harness that splits campaign-running agent teams by domain while syncing a shared core. It is the working environment I use every day, and the rest of this portfolio was built inside it.
Overview
A harness that splits campaign-running agent teams by domain while keeping a shared core in sync. It is the environment I work in every day, and the rest of this portfolio was built inside it.
One core agent team is the source of truth, and four domains (medical, commerce, saas, content) each hold a copy of it. No symlinks. Any one domain has to be deliverable on its own, and an incident in one must not spread to the others. Changes to the core propagate through a sync script.
The rule I care most about is that the agent producing work is not the agent reviewing it. A writer's own check is a filter, nothing more, and no patient-facing copy ships without an independent reviewer's verdict. Treat passing your own check as approval and you effectively have no line of defense at all.
Operating rules live in hooks rather than in documents. Skills are routed when a prompt comes in, and dangerous commands are blocked at the moment a tool runs. Anything that depends on a person remembering it collapses on a busy day.
Core skills
Implementation
- 1Keeps one core agent team as the source of truth, with medical, commerce, saas, and content domains each holding a copy. No symlinks, so any single domain can ship on its own.
- 2Separates the agent that produces work from the agent that reviews it. A writer's self-check is only a filter; nothing publishes without an independent reviewer's verdict.
- 3Handles skill routing and dangerous-command blocking through UserPromptSubmit and PreToolUse hooks, so the rules live in the execution path instead of in a document.
Strengths
- Pulling review away from the author is the point. Passing your own check is not approval, and that single rule turns one line of compliance defense into two.
- Because each domain owns a copy of the core, an incident in one domain does not spread to the others.
- The work above, this portfolio included, came out of this environment. That is the difference between using tools and building the ones you use.
Metrics
Tech stack
Screenshots