@codemcp/workflows-core 5.0.1 → 5.1.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
|
@@ -14,4 +14,10 @@ metadata:
|
|
|
14
14
|
version: '${VERSION}'
|
|
15
15
|
repository: https://github.com/mrsimpson/responsible-vibe-mcp
|
|
16
16
|
author: mrsimpson
|
|
17
|
+
requires-mcp-servers:
|
|
18
|
+
- name: responsible-vibe-workflows
|
|
19
|
+
package: '@codemcp/workflows'
|
|
20
|
+
description: 'Structured development workflows for AI-assisted coding'
|
|
21
|
+
command: npx
|
|
22
|
+
args: ['-y', '@codemcp/workflows']
|
|
17
23
|
---
|
|
@@ -38,7 +38,7 @@ states:
|
|
|
38
38
|
|
|
39
39
|
plan:
|
|
40
40
|
description: 'Planning phase - creating a detailed implementation strategy'
|
|
41
|
-
default_instructions: 'You are in the planning phase. Create a detailed implementation strategy based on your exploration. If $REQUIREMENTS_DOC exists, base your strategy on requirements from $REQUIREMENTS_DOC, otherwise use existing task context. Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. If it impacts the general architecture and $ARCHITECTURE_DOC exists, document this in $ARCHITECTURE_DOC, otherwise create tasks to track architectural decisions. If $DESIGN_DOC exists, make sure to adhere to the design in $DESIGN_DOC. Document the planning work thoroughly and create implementation tasks as needed.'
|
|
41
|
+
default_instructions: 'You are in the planning phase. Create a detailed implementation strategy based on your exploration. If $REQUIREMENTS_DOC exists, base your strategy on requirements from $REQUIREMENTS_DOC, otherwise use existing task context. Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. If it impacts the general architecture and $ARCHITECTURE_DOC exists, document this in $ARCHITECTURE_DOC, otherwise create tasks to track architectural decisions. If $DESIGN_DOC exists, make sure to adhere to the design in $DESIGN_DOC. Document the planning work thoroughly and create implementation tasks as part of the code phase as needed.'
|
|
42
42
|
transitions:
|
|
43
43
|
- trigger: 'need_more_exploration'
|
|
44
44
|
to: 'explore'
|