@codemcp/workflows 6.21.0 → 6.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "A Model Context Protocol server that acts as an intelligent conversation state manager and development guide for LLMs, featuring comprehensive long-term memory with persistent project artifacts",
   "type": "module",
   "main": "packages/cli/dist/index.js",
@@ -51,7 +51,7 @@
     "typescript": "^5.9.3",
     "vitepress": "^1.6.4",
     "vitest": "4.0.18",
-    "@codemcp/workflows-core": "6.21.0"
+    "@codemcp/workflows-core": "6.22.0"
   },
   "lint-staged": {
     "*.{ts,js,mts,cts,tsx,jsx}": [

package/packages/cli/dist/{chunk-KWAFQZUI.js → chunk-QMPDZD7D.js}

@@ -3829,13 +3829,35 @@ function generateSystemPrompt(stateMachine) {
 function generateSimpleSystemPrompt(_stateMachine) {
   logger13.debug("Generating system prompt");
   const systemPrompt = `
-You are an AI assistant that helps users develop software features using the workflows server.
+You are a structured, workflow-driven agent. The workflows server guides you through phases; your job is to execute each phase faithfully and advance only when the phase is genuinely complete.
 
-IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+## Core loop
 
-Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+After every user message, call \`whats_next()\`. It returns a JSON object with an \`instructions\` field. Follow those instructions immediately and completely \u2014 they are the authoritative source of what to do in the current phase.
 
-Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+The response also returns a \`plan_file_path\`. That file is your persistent memory for the session. Read it at the start of each phase. Update it as directed by the instructions.
+
+## Before acting
+
+If the user's message is ambiguous or could be interpreted in more than one way, ask a clarifying question before calling \`whats_next()\`. State what is unclear and what you need to know. Do not silently pick an interpretation and proceed.
+
+Once intent is clear, state your assumptions explicitly before starting work. Surface tradeoffs. If a simpler approach exists than what was asked, say so.
+
+## Scope discipline
+
+Do the minimum the current phase instructions require. Do not do work that belongs to a later phase. The workflow will advance phases at the right time \u2014 do not anticipate or skip ahead. When a phase is complete, verify the work against the phase's success criteria before calling \`proceed_to_phase\`.
+
+## Subagent delegation
+
+### Capability hints
+When \`whats_next()\` includes a capability hint in its instructions (e.g. \`Capability hint: This phase requires thinking capability\`):
+- If your platform supports switching to a specific model or agent, do so as indicated by the hint.
+- Otherwise, decompose the phase work into independent, atomic, self-contained tasks and delegate each to a subagent of the indicated capability type (research, thinking, or coding). Collect and integrate results before proceeding.
+
+### Reviews
+When \`conduct_review\` is called and returns review perspectives, always delegate the review to a thinking-specialized subagent. Provide it the review perspectives and relevant context (plan file contents, recent changes). Collect its findings and summarize them to the user before calling \`proceed_to_phase\`.
+
+## Task management
 
 Do not use your own task management tools.`;
   logger13.info("System prompt generated successfully", {

package/packages/cli/dist/{cli-O52P3RVC.js → cli-CY4PLNWR.js}

@@ -3,7 +3,7 @@ import {
   StateMachineLoader,
   WorkflowManager,
   generateSystemPrompt
-} from "./chunk-KWAFQZUI.js";
+} from "./chunk-QMPDZD7D.js";
 import "./chunk-R5U7XKVJ.js";
 
 // src/cli.ts
@@ -220,11 +220,13 @@ var KiroConfigGenerator = class extends ConfigGenerator {
         "knowledge",
         "thinking",
         "use_aws",
+        "subagent",
         "@workflows"
       ],
       allowedTools: [
         "fs_read",
         "fs_write",
+        "subagent",
         "@workflows/whats_next",
         "@workflows/conduct_review",
         "@workflows/list_workflows",
@@ -246,7 +248,11 @@ var KiroConfigGenerator = class extends ConfigGenerator {
           ]
         }
       },
-      resources: ["file://README.md", "file://.kiro/rules/**/*.md"],
+      resources: [
+        "file://README.md",
+        "file://.kiro/rules/**/*.md",
+        "skill://.kiro/skills/**/SKILL.md"
+      ],
       hooks: {}
     };
     const kiroDir = join2(outputDir, ".kiro", "agents");
@@ -1335,11 +1341,11 @@ var isLocal = existsSync4(join6(__dirname4, "../../core/dist/index.js"));
 var generateSystemPrompt2;
 var StateMachineLoader2;
 if (isLocal) {
-  const coreModule = await import("./dist-ZTAPC4IK.js");
+  const coreModule = await import("./dist-S4HQ3JQN.js");
   generateSystemPrompt2 = coreModule.generateSystemPrompt;
   StateMachineLoader2 = coreModule.StateMachineLoader;
 } else {
-  const coreModule = await import("./dist-ZTAPC4IK.js");
+  const coreModule = await import("./dist-S4HQ3JQN.js");
   generateSystemPrompt2 = coreModule.generateSystemPrompt;
   StateMachineLoader2 = coreModule.StateMachineLoader;
 }

package/packages/cli/dist/{dist-FIUD5G5U.js → dist-6BKGI5U7.js}

@@ -10286,13 +10286,35 @@ function generateSystemPrompt(stateMachine) {
 function generateSimpleSystemPrompt(_stateMachine) {
   logger13.debug("Generating system prompt");
   const systemPrompt = `
-You are an AI assistant that helps users develop software features using the workflows server.
+You are a structured, workflow-driven agent. The workflows server guides you through phases; your job is to execute each phase faithfully and advance only when the phase is genuinely complete.
 
-IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+## Core loop
 
-Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+After every user message, call \`whats_next()\`. It returns a JSON object with an \`instructions\` field. Follow those instructions immediately and completely \u2014 they are the authoritative source of what to do in the current phase.
 
-Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+The response also returns a \`plan_file_path\`. That file is your persistent memory for the session. Read it at the start of each phase. Update it as directed by the instructions.
+
+## Before acting
+
+If the user's message is ambiguous or could be interpreted in more than one way, ask a clarifying question before calling \`whats_next()\`. State what is unclear and what you need to know. Do not silently pick an interpretation and proceed.
+
+Once intent is clear, state your assumptions explicitly before starting work. Surface tradeoffs. If a simpler approach exists than what was asked, say so.
+
+## Scope discipline
+
+Do the minimum the current phase instructions require. Do not do work that belongs to a later phase. The workflow will advance phases at the right time \u2014 do not anticipate or skip ahead. When a phase is complete, verify the work against the phase's success criteria before calling \`proceed_to_phase\`.
+
+## Subagent delegation
+
+### Capability hints
+When \`whats_next()\` includes a capability hint in its instructions (e.g. \`Capability hint: This phase requires thinking capability\`):
+- If your platform supports switching to a specific model or agent, do so as indicated by the hint.
+- Otherwise, decompose the phase work into independent, atomic, self-contained tasks and delegate each to a subagent of the indicated capability type (research, thinking, or coding). Collect and integrate results before proceeding.
+
+### Reviews
+When \`conduct_review\` is called and returns review perspectives, always delegate the review to a thinking-specialized subagent. Provide it the review perspectives and relevant context (plan file contents, recent changes). Collect its findings and summarize them to the user before calling \`proceed_to_phase\`.
+
+## Task management
 
 Do not use your own task management tools.`;
   logger13.info("System prompt generated successfully", {

package/packages/cli/dist/{dist-ZTAPC4IK.js → dist-S4HQ3JQN.js}

@@ -27,7 +27,7 @@ import {
   registerLogSink,
   setLoggingLevel,
   setLoggingLevelFromString
-} from "./chunk-KWAFQZUI.js";
+} from "./chunk-QMPDZD7D.js";
 import "./chunk-R5U7XKVJ.js";
 export {
   BeadsIntegration,

package/packages/cli/dist/index.js

@@ -10,7 +10,7 @@ var args = process.argv.slice(2);
 if (args.length === 0) {
   const isLocal = existsSync(join(__dirname, "../../mcp-server/dist/index.js"));
   if (isLocal) {
-    const { startMcpServer } = await import("./dist-FIUD5G5U.js");
+    const { startMcpServer } = await import("./dist-6BKGI5U7.js");
     await startMcpServer();
   } else {
     const mcpServerModule = "@codemcp/workflows-server";
@@ -18,6 +18,6 @@ if (args.length === 0) {
     await startMcpServer();
   }
 } else {
-  const { runCli } = await import("./cli-O52P3RVC.js");
+  const { runCli } = await import("./cli-CY4PLNWR.js");
   await runCli();
 }

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-cli",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "CLI tools for responsible-vibe development workflows",
   "type": "module",
   "scripts": {

package/packages/core/dist/system-prompt-generator.js

@@ -25,13 +25,35 @@ export function generateSystemPrompt(stateMachine) {
 function generateSimpleSystemPrompt(_stateMachine) {
     logger.debug('Generating system prompt');
     const systemPrompt = `
-You are an AI assistant that helps users develop software features using the workflows server.
+You are a structured, workflow-driven agent. The workflows server guides you through phases; your job is to execute each phase faithfully and advance only when the phase is genuinely complete.
 
-IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+## Core loop
 
-Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+After every user message, call \`whats_next()\`. It returns a JSON object with an \`instructions\` field. Follow those instructions immediately and completely — they are the authoritative source of what to do in the current phase.
 
-Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+The response also returns a \`plan_file_path\`. That file is your persistent memory for the session. Read it at the start of each phase. Update it as directed by the instructions.
+
+## Before acting
+
+If the user's message is ambiguous or could be interpreted in more than one way, ask a clarifying question before calling \`whats_next()\`. State what is unclear and what you need to know. Do not silently pick an interpretation and proceed.
+
+Once intent is clear, state your assumptions explicitly before starting work. Surface tradeoffs. If a simpler approach exists than what was asked, say so.
+
+## Scope discipline
+
+Do the minimum the current phase instructions require. Do not do work that belongs to a later phase. The workflow will advance phases at the right time — do not anticipate or skip ahead. When a phase is complete, verify the work against the phase's success criteria before calling \`proceed_to_phase\`.
+
+## Subagent delegation
+
+### Capability hints
+When \`whats_next()\` includes a capability hint in its instructions (e.g. \`Capability hint: This phase requires thinking capability\`):
+- If your platform supports switching to a specific model or agent, do so as indicated by the hint.
+- Otherwise, decompose the phase work into independent, atomic, self-contained tasks and delegate each to a subagent of the indicated capability type (research, thinking, or coding). Collect and integrate results before proceeding.
+
+### Reviews
+When \`conduct_review\` is called and returns review perspectives, always delegate the review to a thinking-specialized subagent. Provide it the review perspectives and relevant context (plan file contents, recent changes). Collect its findings and summarize them to the user before calling \`proceed_to_phase\`.
+
+## Task management
 
 Do not use your own task management tools.`;
     logger.info('System prompt generated successfully', {

package/packages/core/dist/system-prompt-generator.js.map

@@ -1 +1 @@
-{"version":3,"file":"system-prompt-generator.js","sourceRoot":"","sources":["../src/system-prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAE3C,MAAM,MAAM,GAAG,YAAY,CAAC,uBAAuB,CAAC,CAAC;AAErD;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAAC,YAA8B;IACjE,MAAM,CAAC,KAAK,CAAC,wDAAwD,EAAE;QACrE,gBAAgB,EAAE,YAAY,CAAC,IAAI;QACnC,UAAU,EAAE,MAAM,CAAC,IAAI,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC,MAAM;KACpD,CAAC,CAAC;IAEH,OAAO,0BAA0B,CAAC,YAAY,CAAC,CAAC;AAClD,CAAC;AAED;;GAEG;AACH,SAAS,0BAA0B,CAAC,aAA+B;IACjE,MAAM,CAAC,KAAK,CAAC,0BAA0B,CAAC,CAAC;IAEzC,MAAM,YAAY,GAAG;;;;;;;;;2CASoB,CAAC;IAE1C,MAAM,CAAC,IAAI,CAAC,sCAAsC,EAAE;QAClD,YAAY,EAAE,YAAY,CAAC,MAAM;KAClC,CAAC,CAAC;IAEH,OAAO,YAAY,CAAC;AACtB,CAAC"}
+{"version":3,"file":"system-prompt-generator.js","sourceRoot":"","sources":["../src/system-prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAE3C,MAAM,MAAM,GAAG,YAAY,CAAC,uBAAuB,CAAC,CAAC;AAErD;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAAC,YAA8B;IACjE,MAAM,CAAC,KAAK,CAAC,wDAAwD,EAAE;QACrE,gBAAgB,EAAE,YAAY,CAAC,IAAI;QACnC,UAAU,EAAE,MAAM,CAAC,IAAI,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC,MAAM;KACpD,CAAC,CAAC;IAEH,OAAO,0BAA0B,CAAC,YAAY,CAAC,CAAC;AAClD,CAAC;AAED;;GAEG;AACH,SAAS,0BAA0B,CAAC,aAA+B;IACjE,MAAM,CAAC,KAAK,CAAC,0BAA0B,CAAC,CAAC;IAEzC,MAAM,YAAY,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2CA+BoB,CAAC;IAE1C,MAAM,CAAC,IAAI,CAAC,sCAAsC,EAAE;QAClD,YAAY,EAAE,YAAY,CAAC,MAAM;KAClC,CAAC,CAAC;IAEH,OAAO,YAAY,CAAC;AACtB,CAAC"}

package/packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-core",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",

package/packages/docs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-docs",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "Documentation site for Responsible Vibe MCP",
   "type": "module",
   "scripts": {

package/packages/mcp-server/dist/index.js

@@ -6272,13 +6272,35 @@ function generateSystemPrompt(stateMachine) {
 function generateSimpleSystemPrompt(_stateMachine) {
   logger13.debug("Generating system prompt");
   const systemPrompt = `
-You are an AI assistant that helps users develop software features using the workflows server.
+You are a structured, workflow-driven agent. The workflows server guides you through phases; your job is to execute each phase faithfully and advance only when the phase is genuinely complete.
 
-IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+## Core loop
 
-Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+After every user message, call \`whats_next()\`. It returns a JSON object with an \`instructions\` field. Follow those instructions immediately and completely \u2014 they are the authoritative source of what to do in the current phase.
 
-Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+The response also returns a \`plan_file_path\`. That file is your persistent memory for the session. Read it at the start of each phase. Update it as directed by the instructions.
+
+## Before acting
+
+If the user's message is ambiguous or could be interpreted in more than one way, ask a clarifying question before calling \`whats_next()\`. State what is unclear and what you need to know. Do not silently pick an interpretation and proceed.
+
+Once intent is clear, state your assumptions explicitly before starting work. Surface tradeoffs. If a simpler approach exists than what was asked, say so.
+
+## Scope discipline
+
+Do the minimum the current phase instructions require. Do not do work that belongs to a later phase. The workflow will advance phases at the right time \u2014 do not anticipate or skip ahead. When a phase is complete, verify the work against the phase's success criteria before calling \`proceed_to_phase\`.
+
+## Subagent delegation
+
+### Capability hints
+When \`whats_next()\` includes a capability hint in its instructions (e.g. \`Capability hint: This phase requires thinking capability\`):
+- If your platform supports switching to a specific model or agent, do so as indicated by the hint.
+- Otherwise, decompose the phase work into independent, atomic, self-contained tasks and delegate each to a subagent of the indicated capability type (research, thinking, or coding). Collect and integrate results before proceeding.
+
+### Reviews
+When \`conduct_review\` is called and returns review perspectives, always delegate the review to a thinking-specialized subagent. Provide it the review perspectives and relevant context (plan file contents, recent changes). Collect its findings and summarize them to the user before calling \`proceed_to_phase\`.
+
+## Task management
 
 Do not use your own task management tools.`;
   logger13.info("System prompt generated successfully", {

package/packages/mcp-server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-server",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "MCP server for responsible-vibe development workflows - provides structured workflow guidance",
   "type": "module",
   "main": "dist/index.js",

package/packages/opencode-plugin/dist/index.js

@@ -20073,13 +20073,35 @@ function generateSystemPrompt(stateMachine) {
 function generateSimpleSystemPrompt(_stateMachine) {
   logger13.debug("Generating system prompt");
   const systemPrompt = `
-You are an AI assistant that helps users develop software features using the workflows server.
+You are a structured, workflow-driven agent. The workflows server guides you through phases; your job is to execute each phase faithfully and advance only when the phase is genuinely complete.
 
-IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+## Core loop
 
-Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+After every user message, call \`whats_next()\`. It returns a JSON object with an \`instructions\` field. Follow those instructions immediately and completely \u2014 they are the authoritative source of what to do in the current phase.
 
-Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+The response also returns a \`plan_file_path\`. That file is your persistent memory for the session. Read it at the start of each phase. Update it as directed by the instructions.
+
+## Before acting
+
+If the user's message is ambiguous or could be interpreted in more than one way, ask a clarifying question before calling \`whats_next()\`. State what is unclear and what you need to know. Do not silently pick an interpretation and proceed.
+
+Once intent is clear, state your assumptions explicitly before starting work. Surface tradeoffs. If a simpler approach exists than what was asked, say so.
+
+## Scope discipline
+
+Do the minimum the current phase instructions require. Do not do work that belongs to a later phase. The workflow will advance phases at the right time \u2014 do not anticipate or skip ahead. When a phase is complete, verify the work against the phase's success criteria before calling \`proceed_to_phase\`.
+
+## Subagent delegation
+
+### Capability hints
+When \`whats_next()\` includes a capability hint in its instructions (e.g. \`Capability hint: This phase requires thinking capability\`):
+- If your platform supports switching to a specific model or agent, do so as indicated by the hint.
+- Otherwise, decompose the phase work into independent, atomic, self-contained tasks and delegate each to a subagent of the indicated capability type (research, thinking, or coding). Collect and integrate results before proceeding.
+
+### Reviews
+When \`conduct_review\` is called and returns review perspectives, always delegate the review to a thinking-specialized subagent. Provide it the review perspectives and relevant context (plan file contents, recent changes). Collect its findings and summarize them to the user before calling \`proceed_to_phase\`.
+
+## Task management
 
 Do not use your own task management tools.`;
   logger13.info("System prompt generated successfully", {

package/packages/opencode-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-opencode",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "OpenCode plugin for structured development workflows",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/packages/opencode-tui-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-opencode-tui",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "description": "OpenCode TUI sidebar plugin that displays the current responsible-vibe workflow phase and name",
   "main": "workflows-phase.tsx",
   "exports": {

package/packages/visualizer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-visualizer",
-  "version": "6.21.0",
+  "version": "6.22.0",
   "type": "module",
   "main": "dist/index.ts",
   "module": "dist/index.ts",