Hyrax
Skill · assembly-line · October 21, 2026

Every deliverable moves through one line.
Two gates, one human yes.

Decks, research reports, and content go through the same stations in the same order. Agents build, check, and challenge the work. The owners make the calls and every final edit.

Gates: fact check + format QAReview: inside + outsideShip: owners only
/assembly-line run in Claude Code
00 · Invoke

Type the command or say the phrase.

The skill lives at ~/.claude/skills/assembly-line/SKILL.md. Claude picks the profile from the brief.

01

Slash command

> /assembly-line one-page memo on AI code review buyers
> /assembly-line Q4 board deck from the finance sheet
# or describe the job in plain words
02

Trigger phrases

  • "run it through the line"
  • "war room this"
  • "build the deck properly" or "full pipeline"
  • A high-stakes deck, report, or content piece that must be accurate
01 · The line

Six stations, always in this order. Only the two gates can stop work.

00

Intake

Writes the brief: goal, audience, format, done-when, example, and sources of truth.

Coordinator
01

Builder

Researches and builds from the sources. Logs every claim with its source.

Subagent
02Gate

Fact-check

Every number, unit, timeframe, name, and quote against the source. Completeness against the brief.

Fresh agent
03Gate

Format QA

Reads the rendered output against the profile rules: palette, grid, overlaps, length, voice.

Fresh agent
04

Story review

Inside · Storyline leadOwns the narrative, proposes cuts
Outside · Red teamReads cold as the audience
Advises, never gates
05

Owners approve

Nothing ships without their yes. Owners make every final edit.

Humans

A gate failure sends the unit back to the builder and through both gates again. After 3 loops, the unit is marked blocked and the owners hear about it.

02 · Roles

Humans own the calls. Agents build, check, and challenge.

01

Owners

Tristan, or the people named in the brief. Narrative calls, decisions, approval, and every final edit.

02

Source of truth

The data owners: data science, Finance, PostHog, or the research sources. The line never invents a number.

03

Coordinator

The main Claude session. It runs the stations, keeps the ledger, and writes the daily brief.

03 · Profiles

One line, many deliverables.

The profile sets the builder's tools, the fact-check focus, the format rules, and who the red team reads as.

ProfileBuilder usesFact-check focusFormat QA rulesRed team reads as
Presentationstrategy-deck-pdf or present-internally, linked Sheet chartsEvery chart value traces to a sheet cellOne message per slide, one main element, no so-what bands, zero overlapsThe person in the room
Research reportmulti-source-research, deep-research, market-researchTwo sources per key claim, dates on every statResearch memo standard, BLUF, readable PDFA skeptical decision maker
Contentwrite-copy, hyrax-brand, write-like-humanProduct facts match the live site and pricingBrand voice, banned words, platform specs, content-ops 90+The ICP buyer scrolling past
OtherClosest skill in the listSame as researchAsked once, then saved to the skillThe named audience
04 · Ledger

One folder per job.

It sits next to the source material, never in a deploy folder.

01

Folder

<job>/
  brief.md   goal, audience, format, sources
  sources.md claim, source, date
  ledger.md  decisions, data asks, objections
  notes/     daily owner notes
  out/       deliverable and previews
02

ledger.md sections

  • Decisions, with dates and owners
  • Data asks: to whom, asked date, status
  • Objections from story review, with status
  • Blocked units after 3 loops
05 · Daily loop

Multi-day jobs run the line once a day.

01–03

Capture

  • Owners write notes
  • Coordinator logs decisions and data asks
  • Builder updates data and units
04–06

Check

  • Fact check
  • Format QA
  • Story review
07–09

Close

  • Coordinator closes resolved items
  • Brief to owners, data asks by owner
  • Owners approve and make the edits
06 · Rules

Every station follows these.

Do
  • Owners make every final edit
  • Every number has a source in sources.md
  • Introduce every subject before use
  • One message per slide, section, or post
  • Plan vs actual uses the owner's budget
Never
  • Overwrite an owner's version
  • Ship a number with no source
  • Block the owners on a slow data ask
  • Use a projection from another deck as the plan
  • Paste a static chart over a linked one
07 · Output

What comes back to the owners.

01

The deliverable

The absolute path to out/ and an open command.

02

Gate results

Pass counts per gate and the loops each unit used.

03

Open objections

Story review points still open, plus one next action.