2fa4dc92c2
- scaffolding-repo + test-writing-repo: anthropic-cloud-paul-oauth -> minimax + minimax-m3-max - merge@1: new best-practices-minimax-repo composite (impl-review stays Sonnet) - spec-draft-opus@1: Opus -> Fable 5 low effort via new fable-low-effort/v1 env context (ANTHROPIC_MODEL=claude-fable-5, MAX_THINKING_TOKENS=1024) + spec-writing-fable-low-repo composite - review-spec-arch-opus@1: Qwen3.6/airouter -> Fable 5 low effort via best-practices-fable-low-repo (arch review was on the cheapest model) Template names kept (trigger rules reference them). Node model: fields removed where env pins the model — a --model flag overrides ANTHROPIC_MODEL. Claude-Session: https://claude.ai/code/session_019tJk7P8tZzJ24PvtgoGhLN
49 lines
1.8 KiB
YAML
49 lines
1.8 KiB
YAML
name: review-spec-arch-opus
|
|
version: 1
|
|
description: Architecture review of a spec draft
|
|
# Fable 5 low effort (2026-09-02) — was Qwen3.6 via airouter, the cheapest
|
|
# model reviewing architecture while Claude did scaffolding. Template name
|
|
# kept for trigger compat; model comes from the fable-low-effort/v1 env layer.
|
|
runtime: best-practices-fable-low-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-fable-low-repo
|
|
runtime_env:
|
|
AGENT_REPO_URL: "git@gitea.oreillyit.nz-ai-enablement:skynet/agent-runtimes-agents.git"
|
|
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 |