xiaoju
fbfd31a042
CI / check (pull_request) Successful in 2m27s
BREAKING: All workflow YAML files must update $START._ to $START.new + $START.resume. The resume edge prompt replaces the previously hardcoded resume message. - evaluate.ts: remove START_ROLE/START_STATUS special case, use $status like all nodes - thread.ts: resolveEvaluateArgs passes 'new', cmdThreadResume passes 'resume' - validate.ts: reject '_' everywhere (no longer valid) - validate-semantic.ts: require 'new' and 'resume' edges on $START - All workflow YAMLs and test fixtures updated Fixes #101
42 lines
1.5 KiB
YAML
42 lines
1.5 KiB
YAML
name: "analyze-topic"
|
|
description: "Single-role topic analysis using four-phase role description"
|
|
roles:
|
|
analyst:
|
|
description: "Analyzes a given topic and produces a structured summary"
|
|
goal: |
|
|
You are a research analyst with expertise in breaking down complex topics
|
|
into clear, structured summaries. You think critically and cite key points.
|
|
capabilities:
|
|
- research
|
|
- critical-thinking
|
|
- structured-writing
|
|
procedure: |
|
|
Analyze the topic by:
|
|
1. Identifying the main thesis or question
|
|
2. Listing 3-5 key points with brief explanations
|
|
3. Noting any counterarguments or caveats
|
|
Keep your analysis concise (under 500 words).
|
|
output: |
|
|
Provide your analysis as markdown under the frontmatter.
|
|
The frontmatter must include your structured findings.
|
|
frontmatter:
|
|
type: object
|
|
properties:
|
|
$status:
|
|
enum: ["done"]
|
|
thesis:
|
|
type: string
|
|
keyPoints:
|
|
type: array
|
|
items:
|
|
type: string
|
|
caveats:
|
|
type: string
|
|
required: [$status, thesis, keyPoints]
|
|
graph:
|
|
$START:
|
|
new: { role: "analyst", prompt: "Analyze the topic in the task and produce a structured summary with key points." }
|
|
resume: { role: "analyst", prompt: "Review the previous analysis output and continue with additional context." }
|
|
analyst:
|
|
done: { role: "$END", prompt: "Analysis complete. Finish the workflow." }
|