@codemcp/workflows 5.1.1 → 5.2.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 +2 -2
- package/skill/SKILL.md +10 -5
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@codemcp/workflows",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.2.1",
|
|
4
4
|
"description": "MCP server implementation for responsible-vibe",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
],
|
|
14
14
|
"dependencies": {
|
|
15
15
|
"@modelcontextprotocol/sdk": "1.25.3",
|
|
16
|
-
"@codemcp/workflows-core": "5.
|
|
16
|
+
"@codemcp/workflows-core": "5.2.1"
|
|
17
17
|
},
|
|
18
18
|
"devDependencies": {
|
|
19
19
|
"@types/node": "^22.0.0",
|
package/skill/SKILL.md
CHANGED
|
@@ -5,13 +5,9 @@ description: >
|
|
|
5
5
|
new features, fixing bugs, following TDD, refactoring code, or any development
|
|
6
6
|
task that benefits from planning and structure. Activate it when
|
|
7
7
|
users mention to build, enhance or fix code.
|
|
8
|
-
allowed-tools: >
|
|
9
|
-
whats_next proceed_to_phase conduct_review start_development
|
|
10
|
-
resume_workflow reset_development list_workflows get_tool_info
|
|
11
|
-
setup_project_docs
|
|
12
8
|
license: MIT
|
|
13
9
|
metadata:
|
|
14
|
-
version: '5.
|
|
10
|
+
version: '5.2.1'
|
|
15
11
|
repository: https://github.com/mrsimpson/responsible-vibe-mcp
|
|
16
12
|
author: mrsimpson
|
|
17
13
|
requires-mcp-servers:
|
|
@@ -21,3 +17,12 @@ requires-mcp-servers:
|
|
|
21
17
|
command: npx
|
|
22
18
|
args: ['-y', '@codemcp/workflows']
|
|
23
19
|
---
|
|
20
|
+
You are an AI assistant that helps users develop software features using the responsible-vibe-mcp server.
|
|
21
|
+
|
|
22
|
+
IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
|
|
23
|
+
|
|
24
|
+
Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
|
|
25
|
+
|
|
26
|
+
Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
|
|
27
|
+
|
|
28
|
+
Do not use your own task management tools.
|