Files
agent-runtime-framework/task-templates/workflow/review-spec-arch-airouter@1.yaml
Paul O'Reilly 8d7b3af77d fix(templates): add AGENT_UPSTREAM_REPO_URL/BRANCH to all workflow templates using the agent fork
Fresh agent branches were seeded from the stale fork main (AR-39 fell through to fork).
Work item 18efa01f-f941-4f16-bb67-9cafbb6d668a.

Claude-Session: https://claude.ai/code/session_01N218bERyNeLhbLmDRDvbWF
2026-10-02 15:03:34 +13:00

51 lines
1.7 KiB
YAML

name: review-spec-arch-airouter
version: 1
description: Architecture review of a spec draft
runtime: best-practices-airouter-repo
input:
state: spec-draft
tags_forbidden: [security-sensitive]
required_artifacts: [spec_file]
output:
state: spec-reviewed-arch
scope_budget:
files_modified_max: 2
lines_diff_max: 150
wall_clock_seconds_max: 1800
nodes:
- id: agent
kind: agent
template: best-practices-airouter-repo
cli: agentic
model: Qwen3.6
labels: [airouter]
runtime_env:
AGENT_REPO_URL: "git@gitea.oreillyit.nz-ai-enablement:skynet/agent-runtimes-agents.git"
AGENT_UPSTREAM_REPO_URL: "git@gitea.oreillyit.nz-ai-enablement:skynet/agent-runtimes.git"
AGENT_UPSTREAM_BRANCH: "main"
AGENT_BRANCH: "spec/${item.uuid}"
prompt: |
The agent-runtimes project repo is cloned at /workspace/project.
Change to that directory before doing any work.
Review the spec draft for the following concept.
**Title**: ${item.title}
**Original concept**:
${item.body}
Steps:
1. cd /workspace/project
2. Find the spec file: ls spec/ and look for a file matching the concept title slug
3. Read the spec file completely
4. Review it against architectural best practices:
- Are requirements testable and unambiguous?
- Are there security implications not addressed?
- Are interfaces and data contracts clearly defined?
- Are edge cases and failure modes covered?
5. Write your review findings to /workspace/.agent-output/review.md with a PASS or
REWORK verdict and specific findings
6. Call task_complete with "PASS" or "REWORK: <one-line reason>"
escalation:
contract_ambiguous: review-spec-opus