xiaoju
63cb4d3645
CI / check (pull_request) Successful in 3m7s
$START keeps _ (special entry node). All user-defined roles now require explicit $status enum in frontmatter + matching graph keys. - moderator: remove UNIT_STATUS fallback, error on missing $status - validate: reject _ graph keys for non-$START roles - validate-semantic: remove checkSingleExitRole(), require $status enum - update all test fixtures to use explicit status values - fix examples/analyze-topic.yaml Fixes #86
41 lines
1.3 KiB
YAML
41 lines
1.3 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:
|
|
_: { role: "analyst", prompt: "Analyze the topic in the task and produce a structured summary with key points." }
|
|
analyst:
|
|
done: { role: "$END", prompt: "Analysis complete. Finish the workflow." }
|