@exaudeus/workrail 0.0.6 ā 0.0.7
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
|
@@ -29,19 +29,28 @@
|
|
|
29
29
|
],
|
|
30
30
|
"steps": [
|
|
31
31
|
{
|
|
32
|
-
"id": "phase-
|
|
33
|
-
"title": "Phase
|
|
34
|
-
"prompt": "
|
|
32
|
+
"id": "phase-0-discovery",
|
|
33
|
+
"title": "Phase 0: Comprehensive Discovery & Requirements Analysis",
|
|
34
|
+
"prompt": "Before we build, let's understand the 'why'. This phase ensures your new workflow solves the right problem for the right people.\n\n**STEP 1: Define the Core Problem & Goal**\n\n- **Problem Statement**: Describe the specific, recurring task or problem this new workflow will solve.\n- **Primary Objective**: What is the single most important outcome or key message of completing this workflow?\n- **Critical Failure Mode**: What is the most critical error or negative outcome this workflow is designed to prevent?\n\n**STEP 2: Understand the Users & Context**\n\n- **Target Audience**: Who is this workflow for? Describe their role, expertise level, and what they need to succeed.\n- **Usage Context**: In what situation will this workflow be used? (e.g., during code review, content planning, incident response, customer onboarding).\n\n**STEP 3: Gather Materials & Define Success**\n\n- **Supporting Materials**: What supporting documents, data, or examples are available that could inform the design?\n- **Constraints & Requirements**: Are there any specific constraints, required tools, or other requirements to consider?\n- **Success Metrics**: How will you measure if this workflow is successful? What does a high-quality result look like?\n\n**Agent Guidance**: Synthesize this information and confirm your understanding before proceeding. Use `workflow_list` and `workflow_get` to find suitable templates based on the problem *structure*, not necessarily the domain.",
|
|
35
35
|
"guidance": [
|
|
36
|
-
"
|
|
37
|
-
"
|
|
38
|
-
"
|
|
39
|
-
"TEMPLATE STRATEGY: Focus on structural similarity
|
|
40
|
-
"PROGRESSIVE TEACHING: Even in basic path, introduce advanced features when the use case demands them - just with more explanation."
|
|
36
|
+
"BE SPECIFIC: Vague goals lead to vague workflows. The more precise you are here, the better the final product.",
|
|
37
|
+
"THINK ABOUT THE USER: A workflow for an expert looks very different from one for a novice. Empathize with your audience.",
|
|
38
|
+
"PROVIDE EXAMPLES: If you have examples of the problem or desired outcome, share them now.",
|
|
39
|
+
"TEMPLATE STRATEGY: Focus on structural similarity, not domain similarity, when recommending templates. A good 'bug investigation' workflow might be a great template for a 'customer complaint' workflow."
|
|
41
40
|
],
|
|
42
41
|
"askForFiles": true,
|
|
43
42
|
"requireConfirmation": true
|
|
44
43
|
},
|
|
44
|
+
{
|
|
45
|
+
"id": "phase-1-assessment",
|
|
46
|
+
"title": "Phase 1: Personalized Learning Path Selection",
|
|
47
|
+
"prompt": "Excellent! With a clear understanding of your goals, let's choose the best way to build your workflow.\n\nPlease select your experience level with workflow creation to get a personalized-path:\n\nš± **Basic Path - \"Learn by Doing with Explanation\"**\n - New to workflows or want thorough understanding\n - Step-by-step guidance with detailed explanations\n - Progressive introduction of advanced features with context\n - Focus: Understanding concepts and building confidence\n\nš **Intermediate Path - \"Balanced Guidance with Examples\"**\n - Some experience with automation or process design\n - Structured approach with practical examples\n - Feature recommendations based on your use case\n - Focus: Efficient workflow creation with best practices\n\nš **Advanced Path - \"Full Features with Expert Context\"**\n - Experienced with workflow/automation tools\n - Comprehensive feature access from the start\n - Architectural guidance and performance considerations\n - Focus: Sophisticated workflow engineering\n\n**Agent Guidance**: Based on the user's selection, set the `learningPath` context variable to 'basic', 'intermediate', or 'advanced'.",
|
|
48
|
+
"guidance": [
|
|
49
|
+
"PATH EXPLANATION: Clearly explain what each learning path offers so users can make an informed choice based on the discovery from Phase 0.",
|
|
50
|
+
"QUALITY FOCUS: All paths should result in high-quality workflows. The difference is in teaching approach, not final capability."
|
|
51
|
+
],
|
|
52
|
+
"requireConfirmation": true
|
|
53
|
+
},
|
|
45
54
|
{
|
|
46
55
|
"id": "phase-2-basic",
|
|
47
56
|
"runCondition": {"var": "learningPath", "equals": "basic"},
|