@defai.digital/cli 13.4.3 → 13.4.5
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/bundled/agents/aerospace-scientist.json +114 -0
- package/bundled/agents/architecture.json +96 -0
- package/bundled/agents/backend.json +125 -0
- package/bundled/agents/blockchain-developer.json +114 -0
- package/bundled/agents/ceo.json +113 -0
- package/bundled/agents/creative-marketer.json +114 -0
- package/bundled/agents/cto.json +96 -0
- package/bundled/agents/data-scientist.json +96 -0
- package/bundled/agents/devops.json +98 -0
- package/bundled/agents/frontend.json +118 -0
- package/bundled/agents/fullstack.json +99 -0
- package/bundled/agents/ml-engineer.json +114 -0
- package/bundled/agents/mlops-engineer.json +102 -0
- package/bundled/agents/mobile.json +96 -0
- package/bundled/agents/product.json +96 -0
- package/bundled/agents/quality.json +95 -0
- package/bundled/agents/quantum-engineer.json +114 -0
- package/bundled/agents/researcher.json +123 -0
- package/bundled/agents/reviewer.json +107 -0
- package/bundled/agents/security.json +79 -0
- package/bundled/agents/standard.json +82 -0
- package/bundled/agents/writer.json +78 -0
- package/bundled/templates/monorepo/contract-index.ts.hbs +7 -0
- package/bundled/templates/monorepo/contract-test.ts.hbs +130 -0
- package/bundled/templates/monorepo/contracts-package.json.hbs +29 -0
- package/bundled/templates/monorepo/domain-index.ts.hbs +115 -0
- package/bundled/templates/monorepo/domain-package.json.hbs +27 -0
- package/bundled/templates/monorepo/gitignore.hbs +32 -0
- package/bundled/templates/monorepo/invariants.md.hbs +43 -0
- package/bundled/templates/monorepo/package.json.hbs +28 -0
- package/bundled/templates/monorepo/pnpm-workspace.yaml.hbs +5 -0
- package/bundled/templates/monorepo/schema.ts.hbs +82 -0
- package/bundled/templates/monorepo/template.json +106 -0
- package/bundled/templates/monorepo/tsconfig.json.hbs +22 -0
- package/bundled/templates/standalone/contract-index.ts.hbs +5 -0
- package/bundled/templates/standalone/contract-test.ts.hbs +95 -0
- package/bundled/templates/standalone/contracts-root-index.ts.hbs +7 -0
- package/bundled/templates/standalone/domain-index.ts.hbs +6 -0
- package/bundled/templates/standalone/domain-repository.ts.hbs +44 -0
- package/bundled/templates/standalone/domain-service.ts.hbs +102 -0
- package/bundled/templates/standalone/gitignore.hbs +27 -0
- package/bundled/templates/standalone/invariants.md.hbs +35 -0
- package/bundled/templates/standalone/package.json.hbs +41 -0
- package/bundled/templates/standalone/schema.ts.hbs +61 -0
- package/bundled/templates/standalone/src-index.ts.hbs +11 -0
- package/bundled/templates/standalone/template.json +91 -0
- package/bundled/templates/standalone/tsconfig.json.hbs +20 -0
- package/bundled/templates/standalone/vitest.config.ts.hbs +8 -0
- package/bundled/workflows/adversarial-debate.yaml +222 -0
- package/bundled/workflows/analyst.yaml +115 -0
- package/bundled/workflows/assistant.yaml +74 -0
- package/bundled/workflows/code-review-discussion.yaml +166 -0
- package/bundled/workflows/code-reviewer.yaml +94 -0
- package/bundled/workflows/contract-first-project.yaml +356 -0
- package/bundled/workflows/debugger.yaml +107 -0
- package/bundled/workflows/designer.yaml +113 -0
- package/bundled/workflows/developer.yaml +105 -0
- package/bundled/workflows/discuss-step-examples.yaml +153 -0
- package/bundled/workflows/infrastructure-automation.yaml +283 -0
- package/bundled/workflows/ml-ab-testing.yaml +311 -0
- package/bundled/workflows/ml-experiment-tracker.yaml +150 -0
- package/bundled/workflows/ml-feature-engineering.yaml +242 -0
- package/bundled/workflows/ml-model-evaluation.yaml +234 -0
- package/bundled/workflows/ml-model-monitoring.yaml +227 -0
- package/bundled/workflows/ml-model-registry.yaml +232 -0
- package/bundled/workflows/mlops-deployment.yaml +267 -0
- package/bundled/workflows/mobile-development.yaml +312 -0
- package/bundled/workflows/multi-model-discussion.yaml +243 -0
- package/bundled/workflows/product-discovery.yaml +295 -0
- package/bundled/workflows/qa-specialist.yaml +116 -0
- package/bundled/workflows/refactoring.yaml +105 -0
- package/bundled/workflows/security-audit.yaml +135 -0
- package/bundled/workflows/std/analysis.yaml +190 -0
- package/bundled/workflows/std/code-review.yaml +117 -0
- package/bundled/workflows/std/debugging.yaml +155 -0
- package/bundled/workflows/std/documentation.yaml +180 -0
- package/bundled/workflows/std/implementation.yaml +197 -0
- package/bundled/workflows/std/refactoring.yaml +180 -0
- package/bundled/workflows/std/testing.yaml +200 -0
- package/bundled/workflows/strategic-planning.yaml +235 -0
- package/bundled/workflows/technology-research.yaml +239 -0
- package/dist/commands/agent.d.ts.map +1 -1
- package/dist/commands/agent.js +8 -2
- package/dist/commands/agent.js.map +1 -1
- package/dist/commands/scaffold.d.ts.map +1 -1
- package/dist/commands/scaffold.js +6 -3
- package/dist/commands/scaffold.js.map +1 -1
- package/dist/web/api.d.ts.map +1 -1
- package/dist/web/api.js +13 -6
- package/dist/web/api.js.map +1 -1
- package/package.json +23 -22
|
@@ -0,0 +1,243 @@
|
|
|
1
|
+
# Multi-Model Discussion Workflow
|
|
2
|
+
#
|
|
3
|
+
# This workflow enables multiple LLM providers to discuss a topic,
|
|
4
|
+
# building on each other's insights to reach a richer conclusion
|
|
5
|
+
# than any single model could provide.
|
|
6
|
+
#
|
|
7
|
+
# Usage:
|
|
8
|
+
# ax run multi-model-discussion --input '{"topic": "Best architecture for real-time chat"}'
|
|
9
|
+
#
|
|
10
|
+
# Supported providers: claude, gemini, codex, grok
|
|
11
|
+
#
|
|
12
|
+
# Provider Strengths:
|
|
13
|
+
# - Claude: Nuanced reasoning, synthesis (used as synthesizer)
|
|
14
|
+
# - Gemini: Research, long context (1M+ tokens)
|
|
15
|
+
# - Codex: Code generation, OpenAI ecosystem
|
|
16
|
+
# - Grok: Real-time info, reasoning, research
|
|
17
|
+
|
|
18
|
+
workflowId: multi-model-discussion
|
|
19
|
+
version: "1.0.0"
|
|
20
|
+
name: Multi-Model Discussion
|
|
21
|
+
description: >
|
|
22
|
+
Multiple AI models discuss a topic from their unique perspectives,
|
|
23
|
+
then synthesize into a unified conclusion. Leverages cognitive
|
|
24
|
+
diversity of different LLMs for more robust outcomes.
|
|
25
|
+
|
|
26
|
+
steps:
|
|
27
|
+
# Step 1: Gather initial perspectives from each model in parallel
|
|
28
|
+
- stepId: gather-perspectives
|
|
29
|
+
type: parallel
|
|
30
|
+
name: Gather Diverse Perspectives
|
|
31
|
+
timeout: 120000
|
|
32
|
+
config:
|
|
33
|
+
failureStrategy: failSafe # Continue even if one provider fails
|
|
34
|
+
steps:
|
|
35
|
+
- stepId: claude-perspective
|
|
36
|
+
type: prompt
|
|
37
|
+
config:
|
|
38
|
+
provider: claude
|
|
39
|
+
prompt: |
|
|
40
|
+
You are Claude, known for nuanced reasoning and careful analysis.
|
|
41
|
+
|
|
42
|
+
Topic for discussion: {{input.topic}}
|
|
43
|
+
|
|
44
|
+
Provide your unique perspective on this topic. Focus on:
|
|
45
|
+
- Nuanced considerations others might miss
|
|
46
|
+
- Ethical and safety implications
|
|
47
|
+
- Long-term consequences
|
|
48
|
+
|
|
49
|
+
Be thorough but concise.
|
|
50
|
+
|
|
51
|
+
- stepId: grok-perspective
|
|
52
|
+
type: prompt
|
|
53
|
+
config:
|
|
54
|
+
provider: grok
|
|
55
|
+
prompt: |
|
|
56
|
+
You are Grok, known for real-time information, reasoning, and research.
|
|
57
|
+
|
|
58
|
+
Topic for discussion: {{input.topic}}
|
|
59
|
+
|
|
60
|
+
Provide your unique perspective on this topic. Focus on:
|
|
61
|
+
- Current trends and real-time information
|
|
62
|
+
- Practical reasoning and analysis
|
|
63
|
+
- Research-based evidence
|
|
64
|
+
- Critical evaluation of approaches
|
|
65
|
+
|
|
66
|
+
Be thorough but concise.
|
|
67
|
+
|
|
68
|
+
- stepId: gemini-perspective
|
|
69
|
+
type: prompt
|
|
70
|
+
config:
|
|
71
|
+
provider: gemini
|
|
72
|
+
prompt: |
|
|
73
|
+
You are Gemini, known for broad research and long-context understanding.
|
|
74
|
+
|
|
75
|
+
Topic for discussion: {{input.topic}}
|
|
76
|
+
|
|
77
|
+
Provide your unique perspective on this topic. Focus on:
|
|
78
|
+
- Latest trends and research
|
|
79
|
+
- Real-world examples and case studies
|
|
80
|
+
- Large-scale system considerations
|
|
81
|
+
|
|
82
|
+
Be thorough but concise.
|
|
83
|
+
|
|
84
|
+
# Step 2: Cross-pollinate ideas - each model responds to others
|
|
85
|
+
- stepId: cross-discuss
|
|
86
|
+
type: parallel
|
|
87
|
+
name: Cross-Discussion Round
|
|
88
|
+
timeout: 120000
|
|
89
|
+
dependencies:
|
|
90
|
+
- gather-perspectives
|
|
91
|
+
config:
|
|
92
|
+
failureStrategy: failSafe
|
|
93
|
+
steps:
|
|
94
|
+
- stepId: claude-responds
|
|
95
|
+
type: prompt
|
|
96
|
+
config:
|
|
97
|
+
provider: claude
|
|
98
|
+
prompt: |
|
|
99
|
+
Review these perspectives from other AI models:
|
|
100
|
+
|
|
101
|
+
## Grok's Perspective (Real-time Research Expert):
|
|
102
|
+
{{steps.grok-perspective.output}}
|
|
103
|
+
|
|
104
|
+
## Gemini's Perspective (Research Expert):
|
|
105
|
+
{{steps.gemini-perspective.output}}
|
|
106
|
+
|
|
107
|
+
Now respond:
|
|
108
|
+
1. What do you agree with?
|
|
109
|
+
2. What do you respectfully disagree with? Why?
|
|
110
|
+
3. What important points were missed?
|
|
111
|
+
4. How can these perspectives be combined?
|
|
112
|
+
|
|
113
|
+
- stepId: grok-responds
|
|
114
|
+
type: prompt
|
|
115
|
+
config:
|
|
116
|
+
provider: grok
|
|
117
|
+
prompt: |
|
|
118
|
+
Review these perspectives from other AI models:
|
|
119
|
+
|
|
120
|
+
## Claude's Perspective (Reasoning Expert):
|
|
121
|
+
{{steps.claude-perspective.output}}
|
|
122
|
+
|
|
123
|
+
## Gemini's Perspective (Research Expert):
|
|
124
|
+
{{steps.gemini-perspective.output}}
|
|
125
|
+
|
|
126
|
+
Now respond:
|
|
127
|
+
1. What do you agree with?
|
|
128
|
+
2. What current trends or real-time information was missed?
|
|
129
|
+
3. What research evidence supports or contradicts these views?
|
|
130
|
+
4. How can these perspectives be synthesized?
|
|
131
|
+
|
|
132
|
+
- stepId: gemini-responds
|
|
133
|
+
type: prompt
|
|
134
|
+
config:
|
|
135
|
+
provider: gemini
|
|
136
|
+
prompt: |
|
|
137
|
+
Review these perspectives from other AI models:
|
|
138
|
+
|
|
139
|
+
## Claude's Perspective (Reasoning Expert):
|
|
140
|
+
{{steps.claude-perspective.output}}
|
|
141
|
+
|
|
142
|
+
## Grok's Perspective (Real-time Research Expert):
|
|
143
|
+
{{steps.grok-perspective.output}}
|
|
144
|
+
|
|
145
|
+
Now respond:
|
|
146
|
+
1. What do you agree with?
|
|
147
|
+
2. What research or evidence supports or contradicts these views?
|
|
148
|
+
3. What important points were missed?
|
|
149
|
+
4. How can these perspectives be combined?
|
|
150
|
+
|
|
151
|
+
# Step 3: Synthesize all perspectives into final answer
|
|
152
|
+
- stepId: synthesize
|
|
153
|
+
type: prompt
|
|
154
|
+
name: Synthesize Consensus
|
|
155
|
+
timeout: 90000
|
|
156
|
+
dependencies:
|
|
157
|
+
- cross-discuss
|
|
158
|
+
config:
|
|
159
|
+
provider: claude # Claude synthesizes due to nuanced reasoning
|
|
160
|
+
prompt: |
|
|
161
|
+
You are synthesizing a multi-model discussion into a final answer.
|
|
162
|
+
|
|
163
|
+
## Original Topic:
|
|
164
|
+
{{input.topic}}
|
|
165
|
+
|
|
166
|
+
## Initial Perspectives:
|
|
167
|
+
|
|
168
|
+
### Claude (Reasoning & Ethics Expert):
|
|
169
|
+
{{steps.claude-perspective.output}}
|
|
170
|
+
|
|
171
|
+
### Grok (Real-time Research Expert):
|
|
172
|
+
{{steps.grok-perspective.output}}
|
|
173
|
+
|
|
174
|
+
### Gemini (Research & Long-Context Expert):
|
|
175
|
+
{{steps.gemini-perspective.output}}
|
|
176
|
+
|
|
177
|
+
## Discussion Responses:
|
|
178
|
+
|
|
179
|
+
### Claude's Response to Others:
|
|
180
|
+
{{steps.claude-responds.output}}
|
|
181
|
+
|
|
182
|
+
### Grok's Response to Others:
|
|
183
|
+
{{steps.grok-responds.output}}
|
|
184
|
+
|
|
185
|
+
### Gemini's Response to Others:
|
|
186
|
+
{{steps.gemini-responds.output}}
|
|
187
|
+
|
|
188
|
+
## Your Task:
|
|
189
|
+
|
|
190
|
+
Synthesize all perspectives into a comprehensive answer:
|
|
191
|
+
|
|
192
|
+
1. **Areas of Strong Agreement**: What do all models agree on?
|
|
193
|
+
2. **Key Disagreements**: Where do perspectives differ? Why?
|
|
194
|
+
3. **Unique Insights**: What did each model contribute uniquely?
|
|
195
|
+
- Claude: (reasoning/ethics insights)
|
|
196
|
+
- Grok: (real-time research insights)
|
|
197
|
+
- Gemini: (research/context insights)
|
|
198
|
+
4. **Synthesis**: Combine the best insights into a unified recommendation
|
|
199
|
+
5. **Conclusion**: Provide a clear, actionable answer to the original topic
|
|
200
|
+
|
|
201
|
+
Be thorough, balanced, and actionable.
|
|
202
|
+
|
|
203
|
+
# Step 4: Store discussion results
|
|
204
|
+
- stepId: store-result
|
|
205
|
+
type: tool
|
|
206
|
+
name: Store Discussion
|
|
207
|
+
timeout: 10000
|
|
208
|
+
dependencies:
|
|
209
|
+
- synthesize
|
|
210
|
+
config:
|
|
211
|
+
tool: memory_store
|
|
212
|
+
args:
|
|
213
|
+
namespace: discussions
|
|
214
|
+
key: "{{input.topic | slugify}}"
|
|
215
|
+
value:
|
|
216
|
+
topic: "{{input.topic}}"
|
|
217
|
+
perspectives:
|
|
218
|
+
claude: "{{steps.claude-perspective.output}}"
|
|
219
|
+
grok: "{{steps.grok-perspective.output}}"
|
|
220
|
+
gemini: "{{steps.gemini-perspective.output}}"
|
|
221
|
+
responses:
|
|
222
|
+
claude: "{{steps.claude-responds.output}}"
|
|
223
|
+
grok: "{{steps.grok-responds.output}}"
|
|
224
|
+
gemini: "{{steps.gemini-responds.output}}"
|
|
225
|
+
synthesis: "{{steps.synthesize.output}}"
|
|
226
|
+
timestamp: "{{now}}"
|
|
227
|
+
providers: ["claude", "grok", "gemini"]
|
|
228
|
+
|
|
229
|
+
metadata:
|
|
230
|
+
category: collaboration
|
|
231
|
+
tags:
|
|
232
|
+
- multi-model
|
|
233
|
+
- discussion
|
|
234
|
+
- consensus
|
|
235
|
+
- ai-collaboration
|
|
236
|
+
- grok
|
|
237
|
+
requiredAbilities: []
|
|
238
|
+
estimatedDuration: 300000 # ~5 minutes (3 providers)
|
|
239
|
+
estimatedCost: medium
|
|
240
|
+
providers:
|
|
241
|
+
- claude # Synthesis & reasoning
|
|
242
|
+
- grok # Real-time research & reasoning
|
|
243
|
+
- gemini # Research & long context
|
|
@@ -0,0 +1,295 @@
|
|
|
1
|
+
workflowId: product-discovery
|
|
2
|
+
name: Product Discovery Workflow
|
|
3
|
+
description: Validate product ideas through user research, market analysis, and requirements definition
|
|
4
|
+
version: "1.0.0"
|
|
5
|
+
category: product
|
|
6
|
+
tags:
|
|
7
|
+
- product
|
|
8
|
+
- discovery
|
|
9
|
+
- research
|
|
10
|
+
- requirements
|
|
11
|
+
|
|
12
|
+
metadata:
|
|
13
|
+
requiredAbilities:
|
|
14
|
+
- product-management
|
|
15
|
+
- user-research
|
|
16
|
+
- competitive-analysis
|
|
17
|
+
estimatedDuration: 480
|
|
18
|
+
complexity: high
|
|
19
|
+
|
|
20
|
+
steps:
|
|
21
|
+
- stepId: problem-definition
|
|
22
|
+
name: Define Problem Space
|
|
23
|
+
type: prompt
|
|
24
|
+
timeout: 120000
|
|
25
|
+
config:
|
|
26
|
+
agent: product
|
|
27
|
+
task: |
|
|
28
|
+
Define the problem space we're exploring.
|
|
29
|
+
|
|
30
|
+
## Problem Definition Framework
|
|
31
|
+
|
|
32
|
+
1. **Problem Statement**:
|
|
33
|
+
- What problem are we solving?
|
|
34
|
+
- Who experiences this problem?
|
|
35
|
+
- How painful is this problem (1-10)?
|
|
36
|
+
- How frequently does it occur?
|
|
37
|
+
|
|
38
|
+
2. **Current Solutions**:
|
|
39
|
+
- How do users solve this today?
|
|
40
|
+
- What are the limitations of current solutions?
|
|
41
|
+
- Why haven't existing solutions worked?
|
|
42
|
+
|
|
43
|
+
3. **Success Criteria**:
|
|
44
|
+
- How will we know we've solved the problem?
|
|
45
|
+
- What metrics define success?
|
|
46
|
+
- What's the minimum viable outcome?
|
|
47
|
+
|
|
48
|
+
4. **Constraints**:
|
|
49
|
+
- Technical constraints
|
|
50
|
+
- Business constraints
|
|
51
|
+
- Time constraints
|
|
52
|
+
- Resource constraints
|
|
53
|
+
|
|
54
|
+
- stepId: user-research
|
|
55
|
+
name: User Research Synthesis
|
|
56
|
+
type: prompt
|
|
57
|
+
timeout: 180000
|
|
58
|
+
config:
|
|
59
|
+
agent: product
|
|
60
|
+
task: |
|
|
61
|
+
Synthesize user research to validate the problem.
|
|
62
|
+
|
|
63
|
+
## User Research Analysis
|
|
64
|
+
|
|
65
|
+
1. **User Segments**:
|
|
66
|
+
- Primary user persona
|
|
67
|
+
- Secondary user personas
|
|
68
|
+
- User jobs-to-be-done
|
|
69
|
+
|
|
70
|
+
2. **Pain Points**:
|
|
71
|
+
- Top 5 pain points identified
|
|
72
|
+
- Severity ranking
|
|
73
|
+
- Frequency of occurrence
|
|
74
|
+
|
|
75
|
+
3. **User Quotes**:
|
|
76
|
+
- Key verbatim quotes that illustrate the problem
|
|
77
|
+
- Emotional context
|
|
78
|
+
|
|
79
|
+
4. **Behavioral Insights**:
|
|
80
|
+
- Current user workflows
|
|
81
|
+
- Workarounds users employ
|
|
82
|
+
- Trigger events for seeking solutions
|
|
83
|
+
|
|
84
|
+
5. **Willingness to Pay**:
|
|
85
|
+
- Value of solving this problem
|
|
86
|
+
- Budget indicators
|
|
87
|
+
- Purchasing decision makers
|
|
88
|
+
|
|
89
|
+
- stepId: competitive-analysis
|
|
90
|
+
name: Competitive Analysis
|
|
91
|
+
type: prompt
|
|
92
|
+
timeout: 180000
|
|
93
|
+
config:
|
|
94
|
+
agent: researcher
|
|
95
|
+
task: |
|
|
96
|
+
Analyze competitive landscape.
|
|
97
|
+
|
|
98
|
+
## Competitive Analysis
|
|
99
|
+
|
|
100
|
+
1. **Direct Competitors**:
|
|
101
|
+
| Competitor | Strengths | Weaknesses | Pricing | Market Position |
|
|
102
|
+
|------------|-----------|------------|---------|-----------------|
|
|
103
|
+
|
|
104
|
+
2. **Indirect Competitors**:
|
|
105
|
+
- Alternative solutions users employ
|
|
106
|
+
- Substitute products/services
|
|
107
|
+
|
|
108
|
+
3. **Competitive Advantages**:
|
|
109
|
+
- What can we do better?
|
|
110
|
+
- What's our unique angle?
|
|
111
|
+
- Defensibility of our approach
|
|
112
|
+
|
|
113
|
+
4. **Market Gaps**:
|
|
114
|
+
- Underserved segments
|
|
115
|
+
- Unmet needs
|
|
116
|
+
- Opportunity areas
|
|
117
|
+
|
|
118
|
+
5. **Risks**:
|
|
119
|
+
- Competitive responses
|
|
120
|
+
- Market timing risks
|
|
121
|
+
- Technology risks
|
|
122
|
+
|
|
123
|
+
- stepId: solution-ideation
|
|
124
|
+
name: Solution Ideation
|
|
125
|
+
type: prompt
|
|
126
|
+
timeout: 180000
|
|
127
|
+
config:
|
|
128
|
+
agent: product
|
|
129
|
+
task: |
|
|
130
|
+
Generate and evaluate solution concepts.
|
|
131
|
+
|
|
132
|
+
## Solution Ideation
|
|
133
|
+
|
|
134
|
+
1. **Solution Concepts**:
|
|
135
|
+
For each concept:
|
|
136
|
+
- Description
|
|
137
|
+
- How it solves the problem
|
|
138
|
+
- Key features
|
|
139
|
+
- Technical feasibility (1-10)
|
|
140
|
+
- Business viability (1-10)
|
|
141
|
+
- User desirability (1-10)
|
|
142
|
+
|
|
143
|
+
2. **MVP Definition**:
|
|
144
|
+
- Minimum features for first version
|
|
145
|
+
- What we're explicitly NOT building
|
|
146
|
+
- Success metrics for MVP
|
|
147
|
+
|
|
148
|
+
3. **Validation Approach**:
|
|
149
|
+
- How will we test this solution?
|
|
150
|
+
- What experiments should we run?
|
|
151
|
+
- What would prove us wrong?
|
|
152
|
+
|
|
153
|
+
4. **Risk Assessment**:
|
|
154
|
+
- Technical risks
|
|
155
|
+
- Market risks
|
|
156
|
+
- Execution risks
|
|
157
|
+
- Mitigation strategies
|
|
158
|
+
|
|
159
|
+
- stepId: requirements-definition
|
|
160
|
+
name: Define Requirements
|
|
161
|
+
type: prompt
|
|
162
|
+
timeout: 180000
|
|
163
|
+
config:
|
|
164
|
+
agent: product
|
|
165
|
+
task: |
|
|
166
|
+
Create detailed requirements documentation.
|
|
167
|
+
|
|
168
|
+
## Product Requirements Document
|
|
169
|
+
|
|
170
|
+
1. **Overview**:
|
|
171
|
+
- Product name
|
|
172
|
+
- One-line description
|
|
173
|
+
- Target release
|
|
174
|
+
|
|
175
|
+
2. **Goals & Success Metrics**:
|
|
176
|
+
| Goal | Metric | Target | Current Baseline |
|
|
177
|
+
|------|--------|--------|------------------|
|
|
178
|
+
|
|
179
|
+
3. **User Stories**:
|
|
180
|
+
Format: As a [user type], I want [action], so that [benefit]
|
|
181
|
+
|
|
182
|
+
**Must Have (P0)**:
|
|
183
|
+
- Story 1
|
|
184
|
+
- Story 2
|
|
185
|
+
|
|
186
|
+
**Should Have (P1)**:
|
|
187
|
+
- Story 3
|
|
188
|
+
- Story 4
|
|
189
|
+
|
|
190
|
+
**Nice to Have (P2)**:
|
|
191
|
+
- Story 5
|
|
192
|
+
|
|
193
|
+
4. **Functional Requirements**:
|
|
194
|
+
- Feature 1: Description, acceptance criteria
|
|
195
|
+
- Feature 2: Description, acceptance criteria
|
|
196
|
+
|
|
197
|
+
5. **Non-Functional Requirements**:
|
|
198
|
+
- Performance requirements
|
|
199
|
+
- Security requirements
|
|
200
|
+
- Scalability requirements
|
|
201
|
+
- Accessibility requirements
|
|
202
|
+
|
|
203
|
+
6. **Out of Scope**:
|
|
204
|
+
- Explicitly excluded features
|
|
205
|
+
- Future considerations
|
|
206
|
+
|
|
207
|
+
- stepId: technical-feasibility
|
|
208
|
+
name: Technical Feasibility Assessment
|
|
209
|
+
type: prompt
|
|
210
|
+
timeout: 120000
|
|
211
|
+
config:
|
|
212
|
+
agent: architecture
|
|
213
|
+
task: |
|
|
214
|
+
Assess technical feasibility of proposed solution.
|
|
215
|
+
|
|
216
|
+
## Technical Feasibility Assessment
|
|
217
|
+
|
|
218
|
+
1. **Architecture Approach**:
|
|
219
|
+
- High-level system design
|
|
220
|
+
- Key components
|
|
221
|
+
- Integration points
|
|
222
|
+
|
|
223
|
+
2. **Technology Stack**:
|
|
224
|
+
- Recommended technologies
|
|
225
|
+
- Build vs buy decisions
|
|
226
|
+
- Third-party dependencies
|
|
227
|
+
|
|
228
|
+
3. **Effort Estimation**:
|
|
229
|
+
| Component | Complexity | Effort (days) | Risk |
|
|
230
|
+
|-----------|------------|---------------|------|
|
|
231
|
+
|
|
232
|
+
4. **Technical Risks**:
|
|
233
|
+
- Identified risks
|
|
234
|
+
- Mitigation strategies
|
|
235
|
+
- Unknowns to investigate
|
|
236
|
+
|
|
237
|
+
5. **Recommendation**:
|
|
238
|
+
- GO / NO-GO / NEEDS MORE RESEARCH
|
|
239
|
+
- Conditions for proceeding
|
|
240
|
+
- Recommended next steps
|
|
241
|
+
|
|
242
|
+
- stepId: create-roadmap
|
|
243
|
+
name: Create Roadmap
|
|
244
|
+
type: prompt
|
|
245
|
+
timeout: 120000
|
|
246
|
+
config:
|
|
247
|
+
agent: product
|
|
248
|
+
task: |
|
|
249
|
+
Create product roadmap based on discovery findings.
|
|
250
|
+
|
|
251
|
+
## Product Roadmap
|
|
252
|
+
|
|
253
|
+
1. **Phase 1: MVP** (Target: X weeks)
|
|
254
|
+
- Features included
|
|
255
|
+
- Success criteria
|
|
256
|
+
- Go/no-go decision point
|
|
257
|
+
|
|
258
|
+
2. **Phase 2: Enhancement** (Target: X weeks)
|
|
259
|
+
- Features included
|
|
260
|
+
- Dependencies on Phase 1
|
|
261
|
+
|
|
262
|
+
3. **Phase 3: Scale** (Target: X weeks)
|
|
263
|
+
- Features included
|
|
264
|
+
- Market expansion
|
|
265
|
+
|
|
266
|
+
4. **Key Milestones**:
|
|
267
|
+
| Milestone | Date | Success Criteria |
|
|
268
|
+
|-----------|------|------------------|
|
|
269
|
+
|
|
270
|
+
5. **Resource Requirements**:
|
|
271
|
+
- Team composition
|
|
272
|
+
- Skills needed
|
|
273
|
+
- External dependencies
|
|
274
|
+
|
|
275
|
+
- stepId: store-discovery
|
|
276
|
+
name: Store Discovery Artifacts
|
|
277
|
+
type: tool
|
|
278
|
+
timeout: 10000
|
|
279
|
+
tool: memory_store
|
|
280
|
+
config:
|
|
281
|
+
namespace: product-discovery
|
|
282
|
+
key: "{{product_id}}/{{version}}"
|
|
283
|
+
ttl: 31536000
|
|
284
|
+
value:
|
|
285
|
+
product_id: "{{product_id}}"
|
|
286
|
+
version: "{{version}}"
|
|
287
|
+
problem_statement: "{{problem_statement}}"
|
|
288
|
+
user_research: "{{user_research}}"
|
|
289
|
+
competitive_analysis: "{{competitive_analysis}}"
|
|
290
|
+
solution_concept: "{{solution_concept}}"
|
|
291
|
+
requirements: "{{requirements}}"
|
|
292
|
+
feasibility: "{{feasibility}}"
|
|
293
|
+
roadmap: "{{roadmap}}"
|
|
294
|
+
created_at: "{{timestamp}}"
|
|
295
|
+
created_by: "{{user}}"
|
|
@@ -0,0 +1,116 @@
|
|
|
1
|
+
workflowId: qa-specialist
|
|
2
|
+
version: "1.0.0"
|
|
3
|
+
name: Quality Assurance Workflow
|
|
4
|
+
description: Comprehensive testing and quality assurance process
|
|
5
|
+
|
|
6
|
+
steps:
|
|
7
|
+
- stepId: analyze-changes
|
|
8
|
+
type: prompt
|
|
9
|
+
name: Analyze Changes for Testing
|
|
10
|
+
timeout: 60000
|
|
11
|
+
config:
|
|
12
|
+
agentId: quality
|
|
13
|
+
prompt: |
|
|
14
|
+
Analyze changes to determine testing needs:
|
|
15
|
+
1. Identify affected features
|
|
16
|
+
2. Determine test types needed
|
|
17
|
+
3. Assess risk level
|
|
18
|
+
4. Plan test coverage
|
|
19
|
+
|
|
20
|
+
- stepId: create-test-plan
|
|
21
|
+
type: prompt
|
|
22
|
+
name: Create Test Plan
|
|
23
|
+
timeout: 60000
|
|
24
|
+
config:
|
|
25
|
+
agentId: quality
|
|
26
|
+
prompt: |
|
|
27
|
+
Create comprehensive test plan:
|
|
28
|
+
1. Unit test requirements
|
|
29
|
+
2. Integration test scenarios
|
|
30
|
+
3. E2E test cases
|
|
31
|
+
4. Performance test criteria
|
|
32
|
+
5. Security test checklist
|
|
33
|
+
|
|
34
|
+
- stepId: generate-unit-tests
|
|
35
|
+
type: prompt
|
|
36
|
+
name: Generate Unit Tests
|
|
37
|
+
timeout: 180000
|
|
38
|
+
config:
|
|
39
|
+
agentId: quality
|
|
40
|
+
prompt: |
|
|
41
|
+
Generate unit tests:
|
|
42
|
+
1. Test happy paths
|
|
43
|
+
2. Test edge cases
|
|
44
|
+
3. Test error handling
|
|
45
|
+
4. Aim for high coverage
|
|
46
|
+
|
|
47
|
+
- stepId: generate-integration-tests
|
|
48
|
+
type: prompt
|
|
49
|
+
name: Generate Integration Tests
|
|
50
|
+
timeout: 180000
|
|
51
|
+
config:
|
|
52
|
+
agentId: quality
|
|
53
|
+
prompt: |
|
|
54
|
+
Generate integration tests:
|
|
55
|
+
1. API endpoint tests
|
|
56
|
+
2. Database integration tests
|
|
57
|
+
3. External service mocks
|
|
58
|
+
4. Data flow verification
|
|
59
|
+
|
|
60
|
+
- stepId: run-tests
|
|
61
|
+
type: tool
|
|
62
|
+
name: Execute Test Suite
|
|
63
|
+
timeout: 300000
|
|
64
|
+
retryPolicy:
|
|
65
|
+
maxAttempts: 2
|
|
66
|
+
backoffMs: 5000
|
|
67
|
+
config:
|
|
68
|
+
tool: guard_check
|
|
69
|
+
args:
|
|
70
|
+
policyId: test-suite
|
|
71
|
+
parallel: true
|
|
72
|
+
|
|
73
|
+
- stepId: analyze-coverage
|
|
74
|
+
type: tool
|
|
75
|
+
name: Analyze Test Coverage
|
|
76
|
+
timeout: 60000
|
|
77
|
+
config:
|
|
78
|
+
tool: metrics_query
|
|
79
|
+
args:
|
|
80
|
+
metric: test-coverage
|
|
81
|
+
breakdown: file
|
|
82
|
+
|
|
83
|
+
- stepId: performance-test
|
|
84
|
+
type: tool
|
|
85
|
+
name: Run Performance Tests
|
|
86
|
+
timeout: 300000
|
|
87
|
+
config:
|
|
88
|
+
tool: metrics_record
|
|
89
|
+
args:
|
|
90
|
+
metric: performance
|
|
91
|
+
type: benchmark
|
|
92
|
+
|
|
93
|
+
- stepId: generate-report
|
|
94
|
+
type: prompt
|
|
95
|
+
name: Generate QA Report
|
|
96
|
+
timeout: 60000
|
|
97
|
+
config:
|
|
98
|
+
agentId: writer
|
|
99
|
+
prompt: |
|
|
100
|
+
Generate QA report:
|
|
101
|
+
1. Test execution summary
|
|
102
|
+
2. Coverage analysis
|
|
103
|
+
3. Issues found
|
|
104
|
+
4. Performance metrics
|
|
105
|
+
5. Recommendations
|
|
106
|
+
|
|
107
|
+
metadata:
|
|
108
|
+
category: quality
|
|
109
|
+
tags:
|
|
110
|
+
- testing
|
|
111
|
+
- qa
|
|
112
|
+
- quality-assurance
|
|
113
|
+
requiredAbilities:
|
|
114
|
+
- testing-strategy
|
|
115
|
+
- code-review
|
|
116
|
+
- performance-optimization
|