Files
archie/modules/runs/testdata/corpus/implement.yaml
T
sam ce70d4f3ee feat(runs): workflow documents take today's step shape, references and when (#2039)
A step is id/type/settings with when and on_failure; the five kinds become
the types agent.run (inline mission), connector.action, approval.wait,
run.notify and workflow.sleep. Documents declare inputs, repository,
instructions, identity and profile; references are {{ task|inputs|steps }}
checked at save. Any number of approval steps, each asking only about what
was held since; actions still held at the end are put to people before the
run finishes. Triggers are refused for a workflow they can't start, and the
workflows API lists, reads and saves documents beside a step-type catalog.

Copied from internal/domain/workflow: definition.go, step_refs.go,
step_flow.go's checks, control_steps.go's when parser, vocabulary.go and
task/interface.go. stableid moves to internal/platform.
2026-11-17 18:43:45 +11:00

45 lines
1.7 KiB
YAML

identity: 6f129e29-0e26-5246-99bd-74cb4496203b
steps:
- type: repo.prepare
- type: repo.tooling
- type: gate.repository
settings:
repair: true
- id: plan
type: agent.run
settings:
read_only: true
mission: |
Produce a concrete implementation plan for this {{ task.kind }} on the repository {{ task.repository }}.
{{ task.plan }}
{{ task.prompt }}
Explore the codebase with your read-only tools, then call finish with status "passed" and the plan as the summary: files to touch, the approach, acceptance criteria, and what tests should prove it. Keep the plan tightly scoped to the task. Call finish with status "blocked" if the task is too vague or too large for one PR.
- id: build
type: agent.run
settings:
gate: repository
extra_rules: Files matching the repository's protected suffixes (e.g. generated code) are write-blocked. Edit their sources instead; the gate regenerates them.
mission: |
Implement this {{ task.kind }} on the repository {{ task.repository }}, following the plan below.
{{ task.prompt }}
<plan>
{{ steps.plan.summary }}
</plan>
Make the smallest change that satisfies the task and the plan's acceptance criteria. Do not run git: the orchestrator commits and pushes for you. When done, call finish with status "passed" and a summary written for the operator or agent who will review the pull request: what changed, why, and how it was verified.
- type: repo.commit
settings:
message: "{{ task.title }} (archie)"
reference: Implements
push: true
if_empty: complete
- type: repo.open-pr
settings:
review: true
body: "{{ steps.build.summary }}"