@exaudeus/workrail 0.0.13 → 0.0.15
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/spec/examples/coding-task-workflow.json +126 -107
- package/spec/examples/conditional-workflow-example.json +251 -212
- package/spec/examples/valid-workflow.json +118 -115
- package/spec/workflow.schema.json +62 -2
- package/workflows/adaptive-ticket-creation.json +272 -245
- package/workflows/coding-task-workflow.json +317 -138
- package/workflows/learner-centered-course-workflow.json +267 -265
- package/workflows/personal-learning-materials-creation-branched.json +195 -175
- package/workflows/presentation-creation.json +244 -237
- package/workflows/systemic-bug-investigation.json +175 -174
- package/workflows/workflow-for-workflows.json +296 -262
|
@@ -1,264 +1,291 @@
|
|
|
1
1
|
{
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
{
|
|
21
|
-
"id": "phase-0-intelligent-triage",
|
|
22
|
-
"title": "Phase 0: Intelligent Triage & Path Selection",
|
|
23
|
-
"prompt": "**PREP**: Analyze the user's request to determine the appropriate complexity path.\n\n**IMPLEMENT**: Evaluate the request for complexity indicators:\n- **Simple Path**: Single ticket, clear requirements, minimal dependencies, straightforward implementation\n- **Standard Path**: Multiple related tickets, moderate complexity, some analysis needed, clear scope\n- **Epic Path**: Complex feature requiring decomposition, extensive planning, multiple teams/dependencies\n\n**VERIFY**: Document your path selection reasoning and set the pathComplexity context variable. Load any existing rules from `./.workflow_rules/ticket_creation.md` to follow team preferences.",
|
|
24
|
-
"agentRole": "You are an expert Product Manager and Mobile Tech Lead with extensive experience in feature scoping and project complexity assessment. Your role is to quickly and accurately classify requests based on scope, dependencies, and team impact while considering business priorities and technical constraints.",
|
|
25
|
-
"guidance": [
|
|
26
|
-
"Look for complexity indicators: scope size, unknowns, dependencies, team impact",
|
|
27
|
-
"Make the decision autonomously based on the request analysis",
|
|
28
|
-
"Set context variables that will be used in subsequent conditional steps"
|
|
29
|
-
],
|
|
30
|
-
"requireConfirmation": true
|
|
31
|
-
},
|
|
32
|
-
{
|
|
33
|
-
"id": "phase-a1-simple-ticket-gen",
|
|
34
|
-
"title": "Path A: Simple Ticket Generation",
|
|
35
|
-
"runCondition": {
|
|
36
|
-
"var": "pathComplexity",
|
|
37
|
-
"equals": "Simple"
|
|
38
|
-
},
|
|
39
|
-
"prompt": "**PREP**: Since this is a simple request, focus on creating a single high-quality ticket.\n\n**IMPLEMENT**: Generate a complete ticket with:\n- Clear, descriptive title following team conventions\n- Detailed description with sufficient context\n- Specific, testable acceptance criteria\n- Appropriate labels, priority, and story points\n- Any relevant links or attachments\n\n**VERIFY**: Review the ticket for completeness and clarity. This completes the Simple path workflow.",
|
|
40
|
-
"agentRole": "You are a skilled Product Manager focused on creating clear, actionable tickets for development teams. Your expertise lies in writing comprehensive ticket descriptions that provide developers with all necessary context while maintaining clarity and brevity.",
|
|
41
|
-
"validationCriteria": [
|
|
2
|
+
"id": "adaptive-ticket-creation",
|
|
3
|
+
"name": "Adaptive Ticket Creation Workflow",
|
|
4
|
+
"version": "0.1.0",
|
|
5
|
+
"description": "An intelligent workflow for creating high-quality Jira tickets. Uses LLM-driven path selection to automatically choose between Simple, Standard, or Epic complexity paths based on request analysis.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
"User has provided a clear objective for the ticket(s) to be created",
|
|
8
|
+
"Agent has access to relevant context (PRDs, Figma links, etc.) if available",
|
|
9
|
+
"Agent has file system access for persistent feedback mechanism",
|
|
10
|
+
"Agent can maintain context variables throughout the workflow"
|
|
11
|
+
],
|
|
12
|
+
"clarificationPrompts": [
|
|
13
|
+
"What is the main feature or task you want to implement?",
|
|
14
|
+
"Do you have any supporting documentation (PRDs, designs, specs)?",
|
|
15
|
+
"What are your team's Jira conventions or preferences?",
|
|
16
|
+
"Are there any specific constraints or requirements?",
|
|
17
|
+
"What is the expected timeline or priority level?"
|
|
18
|
+
],
|
|
19
|
+
"steps": [
|
|
42
20
|
{
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
21
|
+
"id": "phase-0-intelligent-triage",
|
|
22
|
+
"title": "Phase 0: Intelligent Triage & Path Selection",
|
|
23
|
+
"prompt": "**PREP**: Analyze the user's request to determine the appropriate complexity path.\n\n**IMPLEMENT**: Evaluate the request for complexity indicators:\n- **Simple Path**: Single ticket, clear requirements, minimal dependencies, straightforward implementation\n- **Standard Path**: Multiple related tickets, moderate complexity, some analysis needed, clear scope\n- **Epic Path**: Complex feature requiring decomposition, extensive planning, multiple teams/dependencies\n\n**VERIFY**: Document your path selection reasoning and set the pathComplexity context variable. Load any existing rules from `./.workflow_rules/ticket_creation.md` to follow team preferences.",
|
|
24
|
+
"agentRole": "You are an expert Product Manager and Mobile Tech Lead with extensive experience in feature scoping and project complexity assessment. Your role is to quickly and accurately classify requests based on scope, dependencies, and team impact while considering business priorities and technical constraints.",
|
|
25
|
+
"guidance": [
|
|
26
|
+
"Look for complexity indicators: scope size, unknowns, dependencies, team impact",
|
|
27
|
+
"Make the decision autonomously based on the request analysis",
|
|
28
|
+
"Set context variables that will be used in subsequent conditional steps"
|
|
29
|
+
],
|
|
30
|
+
"requireConfirmation": true
|
|
46
31
|
},
|
|
47
32
|
{
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
33
|
+
"id": "phase-a1-simple-ticket-gen",
|
|
34
|
+
"title": "Path A: Simple Ticket Generation",
|
|
35
|
+
"runCondition": {
|
|
36
|
+
"var": "pathComplexity",
|
|
37
|
+
"equals": "Simple"
|
|
38
|
+
},
|
|
39
|
+
"prompt": "**PREP**: Since this is a simple request, focus on creating a single high-quality ticket.\n\n**IMPLEMENT**: Generate a complete ticket with:\n- Clear, descriptive title following team conventions\n- Detailed description with sufficient context\n- Specific, testable acceptance criteria\n- Appropriate labels, priority, and story points\n- Any relevant links or attachments\n\n**VERIFY**: Review the ticket for completeness and clarity. This completes the Simple path workflow.",
|
|
40
|
+
"agentRole": "You are a skilled Product Manager focused on creating clear, actionable tickets for development teams. Your expertise lies in writing comprehensive ticket descriptions that provide developers with all necessary context while maintaining clarity and brevity.",
|
|
41
|
+
"validationCriteria": [
|
|
42
|
+
{
|
|
43
|
+
"type": "regex",
|
|
44
|
+
"pattern": "(?i)##?\\s*Title:?",
|
|
45
|
+
"message": "Ticket must include a clear title (e.g., 'Title:' or '## Title')"
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"type": "regex",
|
|
49
|
+
"pattern": "(?i)##?\\s*Description:?",
|
|
50
|
+
"message": "Ticket must include a detailed description (e.g., 'Description:' or '## Description')"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"type": "regex",
|
|
54
|
+
"pattern": "(?i)##?\\s*Acceptance Criteria:?",
|
|
55
|
+
"message": "Ticket must include specific acceptance criteria (e.g., 'Acceptance Criteria:' or '## Acceptance Criteria')"
|
|
56
|
+
},
|
|
57
|
+
{
|
|
58
|
+
"type": "regex",
|
|
59
|
+
"pattern": "\\[\\s*\\].{5,}",
|
|
60
|
+
"message": "Acceptance criteria should include checkboxes followed by descriptive text (at least 5 characters)."
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"type": "length",
|
|
64
|
+
"min": 300,
|
|
65
|
+
"max": 2000,
|
|
66
|
+
"message": "Ticket should be between 300-2000 characters for adequate detail"
|
|
67
|
+
}
|
|
68
|
+
],
|
|
69
|
+
"guidance": [
|
|
70
|
+
"This is the complete fast track - workflow ends after this step",
|
|
71
|
+
"Focus on quality over quantity - one excellent ticket",
|
|
72
|
+
"Include all necessary context for the developer"
|
|
73
|
+
],
|
|
74
|
+
"requireConfirmation": true,
|
|
75
|
+
"hasValidation": true
|
|
51
76
|
},
|
|
52
77
|
{
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
78
|
+
"id": "phase-c0-context-priming",
|
|
79
|
+
"title": "Path C, Phase 0: Comprehensive Context Gathering",
|
|
80
|
+
"runCondition": {
|
|
81
|
+
"or": [
|
|
82
|
+
{
|
|
83
|
+
"var": "pathComplexity",
|
|
84
|
+
"equals": "Standard"
|
|
85
|
+
},
|
|
86
|
+
{
|
|
87
|
+
"var": "pathComplexity",
|
|
88
|
+
"equals": "Epic"
|
|
89
|
+
}
|
|
90
|
+
]
|
|
91
|
+
},
|
|
92
|
+
"prompt": "**PREP**: Gather comprehensive context for this complex project.\n\n**IMPLEMENT**: Collect and analyze all available project materials:\n- Load existing rules from `./.workflow_rules/ticket_creation.md`\n- Review provided PRDs, technical specs, and design documents\n- Understand team conventions and Jira formatting preferences\n- Identify key stakeholders and dependencies\n- Note any constraints or special requirements\n\n**VERIFY**: Confirm you have sufficient context to proceed with analysis. Document any missing information that would be critical for planning.",
|
|
93
|
+
"agentRole": "You are a thorough business analyst specializing in requirements gathering and stakeholder management. Your expertise lies in comprehensively understanding project context, identifying information gaps, and ensuring all necessary documentation is available before proceeding with detailed planning.",
|
|
94
|
+
"guidance": [
|
|
95
|
+
"Thorough context gathering is critical for complex projects",
|
|
96
|
+
"Don't proceed without sufficient information",
|
|
97
|
+
"Set context variables for team conventions and project details"
|
|
98
|
+
],
|
|
99
|
+
"askForFiles": true,
|
|
100
|
+
"requireConfirmation": true
|
|
56
101
|
},
|
|
57
102
|
{
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
103
|
+
"id": "phase-c1-analysis-and-questions",
|
|
104
|
+
"title": "Path C, Phase 1: Analysis & Risk Identification",
|
|
105
|
+
"runCondition": {
|
|
106
|
+
"or": [
|
|
107
|
+
{
|
|
108
|
+
"var": "pathComplexity",
|
|
109
|
+
"equals": "Standard"
|
|
110
|
+
},
|
|
111
|
+
{
|
|
112
|
+
"var": "pathComplexity",
|
|
113
|
+
"equals": "Epic"
|
|
114
|
+
}
|
|
115
|
+
]
|
|
116
|
+
},
|
|
117
|
+
"prompt": "**PREP**: Analyze all provided context to identify ambiguities, risks, and missing information.\n\n**IMPLEMENT**: Create a structured analysis:\n- Identify unclear requirements or acceptance criteria\n- Highlight potential technical risks or blockers\n- Note missing information that could impact planning\n- Flag any conflicting requirements or constraints\n- Assess feasibility and effort implications\n\n**VERIFY**: Present findings as prioritized questions or clarifications needed. Only proceed when critical ambiguities are resolved.",
|
|
118
|
+
"agentRole": "You are a risk assessment specialist and requirements analyst with expertise in identifying project risks, ambiguities, and potential blockers. Your role is to proactively surface issues that could derail project success while ensuring all requirements are clearly understood.",
|
|
119
|
+
"guidance": [
|
|
120
|
+
"This is a critical risk reduction step",
|
|
121
|
+
"Better to ask questions now than discover issues later",
|
|
122
|
+
"Focus on blockers and high-impact unknowns"
|
|
123
|
+
],
|
|
124
|
+
"requireConfirmation": true
|
|
61
125
|
},
|
|
62
126
|
{
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
"agentRole": "You are a strategic Product Manager and project planner with expertise in feature decomposition and scope management. Your strength lies in creating comprehensive project plans that balance business objectives with technical feasibility while preventing scope creep.",
|
|
124
|
-
"validationCriteria": [
|
|
125
|
-
{
|
|
126
|
-
"type": "regex",
|
|
127
|
-
"pattern": "(?i)##?\\s*Project Summary:?",
|
|
128
|
-
"message": "Plan must include a Project Summary section"
|
|
129
|
-
},
|
|
130
|
-
{
|
|
131
|
-
"type": "regex",
|
|
132
|
-
"pattern": "(?i)##?\\s*Key Deliverables:?",
|
|
133
|
-
"message": "Plan must include a Key Deliverables section"
|
|
134
|
-
},
|
|
135
|
-
{
|
|
136
|
-
"type": "regex",
|
|
137
|
-
"pattern": "(?i)##?\\s*In-Scope:?",
|
|
138
|
-
"message": "Plan must explicitly define In-Scope items"
|
|
139
|
-
},
|
|
140
|
-
{
|
|
141
|
-
"type": "regex",
|
|
142
|
-
"pattern": "(?i)##?\\s*Out-of-Scope:?",
|
|
143
|
-
"message": "Plan must explicitly define Out-of-Scope items"
|
|
144
|
-
},
|
|
145
|
-
{
|
|
146
|
-
"type": "regex",
|
|
147
|
-
"pattern": "(?i)##?\\s*Success Criteria:?",
|
|
148
|
-
"message": "Plan must include measurable Success Criteria"
|
|
127
|
+
"id": "phase-c2-high-level-plan",
|
|
128
|
+
"title": "Path C, Phase 2: Create High-Level Plan",
|
|
129
|
+
"runCondition": {
|
|
130
|
+
"or": [
|
|
131
|
+
{
|
|
132
|
+
"var": "pathComplexity",
|
|
133
|
+
"equals": "Standard"
|
|
134
|
+
},
|
|
135
|
+
{
|
|
136
|
+
"var": "pathComplexity",
|
|
137
|
+
"equals": "Epic"
|
|
138
|
+
}
|
|
139
|
+
]
|
|
140
|
+
},
|
|
141
|
+
"prompt": "**PREP**: With clarified requirements, create a comprehensive high-level plan.\n\n**IMPLEMENT**: Generate a structured plan document:\n- **Project Summary**: Clear overview of the feature/project\n- **Key Deliverables**: Main components or features to be built\n- **In-Scope**: Explicitly defined scope boundaries\n- **Out-of-Scope**: Clear exclusions to prevent scope creep\n- **Success Criteria**: Measurable definition of done\n- **High-Level Timeline**: Major milestones and phases\n\n**VERIFY**: Ensure the plan is comprehensive and aligns with the original request. This plan will guide ticket creation.",
|
|
142
|
+
"agentRole": "You are a strategic Product Manager and project planner with expertise in feature decomposition and scope management. Your strength lies in creating comprehensive project plans that balance business objectives with technical feasibility while preventing scope creep.",
|
|
143
|
+
"validationCriteria": [
|
|
144
|
+
{
|
|
145
|
+
"type": "regex",
|
|
146
|
+
"pattern": "(?i)##?\\s*Project Summary:?",
|
|
147
|
+
"message": "Plan must include a Project Summary section"
|
|
148
|
+
},
|
|
149
|
+
{
|
|
150
|
+
"type": "regex",
|
|
151
|
+
"pattern": "(?i)##?\\s*Key Deliverables:?",
|
|
152
|
+
"message": "Plan must include a Key Deliverables section"
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"type": "regex",
|
|
156
|
+
"pattern": "(?i)##?\\s*In-Scope:?",
|
|
157
|
+
"message": "Plan must explicitly define In-Scope items"
|
|
158
|
+
},
|
|
159
|
+
{
|
|
160
|
+
"type": "regex",
|
|
161
|
+
"pattern": "(?i)##?\\s*Out-of-Scope:?",
|
|
162
|
+
"message": "Plan must explicitly define Out-of-Scope items"
|
|
163
|
+
},
|
|
164
|
+
{
|
|
165
|
+
"type": "regex",
|
|
166
|
+
"pattern": "(?i)##?\\s*Success Criteria:?",
|
|
167
|
+
"message": "Plan must include measurable Success Criteria"
|
|
168
|
+
},
|
|
169
|
+
{
|
|
170
|
+
"type": "regex",
|
|
171
|
+
"pattern": "(?i)##?\\s*High-Level Timeline:?",
|
|
172
|
+
"message": "Plan must include a High-Level Timeline section"
|
|
173
|
+
},
|
|
174
|
+
{
|
|
175
|
+
"type": "length",
|
|
176
|
+
"min": 800,
|
|
177
|
+
"message": "Plan should be at least 800 characters for comprehensive coverage"
|
|
178
|
+
}
|
|
179
|
+
],
|
|
180
|
+
"guidance": [
|
|
181
|
+
"This plan becomes the foundation for all ticket generation",
|
|
182
|
+
"Be explicit about scope to prevent misunderstandings",
|
|
183
|
+
"For Standard path, this leads directly to ticket generation"
|
|
184
|
+
],
|
|
185
|
+
"requireConfirmation": true,
|
|
186
|
+
"hasValidation": true
|
|
149
187
|
},
|
|
150
188
|
{
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
],
|
|
166
|
-
"requireConfirmation": true
|
|
167
|
-
},
|
|
168
|
-
{
|
|
169
|
-
"id": "phase-c3a-epic-decomposition",
|
|
170
|
-
"title": "Path C, Phase 3a: Epic Decomposition",
|
|
171
|
-
"runCondition": {
|
|
172
|
-
"var": "pathComplexity",
|
|
173
|
-
"equals": "Epic"
|
|
174
|
-
},
|
|
175
|
-
"prompt": "**PREP**: Decompose the approved high-level plan into a logical hierarchy.\n\n**IMPLEMENT**: Create a structured breakdown:\n- **Epic**: Main feature/project container\n- **Features/Stories**: Logical groupings of related functionality\n- **Tasks**: Specific implementation work items\n- **Dependencies**: Clear relationships between items\n- **Rationale**: Explain the decomposition logic and groupings\n\n**VERIFY**: Ensure the hierarchy is logical, dependencies are clear, and nothing is missed from the original plan.",
|
|
176
|
-
"agentRole": "You are a technical Product Manager specializing in epic decomposition and story mapping. Your expertise lies in breaking down complex features into logical, manageable work items while maintaining clear dependencies and ensuring nothing falls through the cracks.",
|
|
177
|
-
"guidance": [
|
|
178
|
-
"Epic path only - creates the story hierarchy",
|
|
179
|
-
"Focus on logical groupings that make sense for development",
|
|
180
|
-
"Consider team capacity and parallel work opportunities"
|
|
181
|
-
],
|
|
182
|
-
"requireConfirmation": true
|
|
183
|
-
},
|
|
184
|
-
{
|
|
185
|
-
"id": "phase-c3b-estimation-and-dependencies",
|
|
186
|
-
"title": "Path C, Phase 3b: Estimation & Dependency Mapping",
|
|
187
|
-
"runCondition": {
|
|
188
|
-
"var": "pathComplexity",
|
|
189
|
-
"equals": "Epic"
|
|
190
|
-
},
|
|
191
|
-
"prompt": "**PREP**: Add effort estimates and dependency mapping to the decomposed stories.\n\n**IMPLEMENT**: For each story, provide:\n- **Effort Estimate**: S/M/L/XL sizing with detailed justification\n- **Dependencies**: Prerequisites and blockers\n- **Risk Assessment**: Technical or business risks\n- **Priority Ranking**: Relative importance and sequencing\n- **Team Assignment**: Suggested team or skill requirements\n\n**VERIFY**: Review estimates for consistency and identify any oversized stories that need further breakdown.",
|
|
192
|
-
"agentRole": "You are a technical project manager with expertise in agile estimation and dependency management. Your strength lies in accurately sizing work items, identifying critical path dependencies, and ensuring realistic project planning that accounts for team capacity and technical constraints.",
|
|
193
|
-
"guidance": [
|
|
194
|
-
"Epic path only - adds planning details",
|
|
195
|
-
"Conservative estimates are better than optimistic ones",
|
|
196
|
-
"Identify critical path items and potential bottlenecks"
|
|
197
|
-
],
|
|
198
|
-
"requireConfirmation": true
|
|
199
|
-
},
|
|
200
|
-
{
|
|
201
|
-
"id": "phase-c4-batch-ticket-generation",
|
|
202
|
-
"title": "Path C, Phase 4: Batch Ticket Generation",
|
|
203
|
-
"runCondition": {
|
|
204
|
-
"or": [
|
|
205
|
-
{"var": "pathComplexity", "equals": "Standard"},
|
|
206
|
-
{"var": "pathComplexity", "equals": "Epic"}
|
|
207
|
-
]
|
|
208
|
-
},
|
|
209
|
-
"prompt": "**PREP**: Generate all necessary Jira tickets based on the approved plan.\n\n**IMPLEMENT**: Create comprehensive tickets for every story/task:\n- **Epic Ticket**: Overall project container (Epic path only)\n- **Feature/Story Tickets**: Individual work items with full details\n- **Consistent Formatting**: Follow team conventions and templates\n- **Complete Information**: Title, description, acceptance criteria, labels, estimates\n- **Proper Linking**: Dependencies and epic relationships\n\n**VERIFY**: Review all tickets for completeness, consistency, and accuracy. Present the full batch for approval.",
|
|
210
|
-
"agentRole": "You are an experienced Product Manager specializing in high-volume ticket creation and project organization. Your expertise lies in creating comprehensive, well-structured tickets that provide development teams with clear, actionable work items while maintaining consistency across large projects.",
|
|
211
|
-
"validationCriteria": [
|
|
212
|
-
{
|
|
213
|
-
"type": "regex",
|
|
214
|
-
"pattern": "(?i)##\\s*(Ticket\\s*\\d+|Epic)",
|
|
215
|
-
"message": "Output must contain multiple numbered tickets (e.g., '## Ticket 1') or an Epic ('## Epic')"
|
|
189
|
+
"id": "phase-c3a-epic-decomposition",
|
|
190
|
+
"title": "Path C, Phase 3a: Epic Decomposition",
|
|
191
|
+
"runCondition": {
|
|
192
|
+
"var": "pathComplexity",
|
|
193
|
+
"equals": "Epic"
|
|
194
|
+
},
|
|
195
|
+
"prompt": "**PREP**: Decompose the approved high-level plan into a logical hierarchy.\n\n**IMPLEMENT**: Create a structured breakdown:\n- **Epic**: Main feature/project container\n- **Features/Stories**: Logical groupings of related functionality\n- **Tasks**: Specific implementation work items\n- **Dependencies**: Clear relationships between items\n- **Rationale**: Explain the decomposition logic and groupings\n\n**VERIFY**: Ensure the hierarchy is logical, dependencies are clear, and nothing is missed from the original plan.",
|
|
196
|
+
"agentRole": "You are a technical Product Manager specializing in epic decomposition and story mapping. Your expertise lies in breaking down complex features into logical, manageable work items while maintaining clear dependencies and ensuring nothing falls through the cracks.",
|
|
197
|
+
"guidance": [
|
|
198
|
+
"Epic path only - creates the story hierarchy",
|
|
199
|
+
"Focus on logical groupings that make sense for development",
|
|
200
|
+
"Consider team capacity and parallel work opportunities"
|
|
201
|
+
],
|
|
202
|
+
"requireConfirmation": true
|
|
216
203
|
},
|
|
217
204
|
{
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
205
|
+
"id": "phase-c3b-estimation-and-dependencies",
|
|
206
|
+
"title": "Path C, Phase 3b: Estimation & Dependency Mapping",
|
|
207
|
+
"runCondition": {
|
|
208
|
+
"var": "pathComplexity",
|
|
209
|
+
"equals": "Epic"
|
|
210
|
+
},
|
|
211
|
+
"prompt": "**PREP**: Add effort estimates and dependency mapping to the decomposed stories.\n\n**IMPLEMENT**: For each story, provide:\n- **Effort Estimate**: S/M/L/XL sizing with detailed justification\n- **Dependencies**: Prerequisites and blockers\n- **Risk Assessment**: Technical or business risks\n- **Priority Ranking**: Relative importance and sequencing\n- **Team Assignment**: Suggested team or skill requirements\n\n**VERIFY**: Review estimates for consistency and identify any oversized stories that need further breakdown.",
|
|
212
|
+
"agentRole": "You are a technical project manager with expertise in agile estimation and dependency management. Your strength lies in accurately sizing work items, identifying critical path dependencies, and ensuring realistic project planning that accounts for team capacity and technical constraints.",
|
|
213
|
+
"guidance": [
|
|
214
|
+
"Epic path only - adds planning details",
|
|
215
|
+
"Conservative estimates are better than optimistic ones",
|
|
216
|
+
"Identify critical path items and potential bottlenecks"
|
|
217
|
+
],
|
|
218
|
+
"requireConfirmation": true
|
|
221
219
|
},
|
|
222
220
|
{
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
221
|
+
"id": "phase-c4-batch-ticket-generation",
|
|
222
|
+
"title": "Path C, Phase 4: Batch Ticket Generation",
|
|
223
|
+
"runCondition": {
|
|
224
|
+
"or": [
|
|
225
|
+
{
|
|
226
|
+
"var": "pathComplexity",
|
|
227
|
+
"equals": "Standard"
|
|
228
|
+
},
|
|
229
|
+
{
|
|
230
|
+
"var": "pathComplexity",
|
|
231
|
+
"equals": "Epic"
|
|
232
|
+
}
|
|
233
|
+
]
|
|
234
|
+
},
|
|
235
|
+
"prompt": "**PREP**: Generate all necessary Jira tickets based on the approved plan.\n\n**IMPLEMENT**: Create comprehensive tickets for every story/task:\n- **Epic Ticket**: Overall project container (Epic path only)\n- **Feature/Story Tickets**: Individual work items with full details\n- **Consistent Formatting**: Follow team conventions and templates\n- **Complete Information**: Title, description, acceptance criteria, labels, estimates\n- **Proper Linking**: Dependencies and epic relationships\n\n**VERIFY**: Review all tickets for completeness, consistency, and accuracy. Present the full batch for approval.",
|
|
236
|
+
"agentRole": "You are an experienced Product Manager specializing in high-volume ticket creation and project organization. Your expertise lies in creating comprehensive, well-structured tickets that provide development teams with clear, actionable work items while maintaining consistency across large projects.",
|
|
237
|
+
"validationCriteria": [
|
|
238
|
+
{
|
|
239
|
+
"type": "regex",
|
|
240
|
+
"pattern": "(?i)##\\s*(Ticket\\s*\\d+|Epic)",
|
|
241
|
+
"message": "Output must contain multiple numbered tickets (e.g., '## Ticket 1') or an Epic ('## Epic')"
|
|
242
|
+
},
|
|
243
|
+
{
|
|
244
|
+
"type": "regex",
|
|
245
|
+
"pattern": "(?i)Story Points?:",
|
|
246
|
+
"message": "Tickets should include story point estimates"
|
|
247
|
+
},
|
|
248
|
+
{
|
|
249
|
+
"type": "regex",
|
|
250
|
+
"pattern": "(?i)Priority:",
|
|
251
|
+
"message": "Tickets should include priority levels"
|
|
252
|
+
},
|
|
253
|
+
{
|
|
254
|
+
"type": "length",
|
|
255
|
+
"min": 1000,
|
|
256
|
+
"message": "Batch ticket output should be substantial (1000+ characters) for multiple tickets"
|
|
257
|
+
}
|
|
258
|
+
],
|
|
259
|
+
"guidance": [
|
|
260
|
+
"Automated batch generation saves significant time",
|
|
261
|
+
"Ensure consistency across all tickets",
|
|
262
|
+
"Include all necessary metadata and relationships"
|
|
263
|
+
],
|
|
264
|
+
"requireConfirmation": true,
|
|
265
|
+
"hasValidation": true
|
|
226
266
|
},
|
|
227
267
|
{
|
|
228
|
-
|
|
229
|
-
|
|
230
|
-
|
|
268
|
+
"id": "phase-c5-continuous-improvement",
|
|
269
|
+
"title": "Path C, Phase 5: Continuous Improvement & Learning",
|
|
270
|
+
"runCondition": {
|
|
271
|
+
"var": "pathComplexity",
|
|
272
|
+
"equals": "Epic"
|
|
273
|
+
},
|
|
274
|
+
"prompt": "**PREP**: Capture lessons learned and improve future ticket creation.\n\n**IMPLEMENT**: Based on feedback from the ticket review:\n- **Identify Patterns**: What worked well vs. what could be improved\n- **Extract Rules**: Formulate specific operational guidelines\n- **Document Preferences**: Team-specific conventions and requirements\n- **Update Rules File**: Append new rules to `./.workflow_rules/ticket_creation.md`\n- **Validate Learning**: Confirm the new rules make sense for future projects\n\n**VERIFY**: Ensure the persistent rules will improve future ticket creation quality and consistency.",
|
|
275
|
+
"agentRole": "You are a process improvement specialist and organizational learning expert. Your role is to extract actionable insights from project experiences and codify them into reusable guidelines that improve team efficiency and consistency over time.",
|
|
276
|
+
"guidance": [
|
|
277
|
+
"Epic path only - creates persistent learning",
|
|
278
|
+
"Focus on actionable, specific rules",
|
|
279
|
+
"This makes the AI smarter over time"
|
|
280
|
+
],
|
|
281
|
+
"requireConfirmation": true
|
|
231
282
|
}
|
|
232
|
-
|
|
233
|
-
|
|
234
|
-
"
|
|
235
|
-
"
|
|
236
|
-
"
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
"id": "phase-c5-continuous-improvement",
|
|
242
|
-
"title": "Path C, Phase 5: Continuous Improvement & Learning",
|
|
243
|
-
"runCondition": {
|
|
244
|
-
"var": "pathComplexity",
|
|
245
|
-
"equals": "Epic"
|
|
246
|
-
},
|
|
247
|
-
"prompt": "**PREP**: Capture lessons learned and improve future ticket creation.\n\n**IMPLEMENT**: Based on feedback from the ticket review:\n- **Identify Patterns**: What worked well vs. what could be improved\n- **Extract Rules**: Formulate specific operational guidelines\n- **Document Preferences**: Team-specific conventions and requirements\n- **Update Rules File**: Append new rules to `./.workflow_rules/ticket_creation.md`\n- **Validate Learning**: Confirm the new rules make sense for future projects\n\n**VERIFY**: Ensure the persistent rules will improve future ticket creation quality and consistency.",
|
|
248
|
-
"agentRole": "You are a process improvement specialist and organizational learning expert. Your role is to extract actionable insights from project experiences and codify them into reusable guidelines that improve team efficiency and consistency over time.",
|
|
249
|
-
"guidance": [
|
|
250
|
-
"Epic path only - creates persistent learning",
|
|
251
|
-
"Focus on actionable, specific rules",
|
|
252
|
-
"This makes the AI smarter over time"
|
|
253
|
-
],
|
|
254
|
-
"requireConfirmation": true
|
|
255
|
-
}
|
|
256
|
-
],
|
|
257
|
-
"metaGuidance": [
|
|
258
|
-
"Maintain the persona of an expert Product Manager and Mobile Tech Lead",
|
|
259
|
-
"Make autonomous decisions based on context analysis rather than asking users to choose",
|
|
260
|
-
"Always load and follow team-specific rules from ./.workflow_rules/ticket_creation.md when available",
|
|
261
|
-
"Focus on creating tickets that provide clear value to development teams",
|
|
262
|
-
"Ensure all tickets have measurable acceptance criteria and appropriate estimates"
|
|
263
|
-
]
|
|
264
|
-
}
|
|
283
|
+
],
|
|
284
|
+
"metaGuidance": [
|
|
285
|
+
"Maintain the persona of an expert Product Manager and Mobile Tech Lead",
|
|
286
|
+
"Make autonomous decisions based on context analysis rather than asking users to choose",
|
|
287
|
+
"Always load and follow team-specific rules from ./.workflow_rules/ticket_creation.md when available",
|
|
288
|
+
"Focus on creating tickets that provide clear value to development teams",
|
|
289
|
+
"Ensure all tickets have measurable acceptance criteria and appropriate estimates"
|
|
290
|
+
]
|
|
291
|
+
}
|