Files
pipelines/internal/author/skill/references/format.md
T

3.2 KiB
Raw Blame History

Definition format

Definitions are Markdown made only of # stage KEY headings and fenced blocks. An optional # settings section precedes all stages. No unrelated prose outside blocks. The first stage receives input.prompt from the runtime user's task; later stages receive exactly the previous executed stage's output map. There are no stage input blocks. Preserve needed context explicitly in output handoffs.

Each model stage requires nonempty output, prompt, configs, and edges blocks:

# stage worker

```output
{ summary, evidence, artifacts }
```

```prompt
Perform the task supplied in input.prompt. Return evidence, not invented success.
```

```configs
type=model
provider=opencode-go
model=deepseek-v4.1-flash
retries=0
```

```tools
```

```edges
success -> #success
blocked -> #failure
error -> #failure
```

Stage/outcome keys begin with a letter and contain letters, digits, _, or -. Each outcome has exactly one target: another stage, #success, or #failure. An omitted error edge defaults to failure. Execution is sequential; forks choose one outcome, never execute parallel branches. Cycles are allowed; every stage must be reachable from entry and have a possible path to a terminal. Use bounded revision counters in prompts/outputs for feedback loops (runtime also has limits).

Only provider opencode-go / model deepseek-v4.1-flash are accepted. Retries are integers 0–100. Explicit empty tools denies all; allowed tools are read, glob, grep, webfetch, websearch, edit, shell, one per line. No wildcards, delegation, or browser tools. Tools are per-stage and automatically enabled by starting a run. edit supports any file type and creating files/directories in the run directory; no file list is required. shell supports commands appropriate to the repository's language and tooling, not a language-specific allowlist. A missing tools block uses local read/glob/grep/edit/shell tools; prefer explicit stage roles. Planning stages must not label a task blocked simply because they defer edits to an implementer stage. Keep examples and prompts language-neutral unless the task itself asks for a specific language.

Scheduling

Manual-only is the default. To schedule, put # settings before all stages with a nonempty fenced prompt and one or more fenced schedule blocks. Each schedule uses exactly one of times=09:00,17:30 or every=15m, optionally days=mon,tue,wed,thu,fri and timezone=Europe/London. Intervals are at least one minute. Submission activates the latest version's schedules immediately. Removing settings disables schedules on the new version. Scheduled shell/edit are not approved. Warn explicitly before adding/changing schedules.

Notifications

Stage hooks use the global phone connection, never store credentials. Optional fenced notify block: on=success,failure, artifacts=markdown. The legacy destination field does not select a per-stage phone. For a native publisher, inspect the anime-today template's ntfy stage: type=ntfy, destination=system; its type-specific blocks differ from model stages. Notification attachment/report support and model availability need real runtime tests; structural validation alone cannot confirm delivery.