Context.
Everything the builder needs to know to produce a high-quality agent package. Input manifest, domain knowledge, and reference standards. Read 02-golden-example/ before this file — see the target before reading the reference.
Input Manifest
Everything the builder needs — or would like — from the human before it starts generating. Missing a Required input means stop and ask; missing an Optional one means proceed with defaults.
Required
Source material
At minimum one of: a description of repeatable work, a GitHub repo URL, a completed deliverable, a transcript of the work being done, or a document describing the process. More sources = better agent.
Golden example mode
Before any mapping or generation, the builder must ask the human: are you bringing me the golden example, or am I building it? The builder presents both options with neutral trade-offs and waits for an answer. There is no default — the build does not proceed to Phase 2 until the human has chosen.
Mode A — Human-provided. The human supplies a real, completed instance of the deliverable. The builder treats it as the specification and reverse-engineers the process, context, and quality files from it.
Mode B — Builder-drafted. The builder generates the golden example from the human’s description, source material, and clarifying answers. The human validates the draft before the rest of the package is built.
Both modes produce a complete five-file package. The downstream process and the order of validation differ. The choice is the human’s.
Agent name
What should this agent be called? Used for the folder name and document titles. Convention: lowercase, hyphenated. Examples: daily-dispatch, support-email-agent, sales-coach.
Target functional area
Which value-chain folder (1–10) does this agent live in? Determines the save path: [N]. [Area]/Agents/[agent-name]/.
Recommended
Trigger phrase
The phrase that activates this agent. Convention: a natural-language phrase Natalee would say. Examples: “Run the daily dispatch,” “Wrap up the call,” “Build an agent for…”
Input sources
Where does the agent get its data? Files on disk, APIs, Gmail, spreadsheets, web scraping, transcripts? Shapes the context file and determines what tools the agent needs.
Optional
Quality criteria
Specific standards the output must meet. If not provided, the builder infers quality gates from the golden example and standard defaults.
Target level
Which of the 7 Levels of Execution should this agent target? Default: Level 4 (single agent, human-triggered). The builder will note if the design could support a higher level.
Domain — The Five-File Structure
Every agent is a folder with five files. The builder must produce all five.
| File | Purpose |
|---|---|
01-start-here.html | Entry point. Part A: what it produces, what it needs, how long, how to run. Part B: agent training. Part C: human training. |
02-golden-example/ | A completed, high-quality deliverable. Uses the deliverable’s format, not the agent format. This IS the specification. |
03-process.html | Machine-readable execution steps. Numbered phases, decision rules, branching logic. Written for Claude to parse and follow. |
04-context.html | Input manifest (required, recommended, optional) plus domain knowledge tables. Static reference data that doesn’t change between runs. |
05-quality.html | Five gates with blockers, majors, and minors. Weighted scoring. Pass criteria: all blockers pass, no more than 2 majors remaining. |
Domain — The Seven Levels
Reference for classifying agent complexity and suggesting level-ups. Default target for a new agent is Level 4.
| Level | Description | Multiplier |
|---|---|---|
| 01 — Manual | Everything in people’s heads. | 0.1× |
| 02 — Documented | Processes written down. SOPs exist. | 1× |
| 03 — AI Workflow | SOPs become prompts. AI handles drafts. | 10× |
| 04 — AI Agent | AI reads the SOP, makes decisions, delivers finished work. Human-triggered. | 100× |
| 05 — Agent Swarm | Dozens of agents in parallel. | 1,000× |
| 06 — Orchestration | VP agent directs swarms autonomously. | 10,000× |
| 07 — Self-Governing | System improves itself. | 100,000× |
Domain — HTML Format Standard
All internal agent files use the canonical house style defined in 0. Chief of Staff/house-style.html. Copy its <style> block verbatim into every new file — do not paraphrase, trim, or modernize it.
Inter only — four weights
Inter at 400 for body, 500 for labels and nav, 600 for structural type (headings, strong, table headers, card titles), and 700 reserved for rare emphatic display. Never import Instrument Serif, DM Sans, JetBrains Mono, Helvetica, or Playfair.
Ten tokens — linen base plus Prussian Blue
--ink, --ink-soft, --mid, --muted, --faint, --rule, --rule-soft, --wash, --paper, --accent. The accent (#064769 Prussian Blue) is punctuation — nav mark, section counters, footer tick — never a fill.
Rule cards, card grid, flow, data table
Compose every document from these components: .rule-group holds numbered .rule-card blocks for rules, steps, and callouts. .flow with .flow-step children diagrams any time-ordered process. .data-table handles tabular data with an ink band above and below the header row. No fills, no shadows, no rounded corners above 2px.
Hero, auto-numbered sections, footer
Every page opens with a .hero (hero-label + h1 + lede), then stacks <section> blocks. A CSS counter on <main> auto-numbers each section as 01, 02… in the accent color above the h2. Footer is a flex row with a dot, document label on the left, sub-label on the right.
Domain — Source Type Reference
How to map common source materials to the five-file structure.
| Source Type | Mapping Strategy |
|---|---|
| GitHub repo | README → START-HERE. Mode/command files → process. Config/env → context. Sample outputs → golden example. Tests/linting → quality. |
| Transcript | Extract the repeatable pattern. Steps taken → process. Data referenced → context. Final output → golden example. “We should check for…” → quality. |
| Completed deliverable | The deliverable IS the golden example. Reverse-engineer the steps → process. Identify inputs → context. Define “what makes this good” → quality. |
| SOP / runbook | Steps → process (almost directly). Referenced data → context. “Example output” sections → golden example. Checklist/sign-off → quality. |
| Working tool / app | User flow → process. Settings/config → context. Demo/sample output → golden example. Validation rules → quality. |
Workspace Reference
Key paths in the operating system that the agent builder references.
| Path | What’s there |
|---|---|
0. Chief of Staff/ | Operating system, agent command center, kanban. |
0. Chief of Staff/house-style.html | Canonical house style for all internal HTML. Copy its <style> block verbatim into any new internal file. |
5. Operations/Agents/agent-builder/ | This agent. The meta-agent. |
5. Operations/Agents/agent-builder/02-golden-example/ | The presentation agent — complete five-file reference. |