@codemcp/workflows 6.3.1 → 6.5.0

package/packages/mcp-server/package.json

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

package/packages/mcp-server/resources/workflows/bugfix.yaml

@@ -26,6 +26,10 @@ metadata:
 states:
   reproduce:
     description: 'Reproduce and understand the bug'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Gather specific information to reliably reproduce the reported bug:
       - What are the exact OS, browser/runtime versions, and hardware specs?
@@ -42,6 +46,10 @@ states:
 
   analyze:
     description: 'Analyze the bug and identify root cause'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: Examine the code paths involved in the bug, identify the root cause, and understand why the issue occurs. Use debugging tools, add logging, and trace through the problematic code. Document your analysis and create tasks as needed.
     transitions:
       - trigger: 'need_more_reproduction'
@@ -66,6 +74,8 @@ states:
 
   fix:
     description: 'Implement the bug fix'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Implement the solution based on your analysis:
 
@@ -100,6 +110,8 @@ states:
 
   verify:
     description: 'Verify the fix and ensure no regressions'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced. Run existing tests, create new ones if needed, and verify the solution is robust.
     transitions:
       - trigger: 'fix_needs_adjustment'
@@ -123,6 +135,8 @@ states:
 
   finalize:
     description: 'Code cleanup and documentation finalization'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Ensure code quality and documentation accuracy through systematic cleanup and review.
 

package/packages/mcp-server/resources/workflows/epcc.yaml

@@ -26,6 +26,10 @@ metadata:
 states:
   explore:
     description: 'Research and exploration phase - understanding the problem space'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Research the codebase to understand existing patterns and gather context about the problem space.
 
@@ -43,6 +47,10 @@ states:
 
   plan:
     description: 'Planning phase - creating a detailed implementation strategy'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Create a detailed implementation strategy based on your exploration:
 
@@ -83,6 +91,8 @@ states:
 
   code:
     description: 'Implementation phase - writing and building the solution'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Follow your plan to build the solution:
 
@@ -124,6 +134,8 @@ states:
 
   commit:
     description: 'Code cleanup and documentation finalization'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: >
       Ensure code quality and documentation accuracy through systematic cleanup and review.
 

package/packages/mcp-server/resources/workflows/greenfield.yaml

@@ -27,6 +27,10 @@ metadata:
 states:
   ideation:
     description: 'Deep requirements discovery and PRD creation phase'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
       - Are there existing solutions? What gaps do they have?
@@ -47,6 +51,10 @@ states:
 
   architecture:
     description: 'Tech stack selection and architecture design phase'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Design the technical solution based on requirements from `$REQUIREMENTS_DOC`.
 
@@ -82,6 +90,10 @@ states:
 
   plan:
     description: 'Implementation planning phase based on established architecture'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Create a detailed implementation strategy based on your completed architecture in `$ARCHITECTURE_DOC` and requirements from `$REQUIREMENTS_DOC`.
 
@@ -118,6 +130,8 @@ states:
 
   code:
     description: 'Implementation phase following the established plan and architecture'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Build the solution following your plan and detailed design from `$DESIGN_DOC` using the architecture from `$ARCHITECTURE_DOC`.
 
@@ -151,6 +165,8 @@ states:
 
   finalize:
     description: 'Code cleanup and documentation finalization'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       This phase ensures code quality and documentation accuracy through systematic cleanup and review.
 

package/packages/mcp-server/resources/workflows/minor.yaml

@@ -26,6 +26,10 @@ metadata:
 states:
   explore:
     description: 'Analysis and design phase - understanding and planning without implementation'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: >
       Understand the problem, analyze existing patterns, and design your approach.
       Consider the scope and impact of the change.
@@ -49,6 +53,8 @@ states:
 
   implement:
     description: 'Combined implementation phase - code, test, and commit'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: >
       Write clean, focused code for the minor enhancement, test your changes, and prepare for commit.
 
@@ -85,6 +91,8 @@ states:
 
   finalize:
     description: 'Code cleanup and documentation finalization'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: >
       Ensure code quality and documentation accuracy through systematic cleanup and review.
 

package/packages/mcp-server/resources/workflows/skilled-bugfix.yaml

@@ -44,8 +44,8 @@ states:
     default_instructions: |
       Examine the code paths involved in the bug, identify the root cause, and understand why the issue occurs. Use debugging tools, add logging, and trace through the problematic code.
 
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
-      - Use your **application-design** skill if available, or ask the user about their application design practices
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
 
       Document your analysis and create tasks as needed.
     transitions:
@@ -74,9 +74,9 @@ states:
     default_instructions: |
       Implement the solution based on your analysis:
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
 
       Before implementing, assess the approach:
       - How critical is this system? What is the blast radius if the fix causes issues?
@@ -109,7 +109,7 @@ states:
     default_instructions: |
       Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced.
 
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify the solution is robust and handles edge cases
     transitions:
       - trigger: 'fix_needs_adjustment'
@@ -154,7 +154,7 @@ states:
       - Ask the user to review document updates
 
       **STEP 3: Final Validation**
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure bug fix is ready for production
       - Update task progress and mark completed work as you finalize the bug fix

package/packages/mcp-server/resources/workflows/skilled-epcc.yaml

@@ -28,11 +28,11 @@ states:
     default_instructions: |
       Research the codebase to understand existing patterns and gather context about the problem space.
 
+      - **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
       - If uncertain about conventions or rules, ask the user about them
       - Read relevant files and documentation
-      - Check whether there is a requirements document in the project and if so, read it carefully
-      - If the project is still empty, use your **starting-project** skill if available, or ask the user about their project setup practices
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
+      - Check whether there is a requirements document in the project and if so, read it carefully)
 
       Focus on understanding without writing code yet. Document your findings and create tasks as needed.
     transitions:
@@ -46,10 +46,10 @@ states:
     default_instructions: |
       Create a detailed implementation strategy based on your exploration:
 
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
       - Check whether there is a requirements document in the project and base your strategy on it
       - Check whether there is a design document in the project and adhere to it; if not, elaborate design options and present them to the user
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
-      - Use your **application-design** skill if available, or ask the user about their application design practices
 
       Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. Document the planning work thoroughly and create implementation tasks as part of the code phase as needed.
     transitions:
@@ -80,10 +80,10 @@ states:
     default_instructions: |
       Follow your plan to build the solution:
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it; if not, elaborate design options and present them to the user
       - Check whether there is a requirements document in the project and ensure all requirements are met
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
 
       Write clean, well-structured code with proper error handling. Prevent regression by building, linting, and executing existing tests. Stay flexible and adapt the plan as you learn more during implementation. Update task progress and create new tasks as needed.
     transitions:
@@ -150,7 +150,7 @@ states:
 
       **STEP 3: Final Validation**
 
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure code is ready for production/delivery
 

package/packages/mcp-server/resources/workflows/skilled-greenfield.yaml

@@ -28,13 +28,14 @@ states:
     description: 'Deep requirements discovery and PRD creation phase'
     default_instructions: |
       Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
+
+      **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
+
       - Are there existing solutions? What gaps do they have?
       - What technologies must/cannot be used? Why?
       - How will you measure product success?
       - Have you validated this need with potential users?
 
-      Use your **starting-project** skill if available, or ask the user about their project setup practices and conventions.
-
       Don't discuss technical implementation yet - focus purely on understanding the problem space and requirements. Check whether there is a requirements document in the project and if so, read it carefully. Create tasks as needed.
     transitions:
       - trigger: 'ideation_complete'
@@ -51,11 +52,11 @@ states:
     default_instructions: |
       Design the technical solution based on the requirements discovered during ideation.
 
+      - **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
       - Ask about the user's technical preferences and experience
       - Challenge their choices by presenting alternatives
       - Evaluate pros and cons of different tech stacks, frameworks, and architectural patterns
       - Consider non-functional requirements like scalability, performance, maintainability, and deployment
-      - Use your **architecture** skill if available, or ask the user about their architectural conventions
 
       Check whether there is an architecture document in the project and if so, read and build on it. Don't start coding yet - focus on technical design decisions.
     transitions:
@@ -87,7 +88,7 @@ states:
     default_instructions: |
       Create a detailed implementation strategy based on your completed architecture and requirements.
 
-      - Use your **application-design** skill if available, or ask the user about their application design practices
+      - **Apply your application-design skill.** If unavailable, ask user about application design practices.
       - Check whether there is a design document in the project and adhere to it
 
       **STEP 1: Break Down Work**
@@ -126,10 +127,10 @@ states:
     default_instructions: |
       Build the solution following your plan and architecture.
 
+      - **Apply your coding skill.** If unavailable, ask user about coding practices.
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Check whether there is a design document in the project and follow it
       - Check whether there is a requirements document in the project and ensure all requirements you are currently working on are met
-      - Use your **coding** skill if available, or ask the user about their coding practices and patterns
-      - Use your **testing** skill if available, or ask the user about their testing practices
       - Write clean, well-structured code with proper error handling
       - Prevent regression by building, linting, and executing existing tests
       - Stay flexible and adapt the plan as you learn more during implementation, but maintain alignment with your architecture decisions
@@ -186,7 +187,7 @@ states:
       Ensure project has complete documentation for newcomers including setup, usage, architecture overview, and contribution guidelines.
 
       **STEP 4: Final Validation**
-      - Use your **testing** skill if available, or ask the user about their testing practices
+      - **Apply your testing skill.** If unavailable, ask user about testing practices.
       - Verify documentation accuracy with a final review
       - Ensure project is ready for users and contributors
       - Update task progress and mark completed work as you finalize the project

package/packages/mcp-server/resources/workflows/tdd.yaml

@@ -26,6 +26,10 @@ metadata:
 states:
   explore:
     description: 'Research and exploration phase - understanding the problem space and codebase'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       **STEP 1:** Gather context about what needs to be developed. Focus on the WHY and WHAT, not the HOW.
 
@@ -46,6 +50,8 @@ states:
 
   red:
     description: 'RED phase - Write a failing test that defines the expected behavior'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Write a failing test that defines the expected behavior for the feature.
 
@@ -81,6 +87,8 @@ states:
 
   green:
     description: 'GREEN phase - Write only the necessary code to make the test pass'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Implement the necessary code to make the failing test pass with proper functionality.
 
@@ -120,6 +128,8 @@ states:
 
   refactor:
     description: 'REFACTOR phase - Improve code quality while keeping tests green (cleanup phase)'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Improve code quality while keeping all tests green. This is the cleanup phase where you enhance readability and maintainability.
 

package/packages/mcp-server/resources/workflows/waterfall.yaml

@@ -27,6 +27,10 @@ metadata:
 states:
   requirements:
     description: 'Gathering and analyzing requirements'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Familiarize yourself with the code base and understand project goals, scope, constraints, and success criteria.
 
@@ -49,6 +53,10 @@ states:
 
   design:
     description: 'Technical design and architecture planning'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
     default_instructions: |
       Review requirements from `$REQUIREMENTS_DOC` and design the technical solution.
 
@@ -72,6 +80,8 @@ states:
 
   implementation:
     description: 'Building the solution according to design'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Follow the architecture from `$ARCHITECTURE_DOC` and detailed design from `$DESIGN_DOC` to build the solution.
 
@@ -102,6 +112,8 @@ states:
 
   qa:
     description: 'Quality assurance and code review'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Perform systematic quality checks and code review:
 
@@ -132,6 +144,8 @@ states:
 
   testing:
     description: 'Comprehensive testing and validation'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Create and execute comprehensive test plans to validate feature completeness.
 
@@ -160,6 +174,8 @@ states:
 
   finalize:
     description: 'Code cleanup and documentation finalization'
+    allowed_file_patterns:
+      - '**/*'
     default_instructions: |
       Complete the feature by cleaning up code and updating documentation.
 

package/packages/opencode-plugin/dist/index.d.ts

@@ -0,0 +1,9 @@
+/**
+ * OpenCode Workflows Plugin
+ *
+ * Structured development workflows for OpenCode.
+ * Replaces the MCP server with native OpenCode integration.
+ */
+export { WorkflowsPlugin } from './plugin.js';
+export * from './types.js';
+export { default } from './plugin.js';

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

@@ -0,0 +1,11 @@
+/**
+ * OpenCode Workflows Plugin
+ *
+ * Structured development workflows for OpenCode.
+ * Replaces the MCP server with native OpenCode integration.
+ */
+export { WorkflowsPlugin } from './plugin.js';
+export * from './types.js';
+// Default export for opencode plugin loader
+export { default } from './plugin.js';
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,EAAE,eAAe,EAAE,MAAM,aAAa,CAAC;AAC9C,cAAc,YAAY,CAAC;AAE3B,4CAA4C;AAC5C,OAAO,EAAE,OAAO,EAAE,MAAM,aAAa,CAAC"}

package/packages/opencode-plugin/dist/opencode-logger.d.ts

@@ -0,0 +1,21 @@
+import { type LoggerFactory } from '@codemcp/workflows-core';
+import type { PluginInput } from './types.js';
+/**
+ * Logger interface for structured logging
+ */
+export interface Logger {
+    debug: (message: string, extra?: Record<string, unknown>) => void;
+    info: (message: string, extra?: Record<string, unknown>) => void;
+    warn: (message: string, extra?: Record<string, unknown>) => void;
+    error: (message: string, extra?: Record<string, unknown>) => void;
+}
+/**
+ * Create a logger factory that creates loggers which send output to OpenCode SDK.
+ * This factory can be passed to ServerContext so handlers use OpenCode logging.
+ */
+export declare function createOpenCodeLoggerFactory(client: PluginInput['client']): LoggerFactory;
+/**
+ * Create a logger backed by core's createLogger + a LogSink that delegates
+ * log output to the OpenCode SDK client.app.log() API.
+ */
+export declare function createOpenCodeLogger(client: PluginInput['client']): Logger;

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

@@ -0,0 +1,104 @@
+import { createLogger as coreCreateLogger, registerLogSink, } from '@codemcp/workflows-core';
+/**
+ * Create a logger factory that creates loggers which send output to OpenCode SDK.
+ * This factory can be passed to ServerContext so handlers use OpenCode logging.
+ */
+export function createOpenCodeLoggerFactory(client) {
+    const openCodeClient = client;
+    return (component) => {
+        return {
+            debug: (message, context) => {
+                openCodeClient.app
+                    .log({
+                    body: {
+                        service: component,
+                        level: 'debug',
+                        message,
+                        extra: context,
+                    },
+                })
+                    .catch(() => { });
+            },
+            info: (message, context) => {
+                openCodeClient.app
+                    .log({
+                    body: {
+                        service: component,
+                        level: 'info',
+                        message,
+                        extra: context,
+                    },
+                })
+                    .catch(() => { });
+            },
+            warn: (message, context) => {
+                openCodeClient.app
+                    .log({
+                    body: {
+                        service: component,
+                        level: 'warn',
+                        message,
+                        extra: context,
+                    },
+                })
+                    .catch(() => { });
+            },
+            error: (message, error, context) => {
+                const errorContext = error
+                    ? { ...context, error: error.message, stack: error.stack }
+                    : context;
+                openCodeClient.app
+                    .log({
+                    body: {
+                        service: component,
+                        level: 'error',
+                        message,
+                        extra: errorContext,
+                    },
+                })
+                    .catch(() => { });
+            },
+        };
+    };
+}
+/**
+ * Create a logger backed by core's createLogger + a LogSink that delegates
+ * log output to the OpenCode SDK client.app.log() API.
+ */
+export function createOpenCodeLogger(client) {
+    const openCodeClient = client;
+    const service = 'plugin.workflows';
+    // Register a LogSink that forwards core log events to the OpenCode SDK.
+    // The core LogSink interface uses 'warning' for warn-level; we map that
+    // back to 'warn' for the OpenCode SDK which expects the shorter form.
+    const sink = {
+        log: (level, _logger, message, context) => {
+            const sdkLevel = level === 'warning' ? 'warn' : level;
+            try {
+                return openCodeClient.app.log({
+                    body: {
+                        service,
+                        level: sdkLevel,
+                        message,
+                        extra: context,
+                    },
+                });
+            }
+            catch {
+                return Promise.resolve();
+            }
+        },
+    };
+    registerLogSink(sink);
+    // Return a Logger that delegates to the core logger.
+    // The core error() method has signature (message, error?, context?) so we
+    // wrap it to match our simpler (message, extra?) interface.
+    const coreLogger = coreCreateLogger('plugin.workflows');
+    return {
+        debug: (message, extra) => coreLogger.debug(message, extra),
+        info: (message, extra) => coreLogger.info(message, extra),
+        warn: (message, extra) => coreLogger.warn(message, extra),
+        error: (message, extra) => coreLogger.error(message, undefined, extra),
+    };
+}
+//# sourceMappingURL=opencode-logger.js.map

package/packages/opencode-plugin/dist/opencode-logger.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"opencode-logger.js","sourceRoot":"","sources":["../src/opencode-logger.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,YAAY,IAAI,gBAAgB,EAChC,eAAe,GAKhB,MAAM,yBAAyB,CAAC;AA6BjC;;;GAGG;AACH,MAAM,UAAU,2BAA2B,CACzC,MAA6B;IAE7B,MAAM,cAAc,GAAG,MAAwB,CAAC;IAEhD,OAAO,CAAC,SAAiB,EAAW,EAAE;QACpC,OAAO;YACL,KAAK,EAAE,CAAC,OAAe,EAAE,OAAoB,EAAE,EAAE;gBAC/C,cAAc,CAAC,GAAG;qBACf,GAAG,CAAC;oBACH,IAAI,EAAE;wBACJ,OAAO,EAAE,SAAS;wBAClB,KAAK,EAAE,OAAO;wBACd,OAAO;wBACP,KAAK,EAAE,OAA8C;qBACtD;iBACF,CAAC;qBACD,KAAK,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC,CAAC;YACrB,CAAC;YACD,IAAI,EAAE,CAAC,OAAe,EAAE,OAAoB,EAAE,EAAE;gBAC9C,cAAc,CAAC,GAAG;qBACf,GAAG,CAAC;oBACH,IAAI,EAAE;wBACJ,OAAO,EAAE,SAAS;wBAClB,KAAK,EAAE,MAAM;wBACb,OAAO;wBACP,KAAK,EAAE,OAA8C;qBACtD;iBACF,CAAC;qBACD,KAAK,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC,CAAC;YACrB,CAAC;YACD,IAAI,EAAE,CAAC,OAAe,EAAE,OAAoB,EAAE,EAAE;gBAC9C,cAAc,CAAC,GAAG;qBACf,GAAG,CAAC;oBACH,IAAI,EAAE;wBACJ,OAAO,EAAE,SAAS;wBAClB,KAAK,EAAE,MAAM;wBACb,OAAO;wBACP,KAAK,EAAE,OAA8C;qBACtD;iBACF,CAAC;qBACD,KAAK,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC,CAAC;YACrB,CAAC;YACD,KAAK,EAAE,CAAC,OAAe,EAAE,KAAa,EAAE,OAAoB,EAAE,EAAE;gBAC9D,MAAM,YAAY,GAAG,KAAK;oBACxB,CAAC,CAAC,EAAE,GAAG,OAAO,EAAE,KAAK,EAAE,KAAK,CAAC,OAAO,EAAE,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE;oBAC1D,CAAC,CAAC,OAAO,CAAC;gBACZ,cAAc,CAAC,GAAG;qBACf,GAAG,CAAC;oBACH,IAAI,EAAE;wBACJ,OAAO,EAAE,SAAS;wBAClB,KAAK,EAAE,OAAO;wBACd,OAAO;wBACP,KAAK,EAAE,YAAmD;qBAC3D;iBACF,CAAC;qBACD,KAAK,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC,CAAC;YACrB,CAAC;SACF,CAAC;IACJ,CAAC,CAAC;AACJ,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,oBAAoB,CAAC,MAA6B;IAChE,MAAM,cAAc,GAAG,MAAwB,CAAC;IAChD,MAAM,OAAO,GAAG,kBAAkB,CAAC;IAEnC,wEAAwE;IACxE,wEAAwE;IACxE,sEAAsE;IACtE,MAAM,IAAI,GAAY;QACpB,GAAG,EAAE,CACH,KAA6C,EAC7C,OAAe,EACf,OAAe,EACf,OAAoB,EACL,EAAE;YACjB,MAAM,QAAQ,GAAG,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,CAAC;YACtD,IAAI,CAAC;gBACH,OAAO,cAAc,CAAC,GAAG,CAAC,GAAG,CAAC;oBAC5B,IAAI,EAAE;wBACJ,OAAO;wBACP,KAAK,EAAE,QAA+C;wBACtD,OAAO;wBACP,KAAK,EAAE,OAA8C;qBACtD;iBACF,CAAC,CAAC;YACL,CAAC;YAAC,MAAM,CAAC;gBACP,OAAO,OAAO,CAAC,OAAO,EAAE,CAAC;YAC3B,CAAC;QACH,CAAC;KACF,CAAC;IACF,eAAe,CAAC,IAAI,CAAC,CAAC;IAEtB,qDAAqD;IACrD,0EAA0E;IAC1E,4DAA4D;IAC5D,MAAM,UAAU,GAAG,gBAAgB,CAAC,kBAAkB,CAAC,CAAC;IACxD,OAAO;QACL,KAAK,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,EAAE,CAAC,UAAU,CAAC,KAAK,CAAC,OAAO,EAAE,KAAmB,CAAC;QACzE,IAAI,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,OAAO,EAAE,KAAmB,CAAC;QACvE,IAAI,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,OAAO,EAAE,KAAmB,CAAC;QACvE,KAAK,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,EAAE,CACxB,UAAU,CAAC,KAAK,CAAC,OAAO,EAAE,SAAS,EAAE,KAAmB,CAAC;KAC5D,CAAC;AACJ,CAAC"}

package/packages/opencode-plugin/dist/plugin.d.ts

@@ -0,0 +1,23 @@
+/**
+ * OpenCode Workflows Plugin
+ *
+ * Integrates workflows-core state management with OpenCode hooks to provide
+ * phase-aware development guidance and file edit restrictions.
+ *
+ * Hooks implemented:
+ * 1. chat.message - Add synthetic part with phase instructions after each user message
+ * 2. tool.execute.before - Block editing of certain files based on phase
+ * 3. experimental.session.compacting - Inject workflow state into compaction context
+ *
+ * Logs are sent via OpenCode SDK's client.app.log() API
+ */
+import type { Plugin } from './types.js';
+/**
+ * Main plugin export
+ */
+export declare const WorkflowsPlugin: Plugin;
+declare const _default: {
+    id: string;
+    server: Plugin;
+};
+export default _default;