@exaudeus/workrail 0.1.8 → 0.1.9
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/README.md
CHANGED
|
@@ -86,15 +86,52 @@ Add to your agent's `config.json`:
|
|
|
86
86
|
|
|
87
87
|
---
|
|
88
88
|
|
|
89
|
+
## 💾 Using Local Workflows (when configuring MCP via JSON)
|
|
90
|
+
|
|
91
|
+
WorkRail will auto-discover workflows even when added to your agent via JSON config. It searches, in priority order:
|
|
92
|
+
|
|
93
|
+
- User: `~/.workrail/workflows` (recommended)
|
|
94
|
+
- Project: `./workflows` relative to the MCP process `cwd`
|
|
95
|
+
- Custom: directories listed in `WORKFLOW_STORAGE_PATH` (colon-separated on macOS/Linux)
|
|
96
|
+
|
|
97
|
+
Example agent config passing env and `cwd` so your local workflows are picked up:
|
|
98
|
+
|
|
99
|
+
```json
|
|
100
|
+
{
|
|
101
|
+
"mcpServers": {
|
|
102
|
+
"workrail": {
|
|
103
|
+
"command": "npx",
|
|
104
|
+
"args": ["-y", "@exaudeus/workrail"],
|
|
105
|
+
"env": {
|
|
106
|
+
"WORKFLOW_STORAGE_PATH": "/absolute/path/my-workflows:/absolute/path/shared-workflows"
|
|
107
|
+
},
|
|
108
|
+
"cwd": "/absolute/path/my-project"
|
|
109
|
+
}
|
|
110
|
+
}
|
|
111
|
+
}
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
Quick tips:
|
|
115
|
+
|
|
116
|
+
- Initialize your user dir once: `workrail init`
|
|
117
|
+
- Validate a file: `workrail validate /abs/path/my-workflows/my-workflow.json`
|
|
118
|
+
- List all discovered workflows: `workrail list`
|
|
119
|
+
|
|
120
|
+
See also: `docs/workflow-management.md` for more details.
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
89
124
|
## 📋 Available Workflows
|
|
90
125
|
|
|
91
126
|
WorkRail comes with battle-tested workflows for common development tasks:
|
|
92
127
|
|
|
93
128
|
### 🔧 **Development Workflows**
|
|
94
|
-
- **`coding-task-workflow`** -
|
|
95
|
-
- **`
|
|
96
|
-
|
|
97
|
-
|
|
129
|
+
- **`coding-task-workflow-with-loops`** - Enhanced coding workflow with iterative refinement loops, analysis, planning, implementation, and review *(Recommended)*
|
|
130
|
+
- **`systematic-bug-investigation-with-loops`** - Enhanced debugging with iterative analysis loops and systematic methodology *(Recommended)*
|
|
131
|
+
|
|
132
|
+
#### Deprecated Workflows
|
|
133
|
+
- ~~**`coding-task-workflow`** - [DEPRECATED] Use `coding-task-workflow-with-loops` instead~~
|
|
134
|
+
- ~~**`systematic-bug-investigation`** - [DEPRECATED] Use `systematic-bug-investigation-with-loops` instead~~
|
|
98
135
|
|
|
99
136
|
### 🚀 **Project Management**
|
|
100
137
|
- **`adaptive-ticket-creation`** - Create well-structured tickets with proper requirements
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "coding-task-workflow",
|
|
3
|
-
"name": "Excellent Adaptive Coding Workflow with Devil's Advocate Review",
|
|
3
|
+
"name": "[DEPRECATED] Excellent Adaptive Coding Workflow with Devil's Advocate Review",
|
|
4
4
|
"version": "0.8.0",
|
|
5
|
-
"description": "Comprehensive AI coding workflow with bidirectional re-triage, deep analysis, intelligent clarification, devil's advocate review, automation levels, failure bounds, tool fallbacks, and context documentation for production-ready development.",
|
|
5
|
+
"description": "[DEPRECATED] This workflow has been superseded by 'coding-task-workflow-with-loops' which includes enhanced loop capabilities for better iterative development. Use 'coding-task-workflow-with-loops' for new projects. Comprehensive AI coding workflow with bidirectional re-triage, deep analysis, intelligent clarification, devil's advocate review, automation levels, failure bounds, tool fallbacks, and context documentation for production-ready development.",
|
|
6
6
|
|
|
7
7
|
"preconditions": [
|
|
8
8
|
"User has a clear task description (e.g., from Jira, a dev doc, or a BRD).",
|
|
@@ -11,6 +11,7 @@
|
|
|
11
11
|
"Git repository is recommended for version control and commits (workflow degrades gracefully if unavailable)."
|
|
12
12
|
],
|
|
13
13
|
"metaGuidance": [
|
|
14
|
+
"⚠️ DEPRECATION NOTICE: This workflow is deprecated. Use 'coding-task-workflow-with-loops' instead for enhanced iterative development capabilities with loop support.",
|
|
14
15
|
"This workflow follows the ANALYZE -> CLARIFY -> PREP -> IMPLEMENT -> VERIFY pattern with bidirectional dynamic re-triage capabilities.",
|
|
15
16
|
"Deep codebase analysis occurs early to inform intelligent requirements clarification and all subsequent planning phases.",
|
|
16
17
|
"Dynamic re-triage allows complexity upgrades and safe downgrades based on new insights from analysis and clarifications.",
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "systematic-bug-investigation",
|
|
3
|
-
"name": "Systematic Bug Investigation Workflow",
|
|
3
|
+
"name": "[DEPRECATED] Systematic Bug Investigation Workflow",
|
|
4
4
|
"version": "1.0.0",
|
|
5
|
-
"description": "A comprehensive workflow for systematic bug and failing test investigation that prevents LLMs from jumping to conclusions. Enforces thorough evidence gathering, hypothesis formation, debugging instrumentation, and validation to achieve near 100% certainty about root causes. This workflow does NOT fix bugs - it produces detailed diagnostic writeups that enable effective fixing by providing complete understanding of what is happening, why it's happening, and supporting evidence.",
|
|
5
|
+
"description": "[DEPRECATED] This workflow has been superseded by 'systematic-bug-investigation-with-loops' which includes enhanced loop capabilities for iterative debugging and investigation. Use 'systematic-bug-investigation-with-loops' for new bug investigations. A comprehensive workflow for systematic bug and failing test investigation that prevents LLMs from jumping to conclusions. Enforces thorough evidence gathering, hypothesis formation, debugging instrumentation, and validation to achieve near 100% certainty about root causes. This workflow does NOT fix bugs - it produces detailed diagnostic writeups that enable effective fixing by providing complete understanding of what is happening, why it's happening, and supporting evidence.",
|
|
6
6
|
"clarificationPrompts": [
|
|
7
7
|
"What type of system is this? (web app, mobile app, backend service, desktop app, etc.)",
|
|
8
8
|
"How consistently can you reproduce this bug? (always reproducible, sometimes reproducible, rarely reproducible)",
|
|
@@ -19,6 +19,7 @@
|
|
|
19
19
|
"Bug is reproducible with specific steps or a minimal test case"
|
|
20
20
|
],
|
|
21
21
|
"metaGuidance": [
|
|
22
|
+
"⚠️ DEPRECATION NOTICE: This workflow is deprecated. Use 'systematic-bug-investigation-with-loops' instead for enhanced iterative debugging capabilities with loop support.",
|
|
22
23
|
"INVESTIGATION DISCIPLINE: Never propose fixes or solutions until Phase 6 (Comprehensive Diagnostic Writeup). Focus entirely on systematic evidence gathering and analysis.",
|
|
23
24
|
"HYPOTHESIS RIGOR: All hypotheses must be based on concrete evidence from code analysis with quantified scoring (1-10 scales). Maximum 5 hypotheses per investigation.",
|
|
24
25
|
"DEBUGGING INSTRUMENTATION: Always implement debugging mechanisms before running tests - logs, print statements, or test modifications that will provide evidence.",
|