Skip to content
DarkPrint
Design your blueprint via the DarkPrint skillConnect via MCP

Blueprint registry

DarkPrint
Reusable blueprints for agent workflows.

Skip to the first section

Reproducible runs, improvable steps

A prompt lets the harness invent the route, so every run is a different run and every score a one-off. A blueprint fixes the steps, so you can study them one at a time and raise the score on purpose.

from a promptyou do not control the path
A goal on the left, and three runs that leave it for three different endings, each with a score of its own: 0.62, 0.81 and 0.55.0.620.810.55goal
same prompt · three routes · no step to credit for the score
The harness picks the steps, and picks differently each time. Three scores, and no two of them are measuring the same thing.
from a blueprintyou define the steps, then tune them
retrieverankdraft

this route runs every time, in this order

Four runs of one blueprint, numbered 01 to 04. Each row names the one step it changed and reports the score and the change from the run before it.
iterwhat changedscoredelta
01baseline0.62
02retrieve → v20.71+0.09
03rank removed0.66−0.05
04draft → v20.86+0.15
one step changed per iteration · everything else held
The steps are yours, so a rerun is the same run. Change one, read the score, and the difference belongs to the thing you moved.

That is what reproducibility buys: a system you can study a part at a time, and improve on purpose rather than by luck.

What surrounds a run →

This is a blueprint

Which agents run and what each hands to the next. Download the folder and run it.

starter software factory
A planner and a builder both feed a tester. The tester sends failure evidence to a debugger and the debugger sends a patch back. The tester hands an approved build to a deployer. One run is deliberately missing, from the planner to the builder, because the builder's card forbids it from receiving acceptance criteria.◌ acceptance-criteriaPlannerBuilderTesterDebuggerDeployer
five nodes, five edges

A blueprint pins the handoffs, loops, checkpoints, and deliberate absences that make a workflow reusable. The files stay plain enough to inspect before your harness runs them.

What a blueprint is →

Every node is a card

Open one and it says what it does, the brief it is handed, which model runs it, what arrives, and what must never reach it.

One of the 5 nodes is code-builder, and the card under this strip is the card that node pins.code-builderis this card
code-builderv1.0.0 · by autogen
agentimplementationclaude-sonnet-5

Work through the build brief and emit the source it describes, adding nothing the brief does not ask for.

inbrief : planoutbuild : code
Must never arrive: read the checks the work will be run againstcannot: acceptance-criteria

Each node pins an exact card version: its job, interface, tool reach, and prohibitions. Reuse the card in another graph.

Card format reference →

Write your first blueprint

The tutorial takes you from a small task to a folder your agent can run, and the graph draws itself as you answer.

  1. 01 Design in conversation
  2. 02 Watch the graph draw
  3. 03 Enrich through MCP
  4. 04 Keep it on your account
Write your first blueprint

In Claude Code or Codex. No account needed to start.