Skip to content
DarkPrint
Aautogencode-builder1.0.0

Code Builder

Get card

Clone

npx -y darkprint clone code-builder@1.0.0

There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.

↓ 1 downloads

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

used in 1 blueprint

Specification

115 words · handed to the agent

A build brief arrives with the run: an ordered list of steps, each naming the file or module it touches and what should exist once it is done. Work through the steps in order and write the source they describe, staying inside the files each step names and adding no behaviour nobody asked for. Emit the finished source on build as one complete, compiling change, with no commentary and no summary of what you did. The brief is all you get, and that is the point do not go looking for a test suite, do not reason about how the result will be checked, and do not tune anything toward a check you imagine exists.

Interfaces

1 in · 1 out

Inputs

1
Inputs declared by this node card
NameData typeRequiredDescription
briefplan requiredThe ordered build steps the run was instantiated with, the only thing this node sees.

Outputs

1
Outputs declared by this node card
NameData typeDescription
buildcodeOne complete, compiling change implementing the brief, with no commentary attached.

Dependencies

0

None declared, no edge has to arrive for this node to run.

Card values

17 declared

Who the node is. The id is the key the DOT pins.

id
code-builder
name
Code Builder
type
agent
phases
Implementation
Behaviourcard spec →

What it does, and the prose the agent is handed when the graph runs.

action19 words
Work through the build brief and emit the source it describes, adding nothing the brief does not ask for.
spec115 words
A build brief arrives with the run: an ordered list of steps, each naming the file or module it touches and what should exist once it is done. Work through the steps in order and write the source they describe, staying inside the files each step names and adding no behaviour nobody asked for. Emit the finished source on build as one complete, compiling change, with no commentary and no summary of what you did. The brief is all you get, and that is the point do not go looking for a test suite, do not reason about how the result will be checked, and do not tune anything toward a check you imagine exists.in full above
model
claude-sonnet-5
agent
Builder
skill
skills/code-builder.md
tools
none
mcp
filesystem
params
none
Interfacescard spec →

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs
brief : plan
outputs
build : code
dependencies
none
cannot
acceptance-criteria
will_not
read the checks the work will be run against
Evaluation metadatacard spec →

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers
none
notes128 words
Doc 1 §3.2: isolation is not only an absent edge, it is the absence of the content from the spec. This card is the reference for what that looks like, the spec above names no criterion, quotes no threshold and paraphrases nothing the planner wrote, so the similarity half of the criteria-leak check stays quiet on it as well as the topological half. Measured against spec-planner@1.0.0, the 3-gram Jaccard similarity is 0.0356, against a configured threshold of 0.35. acceptance-criteria in cannot names a data type in the ontology, so the resolver enforces it: draw an edge that carries the criteria into this node and the bundle fails with bundle/prohibition-violated. The absent edge is a rule the engine holds the graph to rather than a convention the author remembered.
Service fieldscard spec →

The card's own version, and who wrote it.

version
1.0.0
author
autogen
provenance
not stated

Definitions for every card field

Version history

1 version published
  1. code-builder@1.0.0currentsha256:a51438a2c2ecbc52b27ba4679e21655a327c6807d08068f02c20c186996df643

    pinned byStarter Software Factoryautogen/starter-software-factory

A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.

First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.

Community notes (0)

No notes yet.

Nobody has posted about this node card yet.

Sign in to post a note.