@maplezzk/pi-dynamic-workflows 1.2.0 → 1.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/workflow-tool.ts +0 -1
package/package.json
CHANGED
package/src/workflow-tool.ts
CHANGED
|
@@ -92,7 +92,6 @@ export function createWorkflowTool(options: WorkflowToolOptions = {}): ToolDefin
|
|
|
92
92
|
promptSnippet:
|
|
93
93
|
"Run a deterministic JavaScript workflow. Required script header: export const meta = { name: 'short_snake_case', description: 'non-empty description', phases: [{ title: 'Phase 1' }, ...] }. Every agent() call requires opts.schema (JSON Schema). Use phase(title) at runtime to drive progress.",
|
|
94
94
|
promptGuidelines: [
|
|
95
|
-
"Use workflow only when the user explicitly asks for a workflow, workflows, fan-out, or multi-agent orchestration.",
|
|
96
95
|
"For workflow, always pass one raw JavaScript string in the required script parameter; do not include Markdown fences or prose around the script.",
|
|
97
96
|
"For workflow, the script's first statement must be `export const meta = { name: 'short_snake_case', description: 'non-empty human description', phases: [{ title: 'Phase A' }, ...] }`. meta.name and meta.description must be non-empty strings; meta.phases must be a non-empty array of `{ title: string }` objects.",
|
|
98
97
|
"For workflow, meta.whenToUse is an optional string that describes when this workflow should be invoked; include it whenever the workflow has a non-obvious trigger condition.",
|