@codemcp/workflows-core 5.0.0 → 5.1.0
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
|
@@ -3,8 +3,8 @@ name: responsible-vibe
|
|
|
3
3
|
description: >
|
|
4
4
|
Structured development workflows for AI-assisted coding. Use when starting
|
|
5
5
|
new features, fixing bugs, following TDD, refactoring code, or any development
|
|
6
|
-
task that benefits from planning and structure.
|
|
7
|
-
users mention
|
|
6
|
+
task that benefits from planning and structure. Activate it when
|
|
7
|
+
users mention to build, enhance or fix code.
|
|
8
8
|
allowed-tools: >
|
|
9
9
|
whats_next proceed_to_phase conduct_review start_development
|
|
10
10
|
resume_workflow reset_development list_workflows get_tool_info
|
|
@@ -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'
|