@codemcp/workflows 6.3.1 → 6.4.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 +2 -2
- package/packages/cli/dist/{cli-QV7U6L54.js → cli-DXJJF56V.js} +9 -14
- package/packages/cli/dist/index.js +1 -1
- package/packages/cli/package.json +1 -1
- package/packages/cli/resources/workflows/skilled-bugfix.yaml +6 -6
- package/packages/cli/resources/workflows/skilled-epcc.yaml +8 -8
- package/packages/cli/resources/workflows/skilled-greenfield.yaml +8 -7
- package/packages/core/package.json +1 -1
- package/packages/core/resources/workflows/skilled-bugfix.yaml +6 -6
- package/packages/core/resources/workflows/skilled-epcc.yaml +8 -8
- package/packages/core/resources/workflows/skilled-greenfield.yaml +8 -7
- package/packages/docs/.vitepress/dist/404.html +1 -1
- package/packages/docs/.vitepress/dist/assets/{user_advanced-engineering.md.MkETYNtq.js → user_advanced-engineering.md.PD-xOFno.js} +2 -2
- package/packages/docs/.vitepress/dist/assets/{user_agent-setup.md.l0oJQxTR.js → user_agent-setup.md.BhcuRdG8.js} +1 -1
- package/packages/docs/.vitepress/dist/dev/ARCHITECTURE.html +1 -1
- package/packages/docs/.vitepress/dist/dev/DEVELOPMENT.html +1 -1
- package/packages/docs/.vitepress/dist/dev/LOGGING.html +1 -1
- package/packages/docs/.vitepress/dist/dev/PUBLISHING.html +1 -1
- package/packages/docs/.vitepress/dist/hashmap.json +1 -1
- package/packages/docs/.vitepress/dist/index.html +1 -1
- package/packages/docs/.vitepress/dist/user/advanced-engineering.html +4 -4
- package/packages/docs/.vitepress/dist/user/agent-setup.html +3 -3
- package/packages/docs/.vitepress/dist/user/beads-integration.html +1 -1
- package/packages/docs/.vitepress/dist/user/crowd-mcp-integration.html +1 -1
- package/packages/docs/.vitepress/dist/user/custom-workflows.html +1 -1
- package/packages/docs/.vitepress/dist/user/git-commit-feature.html +1 -1
- package/packages/docs/.vitepress/dist/user/how-it-works.html +1 -1
- package/packages/docs/.vitepress/dist/user/long-term-memory.html +1 -1
- package/packages/docs/.vitepress/dist/user/packaged-workflows.html +1 -1
- package/packages/docs/.vitepress/dist/user/tutorial.html +1 -1
- package/packages/docs/.vitepress/dist/user/workflow-selection.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/adr.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/big-bang-conversion.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/boundary-testing.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/bugfix.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/business-analysis.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/c4-analysis.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/epcc.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/game-beginner.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/greenfield.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/minor.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/posts.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-bugfix-crowd.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-bugfix.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-feature-crowd.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-feature.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-greenfield-crowd.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/sdd-greenfield.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/skilled-bugfix.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/skilled-bugfix.yaml +6 -6
- package/packages/docs/.vitepress/dist/workflows/skilled-epcc.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/skilled-epcc.yaml +8 -8
- package/packages/docs/.vitepress/dist/workflows/skilled-greenfield.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/skilled-greenfield.yaml +8 -7
- package/packages/docs/.vitepress/dist/workflows/slides.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/tdd.html +1 -1
- package/packages/docs/.vitepress/dist/workflows/waterfall.html +1 -1
- package/packages/docs/.vitepress/dist/workflows.html +1 -1
- package/packages/docs/package.json +1 -1
- package/packages/mcp-server/package.json +1 -1
- package/packages/mcp-server/resources/workflows/skilled-bugfix.yaml +6 -6
- package/packages/mcp-server/resources/workflows/skilled-epcc.yaml +8 -8
- package/packages/mcp-server/resources/workflows/skilled-greenfield.yaml +8 -7
- package/packages/visualizer/package.json +1 -1
- package/resources/workflows/skilled-bugfix.yaml +6 -6
- package/resources/workflows/skilled-epcc.yaml +8 -8
- package/resources/workflows/skilled-greenfield.yaml +8 -7
- /package/packages/docs/.vitepress/dist/assets/{user_advanced-engineering.md.MkETYNtq.lean.js → user_advanced-engineering.md.PD-xOFno.lean.js} +0 -0
- /package/packages/docs/.vitepress/dist/assets/{user_agent-setup.md.l0oJQxTR.lean.js → user_agent-setup.md.BhcuRdG8.lean.js} +0 -0
- /package/resources/skills/application-design/{application-design.md → SKILL.md} +0 -0
- /package/resources/skills/architecture/{SKILL.md.md → SKILL.md} +0 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@codemcp/workflows",
|
|
3
|
-
"version": "6.
|
|
3
|
+
"version": "6.4.0",
|
|
4
4
|
"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",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "packages/cli/dist/index.js",
|
|
@@ -51,7 +51,7 @@
|
|
|
51
51
|
"typescript": "^5.9.3",
|
|
52
52
|
"vitepress": "^1.6.4",
|
|
53
53
|
"vitest": "4.0.18",
|
|
54
|
-
"@codemcp/workflows-core": "6.
|
|
54
|
+
"@codemcp/workflows-core": "6.4.0"
|
|
55
55
|
},
|
|
56
56
|
"lint-staged": {
|
|
57
57
|
"*.{ts,js,mts,cts,tsx,jsx}": [
|
|
@@ -202,7 +202,7 @@ var ConfigGenerator = class {
|
|
|
202
202
|
return ["whats_next", "conduct_review", "list_workflows", "get_tool_info"];
|
|
203
203
|
}
|
|
204
204
|
};
|
|
205
|
-
var
|
|
205
|
+
var KiroConfigGenerator = class extends ConfigGenerator {
|
|
206
206
|
async generate(outputDir) {
|
|
207
207
|
const systemPrompt = this.getSystemPrompt();
|
|
208
208
|
const mcpServers = this.getDefaultMcpConfig();
|
|
@@ -245,12 +245,12 @@ var AmazonQConfigGenerator = class extends ConfigGenerator {
|
|
|
245
245
|
]
|
|
246
246
|
}
|
|
247
247
|
},
|
|
248
|
-
resources: ["file://README.md", "file://.
|
|
248
|
+
resources: ["file://README.md", "file://.kiro/rules/**/*.md"],
|
|
249
249
|
hooks: {}
|
|
250
250
|
};
|
|
251
|
-
const
|
|
252
|
-
await mkdir(
|
|
253
|
-
const configPath = join2(
|
|
251
|
+
const kiroDir = join2(outputDir, ".kiro", "agents");
|
|
252
|
+
await mkdir(kiroDir, { recursive: true });
|
|
253
|
+
const configPath = join2(kiroDir, "vibe.json");
|
|
254
254
|
const finalConfig = await this.mergeWithExistingConfig(
|
|
255
255
|
configPath,
|
|
256
256
|
newConfig
|
|
@@ -466,14 +466,9 @@ var GeneratorRegistry = class {
|
|
|
466
466
|
};
|
|
467
467
|
GeneratorRegistry.register({
|
|
468
468
|
name: "kiro",
|
|
469
|
-
description: "Generate .
|
|
470
|
-
aliases: ["
|
|
471
|
-
generatorClass:
|
|
472
|
-
});
|
|
473
|
-
GeneratorRegistry.register({
|
|
474
|
-
name: "kiro-cli",
|
|
475
|
-
description: "Generate .amazonq/cli-agents/vibe.json (Kiro/Amazon Q CLI)",
|
|
476
|
-
generatorClass: AmazonQConfigGenerator
|
|
469
|
+
description: "Generate .kiro/agents/vibe.json (Kiro)",
|
|
470
|
+
aliases: ["kiro-cli"],
|
|
471
|
+
generatorClass: KiroConfigGenerator
|
|
477
472
|
});
|
|
478
473
|
GeneratorRegistry.register({
|
|
479
474
|
name: "claude",
|
|
@@ -986,7 +981,7 @@ SkillGeneratorRegistry.register({
|
|
|
986
981
|
SkillGeneratorRegistry.register({
|
|
987
982
|
name: "kiro-cli",
|
|
988
983
|
description: "Generate skill for Kiro/Amazon Q CLI (SKILL.md + mcp.json)",
|
|
989
|
-
aliases: [
|
|
984
|
+
aliases: [],
|
|
990
985
|
generatorClass: KiroCliSkillGenerator
|
|
991
986
|
});
|
|
992
987
|
async function generateSkill(platform, outputDir = ".") {
|
|
@@ -44,8 +44,8 @@ states:
|
|
|
44
44
|
default_instructions: |
|
|
45
45
|
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.
|
|
46
46
|
|
|
47
|
-
-
|
|
48
|
-
-
|
|
47
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
48
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
49
49
|
|
|
50
50
|
Document your analysis and create tasks as needed.
|
|
51
51
|
transitions:
|
|
@@ -74,9 +74,9 @@ states:
|
|
|
74
74
|
default_instructions: |
|
|
75
75
|
Implement the solution based on your analysis:
|
|
76
76
|
|
|
77
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
78
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
77
79
|
- Check whether there is a design document in the project and follow it
|
|
78
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
79
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
80
80
|
|
|
81
81
|
Before implementing, assess the approach:
|
|
82
82
|
- How critical is this system? What is the blast radius if the fix causes issues?
|
|
@@ -109,7 +109,7 @@ states:
|
|
|
109
109
|
default_instructions: |
|
|
110
110
|
Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced.
|
|
111
111
|
|
|
112
|
-
-
|
|
112
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
113
113
|
- Verify the solution is robust and handles edge cases
|
|
114
114
|
transitions:
|
|
115
115
|
- trigger: 'fix_needs_adjustment'
|
|
@@ -154,7 +154,7 @@ states:
|
|
|
154
154
|
- Ask the user to review document updates
|
|
155
155
|
|
|
156
156
|
**STEP 3: Final Validation**
|
|
157
|
-
-
|
|
157
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
158
158
|
- Verify documentation accuracy with a final review
|
|
159
159
|
- Ensure bug fix is ready for production
|
|
160
160
|
- Update task progress and mark completed work as you finalize the bug fix
|
|
@@ -28,11 +28,11 @@ states:
|
|
|
28
28
|
default_instructions: |
|
|
29
29
|
Research the codebase to understand existing patterns and gather context about the problem space.
|
|
30
30
|
|
|
31
|
+
- **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
|
|
32
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
31
33
|
- If uncertain about conventions or rules, ask the user about them
|
|
32
34
|
- Read relevant files and documentation
|
|
33
|
-
- Check whether there is a requirements document in the project and if so, read it carefully
|
|
34
|
-
- If the project is still empty, use your **starting-project** skill if available, or ask the user about their project setup practices
|
|
35
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
35
|
+
- Check whether there is a requirements document in the project and if so, read it carefully)
|
|
36
36
|
|
|
37
37
|
Focus on understanding without writing code yet. Document your findings and create tasks as needed.
|
|
38
38
|
transitions:
|
|
@@ -46,10 +46,10 @@ states:
|
|
|
46
46
|
default_instructions: |
|
|
47
47
|
Create a detailed implementation strategy based on your exploration:
|
|
48
48
|
|
|
49
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
50
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
49
51
|
- Check whether there is a requirements document in the project and base your strategy on it
|
|
50
52
|
- 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
|
|
51
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
52
|
-
- Use your **application-design** skill if available, or ask the user about their application design practices
|
|
53
53
|
|
|
54
54
|
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.
|
|
55
55
|
transitions:
|
|
@@ -80,10 +80,10 @@ states:
|
|
|
80
80
|
default_instructions: |
|
|
81
81
|
Follow your plan to build the solution:
|
|
82
82
|
|
|
83
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
84
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
83
85
|
- Check whether there is a design document in the project and follow it; if not, elaborate design options and present them to the user
|
|
84
86
|
- Check whether there is a requirements document in the project and ensure all requirements are met
|
|
85
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
86
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
87
87
|
|
|
88
88
|
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.
|
|
89
89
|
transitions:
|
|
@@ -150,7 +150,7 @@ states:
|
|
|
150
150
|
|
|
151
151
|
**STEP 3: Final Validation**
|
|
152
152
|
|
|
153
|
-
-
|
|
153
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
154
154
|
- Verify documentation accuracy with a final review
|
|
155
155
|
- Ensure code is ready for production/delivery
|
|
156
156
|
|
|
@@ -28,13 +28,14 @@ states:
|
|
|
28
28
|
description: 'Deep requirements discovery and PRD creation phase'
|
|
29
29
|
default_instructions: |
|
|
30
30
|
Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
|
|
31
|
+
|
|
32
|
+
**Apply your starting-project skill.** If unavailable, ask user about project setup practices.
|
|
33
|
+
|
|
31
34
|
- Are there existing solutions? What gaps do they have?
|
|
32
35
|
- What technologies must/cannot be used? Why?
|
|
33
36
|
- How will you measure product success?
|
|
34
37
|
- Have you validated this need with potential users?
|
|
35
38
|
|
|
36
|
-
Use your **starting-project** skill if available, or ask the user about their project setup practices and conventions.
|
|
37
|
-
|
|
38
39
|
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.
|
|
39
40
|
transitions:
|
|
40
41
|
- trigger: 'ideation_complete'
|
|
@@ -51,11 +52,11 @@ states:
|
|
|
51
52
|
default_instructions: |
|
|
52
53
|
Design the technical solution based on the requirements discovered during ideation.
|
|
53
54
|
|
|
55
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
54
56
|
- Ask about the user's technical preferences and experience
|
|
55
57
|
- Challenge their choices by presenting alternatives
|
|
56
58
|
- Evaluate pros and cons of different tech stacks, frameworks, and architectural patterns
|
|
57
59
|
- Consider non-functional requirements like scalability, performance, maintainability, and deployment
|
|
58
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
59
60
|
|
|
60
61
|
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.
|
|
61
62
|
transitions:
|
|
@@ -87,7 +88,7 @@ states:
|
|
|
87
88
|
default_instructions: |
|
|
88
89
|
Create a detailed implementation strategy based on your completed architecture and requirements.
|
|
89
90
|
|
|
90
|
-
-
|
|
91
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
91
92
|
- Check whether there is a design document in the project and adhere to it
|
|
92
93
|
|
|
93
94
|
**STEP 1: Break Down Work**
|
|
@@ -126,10 +127,10 @@ states:
|
|
|
126
127
|
default_instructions: |
|
|
127
128
|
Build the solution following your plan and architecture.
|
|
128
129
|
|
|
130
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
131
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
129
132
|
- Check whether there is a design document in the project and follow it
|
|
130
133
|
- Check whether there is a requirements document in the project and ensure all requirements you are currently working on are met
|
|
131
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
132
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
133
134
|
- Write clean, well-structured code with proper error handling
|
|
134
135
|
- Prevent regression by building, linting, and executing existing tests
|
|
135
136
|
- Stay flexible and adapt the plan as you learn more during implementation, but maintain alignment with your architecture decisions
|
|
@@ -186,7 +187,7 @@ states:
|
|
|
186
187
|
Ensure project has complete documentation for newcomers including setup, usage, architecture overview, and contribution guidelines.
|
|
187
188
|
|
|
188
189
|
**STEP 4: Final Validation**
|
|
189
|
-
-
|
|
190
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
190
191
|
- Verify documentation accuracy with a final review
|
|
191
192
|
- Ensure project is ready for users and contributors
|
|
192
193
|
- Update task progress and mark completed work as you finalize the project
|
|
@@ -44,8 +44,8 @@ states:
|
|
|
44
44
|
default_instructions: |
|
|
45
45
|
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.
|
|
46
46
|
|
|
47
|
-
-
|
|
48
|
-
-
|
|
47
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
48
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
49
49
|
|
|
50
50
|
Document your analysis and create tasks as needed.
|
|
51
51
|
transitions:
|
|
@@ -74,9 +74,9 @@ states:
|
|
|
74
74
|
default_instructions: |
|
|
75
75
|
Implement the solution based on your analysis:
|
|
76
76
|
|
|
77
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
78
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
77
79
|
- Check whether there is a design document in the project and follow it
|
|
78
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
79
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
80
80
|
|
|
81
81
|
Before implementing, assess the approach:
|
|
82
82
|
- How critical is this system? What is the blast radius if the fix causes issues?
|
|
@@ -109,7 +109,7 @@ states:
|
|
|
109
109
|
default_instructions: |
|
|
110
110
|
Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced.
|
|
111
111
|
|
|
112
|
-
-
|
|
112
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
113
113
|
- Verify the solution is robust and handles edge cases
|
|
114
114
|
transitions:
|
|
115
115
|
- trigger: 'fix_needs_adjustment'
|
|
@@ -154,7 +154,7 @@ states:
|
|
|
154
154
|
- Ask the user to review document updates
|
|
155
155
|
|
|
156
156
|
**STEP 3: Final Validation**
|
|
157
|
-
-
|
|
157
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
158
158
|
- Verify documentation accuracy with a final review
|
|
159
159
|
- Ensure bug fix is ready for production
|
|
160
160
|
- Update task progress and mark completed work as you finalize the bug fix
|
|
@@ -28,11 +28,11 @@ states:
|
|
|
28
28
|
default_instructions: |
|
|
29
29
|
Research the codebase to understand existing patterns and gather context about the problem space.
|
|
30
30
|
|
|
31
|
+
- **Apply your starting-project skill.** If unavailable, ask user about project setup practices.
|
|
32
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
31
33
|
- If uncertain about conventions or rules, ask the user about them
|
|
32
34
|
- Read relevant files and documentation
|
|
33
|
-
- Check whether there is a requirements document in the project and if so, read it carefully
|
|
34
|
-
- If the project is still empty, use your **starting-project** skill if available, or ask the user about their project setup practices
|
|
35
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
35
|
+
- Check whether there is a requirements document in the project and if so, read it carefully)
|
|
36
36
|
|
|
37
37
|
Focus on understanding without writing code yet. Document your findings and create tasks as needed.
|
|
38
38
|
transitions:
|
|
@@ -46,10 +46,10 @@ states:
|
|
|
46
46
|
default_instructions: |
|
|
47
47
|
Create a detailed implementation strategy based on your exploration:
|
|
48
48
|
|
|
49
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
50
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
49
51
|
- Check whether there is a requirements document in the project and base your strategy on it
|
|
50
52
|
- 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
|
|
51
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
52
|
-
- Use your **application-design** skill if available, or ask the user about their application design practices
|
|
53
53
|
|
|
54
54
|
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.
|
|
55
55
|
transitions:
|
|
@@ -80,10 +80,10 @@ states:
|
|
|
80
80
|
default_instructions: |
|
|
81
81
|
Follow your plan to build the solution:
|
|
82
82
|
|
|
83
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
84
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
83
85
|
- Check whether there is a design document in the project and follow it; if not, elaborate design options and present them to the user
|
|
84
86
|
- Check whether there is a requirements document in the project and ensure all requirements are met
|
|
85
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
86
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
87
87
|
|
|
88
88
|
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.
|
|
89
89
|
transitions:
|
|
@@ -150,7 +150,7 @@ states:
|
|
|
150
150
|
|
|
151
151
|
**STEP 3: Final Validation**
|
|
152
152
|
|
|
153
|
-
-
|
|
153
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
154
154
|
- Verify documentation accuracy with a final review
|
|
155
155
|
- Ensure code is ready for production/delivery
|
|
156
156
|
|
|
@@ -28,13 +28,14 @@ states:
|
|
|
28
28
|
description: 'Deep requirements discovery and PRD creation phase'
|
|
29
29
|
default_instructions: |
|
|
30
30
|
Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
|
|
31
|
+
|
|
32
|
+
**Apply your starting-project skill.** If unavailable, ask user about project setup practices.
|
|
33
|
+
|
|
31
34
|
- Are there existing solutions? What gaps do they have?
|
|
32
35
|
- What technologies must/cannot be used? Why?
|
|
33
36
|
- How will you measure product success?
|
|
34
37
|
- Have you validated this need with potential users?
|
|
35
38
|
|
|
36
|
-
Use your **starting-project** skill if available, or ask the user about their project setup practices and conventions.
|
|
37
|
-
|
|
38
39
|
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.
|
|
39
40
|
transitions:
|
|
40
41
|
- trigger: 'ideation_complete'
|
|
@@ -51,11 +52,11 @@ states:
|
|
|
51
52
|
default_instructions: |
|
|
52
53
|
Design the technical solution based on the requirements discovered during ideation.
|
|
53
54
|
|
|
55
|
+
- **Apply your architecture skill.** If unavailable, ask user about architectural conventions.
|
|
54
56
|
- Ask about the user's technical preferences and experience
|
|
55
57
|
- Challenge their choices by presenting alternatives
|
|
56
58
|
- Evaluate pros and cons of different tech stacks, frameworks, and architectural patterns
|
|
57
59
|
- Consider non-functional requirements like scalability, performance, maintainability, and deployment
|
|
58
|
-
- Use your **architecture** skill if available, or ask the user about their architectural conventions
|
|
59
60
|
|
|
60
61
|
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.
|
|
61
62
|
transitions:
|
|
@@ -87,7 +88,7 @@ states:
|
|
|
87
88
|
default_instructions: |
|
|
88
89
|
Create a detailed implementation strategy based on your completed architecture and requirements.
|
|
89
90
|
|
|
90
|
-
-
|
|
91
|
+
- **Apply your application-design skill.** If unavailable, ask user about application design practices.
|
|
91
92
|
- Check whether there is a design document in the project and adhere to it
|
|
92
93
|
|
|
93
94
|
**STEP 1: Break Down Work**
|
|
@@ -126,10 +127,10 @@ states:
|
|
|
126
127
|
default_instructions: |
|
|
127
128
|
Build the solution following your plan and architecture.
|
|
128
129
|
|
|
130
|
+
- **Apply your coding skill.** If unavailable, ask user about coding practices.
|
|
131
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
129
132
|
- Check whether there is a design document in the project and follow it
|
|
130
133
|
- Check whether there is a requirements document in the project and ensure all requirements you are currently working on are met
|
|
131
|
-
- Use your **coding** skill if available, or ask the user about their coding practices and patterns
|
|
132
|
-
- Use your **testing** skill if available, or ask the user about their testing practices
|
|
133
134
|
- Write clean, well-structured code with proper error handling
|
|
134
135
|
- Prevent regression by building, linting, and executing existing tests
|
|
135
136
|
- Stay flexible and adapt the plan as you learn more during implementation, but maintain alignment with your architecture decisions
|
|
@@ -186,7 +187,7 @@ states:
|
|
|
186
187
|
Ensure project has complete documentation for newcomers including setup, usage, architecture overview, and contribution guidelines.
|
|
187
188
|
|
|
188
189
|
**STEP 4: Final Validation**
|
|
189
|
-
-
|
|
190
|
+
- **Apply your testing skill.** If unavailable, ask user about testing practices.
|
|
190
191
|
- Verify documentation accuracy with a final review
|
|
191
192
|
- Ensure project is ready for users and contributors
|
|
192
193
|
- Update task progress and mark completed work as you finalize the project
|
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
</head>
|
|
18
18
|
<body>
|
|
19
19
|
<div id="app"></div>
|
|
20
|
-
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"
|
|
20
|
+
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"PD-xOFno\",\"user_agent-setup.md\":\"BhcuRdG8\",\"user_beads-integration.md\":\"BzdR5Fif\",\"user_crowd-mcp-integration.md\":\"C15kSdIJ\",\"user_custom-workflows.md\":\"Cz4IYCXa\",\"user_git-commit-feature.md\":\"UcTvDR-O\",\"user_how-it-works.md\":\"DiOXNgaL\",\"user_long-term-memory.md\":\"DZh0tjNa\",\"user_packaged-workflows.md\":\"s1HT89ZU\",\"user_tutorial.md\":\"Dmj8zLB2\",\"user_workflow-selection.md\":\"CrPGw9Hr\",\"workflows.md\":\"Bm5sGt3u\",\"workflows_adr.md\":\"DEaXkbRp\",\"workflows_big-bang-conversion.md\":\"BA5R1LxZ\",\"workflows_boundary-testing.md\":\"DBcYnMhx\",\"workflows_bugfix.md\":\"CZRCL0Hp\",\"workflows_business-analysis.md\":\"fGLml8Hw\",\"workflows_c4-analysis.md\":\"Dnssqzuf\",\"workflows_epcc.md\":\"M6DnIhpp\",\"workflows_game-beginner.md\":\"CNxzWLtd\",\"workflows_greenfield.md\":\"vx_g-WOe\",\"workflows_minor.md\":\"DdnfwMf4\",\"workflows_posts.md\":\"SOldXvq7\",\"workflows_sdd-bugfix-crowd.md\":\"-lSf42gJ\",\"workflows_sdd-bugfix.md\":\"oRAsEVbc\",\"workflows_sdd-feature-crowd.md\":\"DAtnfCAd\",\"workflows_sdd-feature.md\":\"Ce3-H_g3\",\"workflows_sdd-greenfield-crowd.md\":\"8DUvcmLe\",\"workflows_sdd-greenfield.md\":\"eEN6U0J4\",\"workflows_skilled-bugfix.md\":\"YyOU6NjA\",\"workflows_skilled-epcc.md\":\"BGeI6g1n\",\"workflows_skilled-greenfield.md\":\"CKxrbPQ-\",\"workflows_slides.md\":\"Cqt-19_1\",\"workflows_tdd.md\":\"BjVC69tu\",\"workflows_waterfall.md\":\"CL6jTZP9\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Responsible Vibe MCP\",\"description\":\"Model Context Protocol server for intelligent conversation state management and development guidance\",\"base\":\"/responsible-vibe-mcp/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":true,\"themeConfig\":{\"nav\":[{\"text\":\"Documentation\",\"link\":\"/\"},{\"text\":\"Workflows\",\"link\":\"/workflows\"},{\"text\":\"Github\",\"link\":\"https://github.com/mrsimpson/responsible-vibe-mcp\"}],\"sidebar\":[{\"text\":\"User Guide\",\"items\":[{\"text\":\"Overview\",\"link\":\"/\"},{\"text\":\"How It Works\",\"link\":\"/user/how-it-works\"},{\"text\":\"Agent Setup\",\"link\":\"/user/agent-setup\"},{\"text\":\"Vibe Engineering\",\"link\":\"/user/advanced-engineering\"},{\"text\":\"Long-Term Memory\",\"link\":\"/user/long-term-memory\"},{\"text\":\"Beads-Integration\",\"link\":\"/user/beads-integration\"},{\"text\":\"Tutorial\",\"link\":\"/user/tutorial\"}]},{\"text\":\"Workflows\",\"items\":[{\"text\":\"Workflow-Selection\",\"link\":\"/user/workflow-selection\"},{\"text\":\"Packaged Workflows\",\"link\":\"/user/packaged-workflows\"},{\"text\":\"Custom Workflows\",\"link\":\"/user/custom-workflows\"},{\"text\":\"Explore All Workflows\",\"link\":\"/workflows\"},{\"text\":\"Crowd MCP Integration\",\"link\":\"/user/crowd-mcp-integration\"}]}]},\"locales\":{},\"scrollOffset\":134,\"cleanUrls\":false}");</script>
|
|
21
21
|
|
|
22
22
|
</body>
|
|
23
23
|
</html>
|
|
@@ -8,7 +8,7 @@ import{_ as s,c as a,o as n,a0 as i}from"./chunks/framework.DZS7lpav.js";const g
|
|
|
8
8
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># Can reference .vibe/docs/ for long-term memory when needed</span></span></code></pre></div><h3 id="explicit-reference-documentation" tabindex="-1">Explicit Reference Documentation <a class="header-anchor" href="#explicit-reference-documentation" aria-label="Permalink to "Explicit Reference Documentation""></a></h3><p>Development plans serve as <strong>process memory</strong> (actively maintained by AI) but can also be <strong>explicitly referenced</strong>:</p><p><strong>Through Commits:</strong></p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">git</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> commit</span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> -m</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> "implement user authentication</span></span>
|
|
9
9
|
<span class="line"></span>
|
|
10
10
|
<span class="line"><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">See development-plan-feature-auth.md for architectural decisions</span></span>
|
|
11
|
-
<span class="line"><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">and requirements analysis from the planning phase."</span></span></code></pre></div><p>When your AI reads this commit, it can reference the plan file to understand the context and decisions made.</p><p><strong>Through Direct Reference:</strong></p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">"Check @.vibe/development-plan-auth.md to see what we thought about back then"</span></span></code></pre></div><h2 id="rule-files-integration" tabindex="-1">Rule Files Integration <a class="header-anchor" href="#rule-files-integration" aria-label="Permalink to "Rule Files Integration""></a></h2><h3 id="process-vs-deliverable-guidance" tabindex="-1">Process vs Deliverable Guidance <a class="header-anchor" href="#process-vs-deliverable-guidance" aria-label="Permalink to "Process vs Deliverable Guidance""></a></h3><p><strong>Responsible Vibe</strong> provides <strong>HOW of the process</strong> (what phase, what to focus on)<br><strong>Rule files</strong> provide <strong>HOW of the deliverables</strong> (coding standards, conventions)</p><p><strong>Example Rule File</strong> (<code>.
|
|
11
|
+
<span class="line"><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">and requirements analysis from the planning phase."</span></span></code></pre></div><p>When your AI reads this commit, it can reference the plan file to understand the context and decisions made.</p><p><strong>Through Direct Reference:</strong></p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">"Check @.vibe/development-plan-auth.md to see what we thought about back then"</span></span></code></pre></div><h2 id="rule-files-integration" tabindex="-1">Rule Files Integration <a class="header-anchor" href="#rule-files-integration" aria-label="Permalink to "Rule Files Integration""></a></h2><h3 id="process-vs-deliverable-guidance" tabindex="-1">Process vs Deliverable Guidance <a class="header-anchor" href="#process-vs-deliverable-guidance" aria-label="Permalink to "Process vs Deliverable Guidance""></a></h3><p><strong>Responsible Vibe</strong> provides <strong>HOW of the process</strong> (what phase, what to focus on)<br><strong>Rule files</strong> provide <strong>HOW of the deliverables</strong> (coding standards, conventions)</p><p><strong>Example Rule File</strong> (<code>.kiro/rules/comments.md</code>):</p><div class="language-markdown vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">markdown</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#24292E;--shiki-light-font-weight:bold;--shiki-dark:#E1E4E8;--shiki-dark-font-weight:bold;">**Use**</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> comments to explain the purpose of a variable/method/function/class.</span></span>
|
|
12
12
|
<span class="line"><span style="--shiki-light:#24292E;--shiki-light-font-weight:bold;--shiki-dark:#E1E4E8;--shiki-dark-font-weight:bold;">**Use**</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> meaningful variable/method/function/class names.</span></span>
|
|
13
13
|
<span class="line"></span>
|
|
14
14
|
<span class="line"><span style="--shiki-light:#24292E;--shiki-light-font-weight:bold;--shiki-dark:#E1E4E8;--shiki-dark-font-weight:bold;">**Avoid**</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> comments that describe what the code is doing.</span></span>
|
|
@@ -34,7 +34,7 @@ import{_ as s,c as a,o as n,a0 as i}from"./chunks/framework.DZS7lpav.js";const g
|
|
|
34
34
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># AI automatically:</span></span>
|
|
35
35
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># 1. Creates development-plan-feature-payment.md for this branch's context</span></span>
|
|
36
36
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># 2. Can reference existing .vibe/docs/architecture.md via workflow variables</span></span>
|
|
37
|
-
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># 3. Follows your .
|
|
37
|
+
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># 3. Follows your .kiro/rules/ coding standards</span></span>
|
|
38
38
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># 4. Maintains separate conversation context for this branch</span></span>
|
|
39
39
|
<span class="line"></span>
|
|
40
40
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># Document decisions in plan file during development</span></span>
|
|
@@ -5,7 +5,7 @@ import{_ as i,c as t,o as e,a0 as a}from"./chunks/framework.DZS7lpav.js";const c
|
|
|
5
5
|
<span class="line"><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> "args"</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">: [</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">"-y"</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">, </span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">"@codemcp/workflows-server"</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">]</span></span>
|
|
6
6
|
<span class="line"><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> }</span></span>
|
|
7
7
|
<span class="line"><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> }</span></span>
|
|
8
|
-
<span class="line"><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">}</span></span></code></pre></div><h2 id="setup-via-cli" tabindex="-1">Setup via CLI <a class="header-anchor" href="#setup-via-cli" aria-label="Permalink to "Setup via CLI""></a></h2><p>The CLI generates both the system prompt and MCP configuration for your agent:</p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">npx</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> @codemcp/workflows</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> setup</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> <</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">targe</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">t</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">></span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> [--mode </span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">config</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">|</span><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">skill]</span></span></code></pre></div><h3 id="modes" tabindex="-1">Modes <a class="header-anchor" href="#modes" aria-label="Permalink to "Modes""></a></h3><table tabindex="0"><thead><tr><th>Mode</th><th>Description</th></tr></thead><tbody><tr><td><code>config</code></td><td>Embeds system prompt in agent configuration files (traditional approach)</td></tr><tr><td><code>skill</code></td><td>Creates <a href="https://agentskills.io" target="_blank" rel="noreferrer">agentskills.io</a> compatible skill files (on-demand loading)</td></tr></tbody></table><p><strong>Config mode</strong> is best when you always want the workflow guidance active.</p><p><strong>Skill mode</strong> is best when you want the agent to load workflow instructions only when needed.</p><h3 id="targets" tabindex="-1">Targets <a class="header-anchor" href="#targets" aria-label="Permalink to "Targets""></a></h3><table tabindex="0"><thead><tr><th>Target</th><th>Aliases</th><th>Description</th></tr></thead><tbody><tr><td><code>kiro</code></td><td><code>
|
|
8
|
+
<span class="line"><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">}</span></span></code></pre></div><h2 id="setup-via-cli" tabindex="-1">Setup via CLI <a class="header-anchor" href="#setup-via-cli" aria-label="Permalink to "Setup via CLI""></a></h2><p>The CLI generates both the system prompt and MCP configuration for your agent:</p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">npx</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> @codemcp/workflows</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> setup</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> <</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">targe</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">t</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">></span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;"> [--mode </span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">config</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">|</span><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">skill]</span></span></code></pre></div><h3 id="modes" tabindex="-1">Modes <a class="header-anchor" href="#modes" aria-label="Permalink to "Modes""></a></h3><table tabindex="0"><thead><tr><th>Mode</th><th>Description</th></tr></thead><tbody><tr><td><code>config</code></td><td>Embeds system prompt in agent configuration files (traditional approach)</td></tr><tr><td><code>skill</code></td><td>Creates <a href="https://agentskills.io" target="_blank" rel="noreferrer">agentskills.io</a> compatible skill files (on-demand loading)</td></tr></tbody></table><p><strong>Config mode</strong> is best when you always want the workflow guidance active.</p><p><strong>Skill mode</strong> is best when you want the agent to load workflow instructions only when needed.</p><h3 id="targets" tabindex="-1">Targets <a class="header-anchor" href="#targets" aria-label="Permalink to "Targets""></a></h3><table tabindex="0"><thead><tr><th>Target</th><th>Aliases</th><th>Description</th></tr></thead><tbody><tr><td><code>kiro</code></td><td><code>kiro-cli</code>.</td><td>Kiro / Kiro CLI</td></tr><tr><td><code>claude</code></td><td><code>claude-code</code>, <code>claude-desktop</code></td><td>Claude Code</td></tr><tr><td><code>gemini</code></td><td><code>gemini-cli</code></td><td>Gemini CLI</td></tr><tr><td><code>opencode</code></td><td>-</td><td>OpenCode CLI</td></tr><tr><td><code>copilot</code></td><td><code>copilot-vscode</code>, <code>vscode</code>, <code>github-copilot</code></td><td>GitHub Copilot</td></tr></tbody></table><h3 id="examples" tabindex="-1">Examples <a class="header-anchor" href="#examples" aria-label="Permalink to "Examples""></a></h3><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># Config mode - embeds system prompt (default)</span></span>
|
|
9
9
|
<span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">npx</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> @codemcp/workflows</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> setup</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> claude</span></span>
|
|
10
10
|
<span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">npx</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> @codemcp/workflows</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> setup</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> kiro</span></span>
|
|
11
11
|
<span class="line"></span>
|
|
@@ -149,7 +149,7 @@
|
|
|
149
149
|
<span class="line"></span>
|
|
150
150
|
<span class="line"><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"># Pretty-print with jq</span></span>
|
|
151
151
|
<span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">cat</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> .vibe/conversations/my-project-main-abc123/interactions.jsonl</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> |</span><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;"> jq</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> .</span></span></code></pre></div><p><strong>Note</strong>: All interaction data is stored locally on your system and is never transmitted to external services.</p><h2 id="task-backend-architecture" tabindex="-1">Task Backend Architecture <a class="header-anchor" href="#task-backend-architecture" aria-label="Permalink to "Task Backend Architecture""></a></h2><p>The system supports multiple task management backends through a factory pattern for component substitution.</p><h3 id="backend-detection" tabindex="-1">Backend Detection <a class="header-anchor" href="#backend-detection" aria-label="Permalink to "Backend Detection""></a></h3><p>At startup, the system auto-detects the task backend. If the <code>bd</code> command is available, beads is used; otherwise markdown is used. This can be overridden via the <code>TASK_BACKEND</code> environment variable (<code>markdown</code> or <code>beads</code>).</p><h3 id="component-factory" tabindex="-1">Component Factory <a class="header-anchor" href="#component-factory" aria-label="Permalink to "Component Factory""></a></h3><p>The ServerComponentsFactory creates appropriate implementations based on detected task backend configuration.</p><h3 id="component-responsibilities" tabindex="-1">Component Responsibilities <a class="header-anchor" href="#component-responsibilities" aria-label="Permalink to "Component Responsibilities""></a></h3><p>Task management functionality varies between backends:</p><ul><li><strong>Plan Management</strong>: Markdown backends use traditional plan files with checkboxes; beads backends reference task hierarchies</li><li><strong>Instruction Generation</strong>: Markdown backends provide generic task guidance; beads backends provide CLI command guidance</li><li><strong>Task Operations</strong>: Markdown backends store tasks in plan files; beads backends integrate with CLI tools for task lifecycle management</li></ul></div></div></main><footer class="VPDocFooter" data-v-cda1d691 data-v-5253e96b><!--[--><!--]--><!----><nav class="prev-next" aria-labelledby="doc-footer-aria-label" data-v-5253e96b><span class="visually-hidden" id="doc-footer-aria-label" data-v-5253e96b>Pager</span><div class="pager" data-v-5253e96b><!----></div><div class="pager" data-v-5253e96b><a class="VPLink link pager-link next" href="/responsible-vibe-mcp/" data-v-5253e96b><!--[--><span class="desc" data-v-5253e96b>Next page</span><span class="title" data-v-5253e96b>Overview</span><!--]--></a></div></nav></footer><!--[--><!--]--></div></div></div><!--[--><!--]--></div></div><!----><!--[--><!--]--></div></div>
|
|
152
|
-
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"
|
|
152
|
+
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"PD-xOFno\",\"user_agent-setup.md\":\"BhcuRdG8\",\"user_beads-integration.md\":\"BzdR5Fif\",\"user_crowd-mcp-integration.md\":\"C15kSdIJ\",\"user_custom-workflows.md\":\"Cz4IYCXa\",\"user_git-commit-feature.md\":\"UcTvDR-O\",\"user_how-it-works.md\":\"DiOXNgaL\",\"user_long-term-memory.md\":\"DZh0tjNa\",\"user_packaged-workflows.md\":\"s1HT89ZU\",\"user_tutorial.md\":\"Dmj8zLB2\",\"user_workflow-selection.md\":\"CrPGw9Hr\",\"workflows.md\":\"Bm5sGt3u\",\"workflows_adr.md\":\"DEaXkbRp\",\"workflows_big-bang-conversion.md\":\"BA5R1LxZ\",\"workflows_boundary-testing.md\":\"DBcYnMhx\",\"workflows_bugfix.md\":\"CZRCL0Hp\",\"workflows_business-analysis.md\":\"fGLml8Hw\",\"workflows_c4-analysis.md\":\"Dnssqzuf\",\"workflows_epcc.md\":\"M6DnIhpp\",\"workflows_game-beginner.md\":\"CNxzWLtd\",\"workflows_greenfield.md\":\"vx_g-WOe\",\"workflows_minor.md\":\"DdnfwMf4\",\"workflows_posts.md\":\"SOldXvq7\",\"workflows_sdd-bugfix-crowd.md\":\"-lSf42gJ\",\"workflows_sdd-bugfix.md\":\"oRAsEVbc\",\"workflows_sdd-feature-crowd.md\":\"DAtnfCAd\",\"workflows_sdd-feature.md\":\"Ce3-H_g3\",\"workflows_sdd-greenfield-crowd.md\":\"8DUvcmLe\",\"workflows_sdd-greenfield.md\":\"eEN6U0J4\",\"workflows_skilled-bugfix.md\":\"YyOU6NjA\",\"workflows_skilled-epcc.md\":\"BGeI6g1n\",\"workflows_skilled-greenfield.md\":\"CKxrbPQ-\",\"workflows_slides.md\":\"Cqt-19_1\",\"workflows_tdd.md\":\"BjVC69tu\",\"workflows_waterfall.md\":\"CL6jTZP9\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Responsible Vibe MCP\",\"description\":\"Model Context Protocol server for intelligent conversation state management and development guidance\",\"base\":\"/responsible-vibe-mcp/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":true,\"themeConfig\":{\"nav\":[{\"text\":\"Documentation\",\"link\":\"/\"},{\"text\":\"Workflows\",\"link\":\"/workflows\"},{\"text\":\"Github\",\"link\":\"https://github.com/mrsimpson/responsible-vibe-mcp\"}],\"sidebar\":[{\"text\":\"User Guide\",\"items\":[{\"text\":\"Overview\",\"link\":\"/\"},{\"text\":\"How It Works\",\"link\":\"/user/how-it-works\"},{\"text\":\"Agent Setup\",\"link\":\"/user/agent-setup\"},{\"text\":\"Vibe Engineering\",\"link\":\"/user/advanced-engineering\"},{\"text\":\"Long-Term Memory\",\"link\":\"/user/long-term-memory\"},{\"text\":\"Beads-Integration\",\"link\":\"/user/beads-integration\"},{\"text\":\"Tutorial\",\"link\":\"/user/tutorial\"}]},{\"text\":\"Workflows\",\"items\":[{\"text\":\"Workflow-Selection\",\"link\":\"/user/workflow-selection\"},{\"text\":\"Packaged Workflows\",\"link\":\"/user/packaged-workflows\"},{\"text\":\"Custom Workflows\",\"link\":\"/user/custom-workflows\"},{\"text\":\"Explore All Workflows\",\"link\":\"/workflows\"},{\"text\":\"Crowd MCP Integration\",\"link\":\"/user/crowd-mcp-integration\"}]}]},\"locales\":{},\"scrollOffset\":134,\"cleanUrls\":false}");</script>
|
|
153
153
|
|
|
154
154
|
</body>
|
|
155
155
|
</html>
|
|
@@ -91,7 +91,7 @@
|
|
|
91
91
|
<span class="line"><span>fix: resolve database connection issue</span></span>
|
|
92
92
|
<span class="line"><span>docs: update API documentation</span></span>
|
|
93
93
|
<span class="line"><span>test: add integration tests for phase transitions</span></span></code></pre></div><h3 id="pull-request-process" tabindex="-1">Pull Request Process <a class="header-anchor" href="#pull-request-process" aria-label="Permalink to "Pull Request Process""></a></h3><ol><li>Fork the repository</li><li>Create a feature branch</li><li>Make your changes with tests</li><li>Ensure all tests pass (<code>npm run test:all</code>)</li><li>Update documentation as needed</li><li>Submit a pull request</li></ol><h3 id="automated-checks" tabindex="-1">Automated Checks <a class="header-anchor" href="#automated-checks" aria-label="Permalink to "Automated Checks""></a></h3><p>The project includes several automated checks that run on every PR:</p><ul><li><strong>Tests</strong>: Comprehensive test suite including MCP contract tests</li><li><strong>Linting</strong>: Code style and quality checks</li><li><strong>Type Checking</strong>: TypeScript compilation verification</li><li><strong>Build Verification</strong>: Ensures the project builds successfully</li></ul><h3 id="dependency-management" tabindex="-1">Dependency Management <a class="header-anchor" href="#dependency-management" aria-label="Permalink to "Dependency Management""></a></h3><p>This project uses <strong>Renovate</strong> for automated dependency management:</p><ul><li>Automatically creates PRs for dependency updates</li><li>Follows semantic versioning for update scheduling</li><li>Includes security updates with higher priority</li><li>Configuration in <code>.github/renovate.json</code></li><li>Helps keep dependencies current and secure</li></ul><h3 id="release-process" tabindex="-1">Release Process <a class="header-anchor" href="#release-process" aria-label="Permalink to "Release Process""></a></h3><p>The project uses automated releases based on conventional commits:</p><ul><li><code>feat:</code> commits trigger minor version bumps</li><li><code>fix:</code> commits trigger patch version bumps</li><li><code>BREAKING CHANGE:</code> in commit body triggers major version bumps</li></ul></div></div></main><footer class="VPDocFooter" data-v-cda1d691 data-v-5253e96b><!--[--><!--]--><!----><nav class="prev-next" aria-labelledby="doc-footer-aria-label" data-v-5253e96b><span class="visually-hidden" id="doc-footer-aria-label" data-v-5253e96b>Pager</span><div class="pager" data-v-5253e96b><!----></div><div class="pager" data-v-5253e96b><a class="VPLink link pager-link next" href="/responsible-vibe-mcp/" data-v-5253e96b><!--[--><span class="desc" data-v-5253e96b>Next page</span><span class="title" data-v-5253e96b>Overview</span><!--]--></a></div></nav></footer><!--[--><!--]--></div></div></div><!--[--><!--]--></div></div><!----><!--[--><!--]--></div></div>
|
|
94
|
-
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"
|
|
94
|
+
<script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"PD-xOFno\",\"user_agent-setup.md\":\"BhcuRdG8\",\"user_beads-integration.md\":\"BzdR5Fif\",\"user_crowd-mcp-integration.md\":\"C15kSdIJ\",\"user_custom-workflows.md\":\"Cz4IYCXa\",\"user_git-commit-feature.md\":\"UcTvDR-O\",\"user_how-it-works.md\":\"DiOXNgaL\",\"user_long-term-memory.md\":\"DZh0tjNa\",\"user_packaged-workflows.md\":\"s1HT89ZU\",\"user_tutorial.md\":\"Dmj8zLB2\",\"user_workflow-selection.md\":\"CrPGw9Hr\",\"workflows.md\":\"Bm5sGt3u\",\"workflows_adr.md\":\"DEaXkbRp\",\"workflows_big-bang-conversion.md\":\"BA5R1LxZ\",\"workflows_boundary-testing.md\":\"DBcYnMhx\",\"workflows_bugfix.md\":\"CZRCL0Hp\",\"workflows_business-analysis.md\":\"fGLml8Hw\",\"workflows_c4-analysis.md\":\"Dnssqzuf\",\"workflows_epcc.md\":\"M6DnIhpp\",\"workflows_game-beginner.md\":\"CNxzWLtd\",\"workflows_greenfield.md\":\"vx_g-WOe\",\"workflows_minor.md\":\"DdnfwMf4\",\"workflows_posts.md\":\"SOldXvq7\",\"workflows_sdd-bugfix-crowd.md\":\"-lSf42gJ\",\"workflows_sdd-bugfix.md\":\"oRAsEVbc\",\"workflows_sdd-feature-crowd.md\":\"DAtnfCAd\",\"workflows_sdd-feature.md\":\"Ce3-H_g3\",\"workflows_sdd-greenfield-crowd.md\":\"8DUvcmLe\",\"workflows_sdd-greenfield.md\":\"eEN6U0J4\",\"workflows_skilled-bugfix.md\":\"YyOU6NjA\",\"workflows_skilled-epcc.md\":\"BGeI6g1n\",\"workflows_skilled-greenfield.md\":\"CKxrbPQ-\",\"workflows_slides.md\":\"Cqt-19_1\",\"workflows_tdd.md\":\"BjVC69tu\",\"workflows_waterfall.md\":\"CL6jTZP9\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Responsible Vibe MCP\",\"description\":\"Model Context Protocol server for intelligent conversation state management and development guidance\",\"base\":\"/responsible-vibe-mcp/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":true,\"themeConfig\":{\"nav\":[{\"text\":\"Documentation\",\"link\":\"/\"},{\"text\":\"Workflows\",\"link\":\"/workflows\"},{\"text\":\"Github\",\"link\":\"https://github.com/mrsimpson/responsible-vibe-mcp\"}],\"sidebar\":[{\"text\":\"User Guide\",\"items\":[{\"text\":\"Overview\",\"link\":\"/\"},{\"text\":\"How It Works\",\"link\":\"/user/how-it-works\"},{\"text\":\"Agent Setup\",\"link\":\"/user/agent-setup\"},{\"text\":\"Vibe Engineering\",\"link\":\"/user/advanced-engineering\"},{\"text\":\"Long-Term Memory\",\"link\":\"/user/long-term-memory\"},{\"text\":\"Beads-Integration\",\"link\":\"/user/beads-integration\"},{\"text\":\"Tutorial\",\"link\":\"/user/tutorial\"}]},{\"text\":\"Workflows\",\"items\":[{\"text\":\"Workflow-Selection\",\"link\":\"/user/workflow-selection\"},{\"text\":\"Packaged Workflows\",\"link\":\"/user/packaged-workflows\"},{\"text\":\"Custom Workflows\",\"link\":\"/user/custom-workflows\"},{\"text\":\"Explore All Workflows\",\"link\":\"/workflows\"},{\"text\":\"Crowd MCP Integration\",\"link\":\"/user/crowd-mcp-integration\"}]}]},\"locales\":{},\"scrollOffset\":134,\"cleanUrls\":false}");</script>
|
|
95
95
|
|
|
96
96
|
</body>
|
|
97
97
|
</html>
|