🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@codemcp/workflows-core

Package Overview
Dependencies
Maintainers
1
Versions
89
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@codemcp/workflows-core - npm Package Compare versions

Comparing version
5.0.1
to
5.1.0
+1
-1
package.json
{
"name": "@codemcp/workflows-core",
"version": "5.0.1",
"version": "5.1.0",
"main": "dist/index.js",

@@ -5,0 +5,0 @@ "types": "dist/index.d.ts",

@@ -17,2 +17,8 @@ ---

author: mrsimpson
requires-mcp-servers:
- name: responsible-vibe-workflows
package: '@codemcp/workflows'
description: 'Structured development workflows for AI-assisted coding'
command: npx
args: ['-y', '@codemcp/workflows']
---

@@ -41,3 +41,3 @@ # yaml-language-server: $schema=../state-machine-schema.json

description: 'Planning phase - creating a detailed implementation strategy'
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.'
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.'
transitions:

@@ -44,0 +44,0 @@ - trigger: 'need_more_exploration'