Draft a spec from the files
draft_specReads input, output, and trace files to propose a spec with output structure, input seals, ID links, trace ordering/counts, and field profiles; deterministic, flagged for human review.
Instructions
Read the input, output and trace files and propose a spec: structure checks for outputs, seals on the inputs, checks relating output ids to input ids, and for traces the ordering and counts it can infer. Also returns a profile of every field so you can write your own conditions without opening the files. Deterministic, no model calls. It never fits a threshold to an output; the spec is marked draft and every verdict against it carries a warning until a person removes the flag.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"spec_path": "<spec_path>"
},
"name": "draft_spec"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| write | No | write the draft to spec_path; refuses to overwrite | |
| inputs | No | name -> path of files given to the agent | |
| traces | No | state logs, read in order | |
| outputs | No | name -> path of files the agent must produce | |
| task_id | No | ||
| spec_path | Yes | Where the spec will live; paths are made relative to it. Written only if write is true. | |
| description | No | ||
| line_prefix | No | only lines starting with this are records; detected if omitted |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| spec | Yes | ||
| notes | Yes | ||
| profiles | Yes | ||
| written_to | Yes |