multi-executor-review-chain-example.task.md

June 23, 2026 ยท View on GitHub

chain.context

Prepare a short change brief for {{var:project_name}}.

Use this feature brief: {{file:.crewplane/workflows/example-templates/sample-inputs/feature-brief.md}}

Return:

  1. Goal
  2. Constraints
  3. Files likely to change

chain.iterate

Work through this handoff chain using the context below: {{chain.context.output}}

Executor semantics:

  • The first executor should make an initial implementation pass.
  • The second executor should inspect the same workspace, refine or complete the result, and explain any disagreements with the first pass. Return the full revised candidate, commands run, and generated-file paths when files change.

Reviewer semantics:

  • Evaluate the latest workspace state plus both executor artifacts for correctness, regressions, and missing validation.
  • Do not edit files.

End with the structured review sections and a final verdict token.

Stop only when no major or minor issues remain; optional nitpicks may remain.

chain.summary

Summarize the multi-executor review chain from: {{chain.context.output}} {{chain.iterate.output}}

Include:

  1. What the first executor did
  2. What the second executor refined
  3. Reviewer verdict and follow-up work