Files
agent-runtime-framework/task-templates/workflow/spec-draft-opus@1.yaml
Paul O'Reilly 2fa4dc92c2 pipeline model routing: mechanical stages to MiniMax M3, spec stages to Fable low effort
- 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
2026-09-02 21:43:23 +12:00

47 lines
1.6 KiB
YAML

name: spec-draft-opus
version: 1
description: Draft a spec from an idea using spec-writer agent
# Fable 5 low effort (2026-09-02) — template name kept for trigger compat.
# Model comes from the fable-low-effort/v1 env layer; no node model: here
# (a --model flag would override ANTHROPIC_MODEL).
runtime: spec-writing-fable-low-repo
input:
state: idea
tags_required: []
tags_forbidden: [security-sensitive]
required_artifacts: []
output:
state: spec-draft
scope_budget:
files_modified_max: 5
lines_diff_max: 300
wall_clock_seconds_max: 3600
nodes:
- id: agent
kind: agent
template: spec-writing-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.
Draft a spec for the following concept and commit it to the repo.
**Title**: ${item.title}
${item.body}
Steps:
1. cd /workspace/project
2. Read existing specs in spec/ to understand the format
3. Create a slug from the title (lowercase, hyphens instead of spaces)
4. Write the spec to spec/<slug>.md following the project spec format
5. git add spec/<slug>.md && git commit -m "spec: auto-draft ${item.title}" && git push
6. Call task_complete with a one-sentence summary
The spec should have numbered requirement IDs, clear acceptance criteria,
and error handling. Follow the format of existing specs in spec/.
escalation:
scope_exceeded: replan-spec-opus