Archie

One teammate who knows every client, every rule and every decision.

A Claude Code plugin that works inside the repos you already have. Hand it an Asana ticket; it builds, reviews and QAs it the way Pact works, then drafts the PR for your go.

Get started See how a ticket runs
Scroll
What went into it

Built from a year of our own work.

14 research agents read 12 months of Asana, Slack and GitHub
1,200 pull requests across 22 repos
2,000 reviewer comments distilled into rules
What Archie knows

Three layers of memory.

Ring 01 — Pact Process, code standards, PR and QA templates, tools.
Ring 02 — Clients Deploy rules, stack, gotchas and the full decision history for 12 clients.
Ring 03 — Reviews ~270 checklist rules, each traced to its reviewer and PR.
Reads the repo

Archie detects the stack before it writes a line.

Shopify facts come from Shopify's live docs — never from memory.

Skeleton Ohm Horizon Dawn Stiletto Agency themes
How a ticket runs

Five stages. Every ticket. Every time.

01Solution
02Build
03Review
04Visual QA
05PR + Handoff
Stage 01 — Solution

It thinks before it builds.

Agent AReads the ticket, thread and client history
Agent BScans the repo for reuse and detects the stack
Agent CChecks open PRs for conflicts

Then: an approach brief — and it waits for your go.

Stages 02–04 — Build, review, QA

Two reviewers who didn't write the code.

02 BuildIts own branch and worktree, to the client's rules.
03 Review/code-review and the Pact checklist auditor run in parallel until both are clean.
04 Visual QAOn a real theme, measured against Figma when applicable, at phone and desktop.
Stage 05 — PR + handoff

It asks before anything leaves your machine.

PR, Verification comment and QA steps are drafted, then shown to you. Nothing is pushed, posted or merged without your yes.

The commands

One command, or one stage at a time.

Run the whole ticket, or just the part you want help with.

/archie:start<Asana URL>
All five stages, start to finish. Stops for your go after the approach and before anything is pushed. You're picking up a new ticket.
/archie:approach<Asana URL>
Stage 1. Reads the ticket, client history and repo, then writes an approach brief with questions. You want to scope or estimate before committing.
/archie:build
Stage 2. Builds in its own branch and worktree, to the client's rules. The approach is agreed.
/archie:review
Stage 3. /code-review plus the Pact checklist auditor, fixes, re-runs until clean. Works on any branch, even code Archie didn't write. You want a second pair of eyes on your own work.
/archie:qa
Stage 4. Visual QA on a real theme, measured against Figma or the reference, phone and desktop. You want a pixel check before review.
/archie:ship
Stage 5. Drafts the PR, Verification comment and QA steps. Given a PR with requested changes, works through every comment. You're ready to open the PR, or a review came back.
/archie:ask<question>
Answers from Archie's client files and history. Changes nothing. “How does Cosabella deploy?” “Who reviews Beekman?”
/archie:sweepConnor only
Weekly update from review comments and team feedback.

Every command follows the same guardrails. Skipping ahead doesn't skip review: /archie:ship runs the review first if it hasn't been done.

Memory

Come back next week. It picks up where you left off.

ApproachDone · Oct 8
BuildNext
Review—
QA—
Ship—
archie
› /archie:start <Asana URL> Approach agreed Oct 8. Build not started. Picking up at Stage 2.
One log per ticket.The approach, your answers, review findings and QA results are saved as Archie works.
Finds it on its own.By the Asana ticket, or by the branch you're on. Renamed tickets don't matter.
No repeat work.No second round of research or questions. If the code changed since last time, it re-reviews what changed before moving on.

The log stays on your machine. It never goes into git or a PR. Picking up a teammate's ticket? Archie starts fresh from Asana.

How Archie gets smarter

It learns from what we already do.

WeeklyConnor's sweep reads every review comment across our repos.
AnytimeFeedback posted in #archie goes into the next sweep.
One PRNew rules, reviewed and merged by Connor.
AutomaticEveryone's Archie updates itself the next time they start a session.

Archie never adds anything to your PRs for itself, and you never have to update it or report back.

Guardrails

Fast, but never reckless.

Enforced by the plugin — whatever command you run
Asks before every push, PR change, comment or theme push, even from outside the repo
Asks before posting anything to GitHub, Asana, Slack or email
Can't publish a theme or edit a Figma file
Blocks AI attribution in commits, PRs and comments
Built into how it works
Never merges to a live branch without the owner's go
Humans do every login, no credentials anywhere
Nothing internal in client-visible channels
You're accountable

Archie drafts. You own what ships.

Review everything it produces — code, PR copy and comments — before it goes out. If it ships under your name, it's yours.

Getting started

About fifteen minutes to set up. Then it's yours.

01Get access to workwithpact/archie on GitHub (ask Connor).
02Open Claude Code (terminal or desktop app), drop in INSTALL.md and say “install Archie”. It checks your tools, installs the plugin and turns on auto-update.
03Figma: install Figma desktop and the Figma MCP Bridge plugin. INSTALL.md walks you through it.
04Start a new session in any client repo you already have. You'll see “Archie is ready”.

Point it at your backlog.

Or start smaller: /archie:review on a branch you're already working on.