f5968cfab5
Brings the framework CRS repo up to date with all content that was living in agent-runtimes (local-dev fallback) but hadn't been promoted. New composites: feature-delivery-loop, integration-direct, scaffolding-repo, sonnet-impl-narrow, sonnet-manager, test-writing-repo New contexts: integration/v1, scaffolding/v1, sonnet-manager/v1, z-ai/v1, airouter/v1/bin (anthropic-compat-wrapper.sh), cp-harness/v1/init.sh New task-templates: sonnet-integrator.yaml, workflow/* (17 typed workflow task templates for the Epic 1 pipeline) Updated: agent-repo/v1/finalize.sh — adds AR-38/F97 empty-deliverable audit (SKIP_BRANCH_PUSH support, boilerplate-path filtering, ci_metadata.json flag) Also adds MEMORY.md index and memory/ topic files for the framework repo.
49 lines
1.6 KiB
YAML
49 lines
1.6 KiB
YAML
name: review-spec-arch-opus
|
|
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_BRANCH: "spec/auto-draft"
|
|
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 |