keystone-cli 0.4.0 → 0.4.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
CHANGED
|
@@ -54,6 +54,14 @@ Markdown files with YAML frontmatter:
|
|
|
54
54
|
- **Clarification**: Enable `allowClarification` in `llm` steps if the agent should be able to ask the user for missing info.
|
|
55
55
|
- **Discovery**: Use `mcpServers` in `llm` steps when the agent needs access to external tools or systems. `mcpServers` can be a list of server names or configuration objects `{ name, command, args, env }`.
|
|
56
56
|
|
|
57
|
+
# Seeking Clarification
|
|
58
|
+
If you have access to an `ask` tool and the user requirements are unclear, **use it** before generating output. Ask about:
|
|
59
|
+
- Ambiguous scope or missing details (e.g., "Should this workflow support multiple file formats?")
|
|
60
|
+
- Integration points (e.g., "Which MCP servers should be available to the agent?")
|
|
61
|
+
- Error handling preferences (e.g., "Should the workflow retry on failure or fail fast?")
|
|
62
|
+
|
|
63
|
+
Only ask **essential** questions. Don't over-clarify obvious requirements.
|
|
64
|
+
|
|
57
65
|
# Output Instructions
|
|
58
66
|
When asked to design a feature:
|
|
59
67
|
1. Provide the necessary Keystone files (Workflows and Agents).
|