@codemcp/workflows 6.3.0 → 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/core/resources/templates/skills/application-design.md +0 -29
- package/packages/core/resources/templates/skills/architecture.md +0 -13
- package/packages/core/resources/templates/skills/coding.md +0 -35
- package/packages/core/resources/templates/skills/starting-project.md +0 -23
- package/packages/core/resources/templates/skills/task-handling.md +0 -19
- package/packages/core/resources/templates/skills/testing.md +0 -20
- package/packages/mcp-server/resources/templates/skills/application-design.md +0 -29
- package/packages/mcp-server/resources/templates/skills/architecture.md +0 -13
- package/packages/mcp-server/resources/templates/skills/coding.md +0 -35
- package/packages/mcp-server/resources/templates/skills/starting-project.md +0 -23
- package/packages/mcp-server/resources/templates/skills/task-handling.md +0 -19
- package/packages/mcp-server/resources/templates/skills/testing.md +0 -20
- package/resources/templates/skills/application-design.md +0 -29
- package/resources/templates/skills/architecture.md +0 -13
- package/resources/templates/skills/coding.md +0 -35
- package/resources/templates/skills/starting-project.md +0 -23
- package/resources/templates/skills/task-handling.md +0 -19
- package/resources/templates/skills/testing.md +0 -20
- /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/{packages/cli/resources/templates/skills/application-design.md → resources/skills/application-design/SKILL.md} +0 -0
- /package/{packages/cli/resources/templates/skills/architecture.md → resources/skills/architecture/SKILL.md} +0 -0
- /package/{packages/cli/resources/templates/skills/coding.md → resources/skills/coding/SKILL.md} +0 -0
- /package/{packages/cli/resources/templates/skills/starting-project.md → resources/skills/starting-project/SKILL.md} +0 -0
- /package/{packages/cli/resources/templates/skills/task-handling.md → resources/skills/task-handling/SKILL.md} +0 -0
- /package/{packages/cli/resources/templates/skills/testing.md → resources/skills/testing/SKILL.md} +0 -0
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
</head>
|
|
21
21
|
<body>
|
|
22
22
|
<div id="app"><div style="position:relative;" data-v-c1df4d5c><div><div id="workflow-visualizer-app" class="" data-v-b5ec7de4><!----><main class="app-main"><div class="diagram-container"><div id="diagram-canvas" class="diagram-canvas"><div class="loading-message">Loading workflow...</div></div></div><aside class="side-panel"><div class="side-panel-header"><h2>Details</h2></div><div class="side-panel-content"><div class="empty-state"> Click on a state or transition to see details </div></div></aside></main><div id="error-container" class="error-container hidden"><div class="error-message"><span class="error-text"></span><button class="error-close">×</button></div></div></div></div></div></div>
|
|
23
|
-
<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\":\"
|
|
23
|
+
<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>
|
|
24
24
|
|
|
25
25
|
</body>
|
|
26
26
|
</html>
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
</head>
|
|
21
21
|
<body>
|
|
22
22
|
<div id="app"><div style="position:relative;" data-v-c1df4d5c><div><div id="workflow-visualizer-app" class="" data-v-b5ec7de4><!----><main class="app-main"><div class="diagram-container"><div id="diagram-canvas" class="diagram-canvas"><div class="loading-message">Loading workflow...</div></div></div><aside class="side-panel"><div class="side-panel-header"><h2>Details</h2></div><div class="side-panel-content"><div class="empty-state"> Click on a state or transition to see details </div></div></aside></main><div id="error-container" class="error-container hidden"><div class="error-message"><span class="error-text"></span><button class="error-close">×</button></div></div></div></div></div></div>
|
|
23
|
-
<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\":\"
|
|
23
|
+
<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>
|
|
24
24
|
|
|
25
25
|
</body>
|
|
26
26
|
</html>
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
</head>
|
|
21
21
|
<body>
|
|
22
22
|
<div id="app"><div class="Layout" data-v-c1df4d5c><!--[--><!--]--><!--[--><span tabindex="-1" data-v-ecac0ce8></span><a href="#VPContent" class="VPSkipLink visually-hidden" data-v-ecac0ce8>Skip to content</a><!--]--><!----><header class="VPNav" data-v-c1df4d5c data-v-b2fedd30><div class="VPNavBar" data-v-b2fedd30 data-v-37a0846a><div class="wrapper" data-v-37a0846a><div class="container" data-v-37a0846a><div class="title" data-v-37a0846a><div class="VPNavBarTitle" data-v-37a0846a data-v-b408e164><a class="title" href="/responsible-vibe-mcp/" data-v-b408e164><!--[--><!--]--><!----><span data-v-b408e164>Responsible Vibe MCP</span><!--[--><!--]--></a></div></div><div class="content" data-v-37a0846a><div class="content-body" data-v-37a0846a><!--[--><!--]--><div class="VPNavBarSearch search" data-v-37a0846a><!----></div><nav aria-labelledby="main-nav-aria-label" class="VPNavBarMenu menu" data-v-37a0846a data-v-27d7d4fe><span id="main-nav-aria-label" class="visually-hidden" data-v-27d7d4fe> Main Navigation </span><!--[--><!--[--><a class="VPLink link VPNavBarMenuLink" href="/responsible-vibe-mcp/" tabindex="0" data-v-27d7d4fe data-v-e70ce59d><!--[--><span data-v-e70ce59d>Documentation</span><!--]--></a><!--]--><!--[--><a class="VPLink link VPNavBarMenuLink active" href="/responsible-vibe-mcp/workflows.html" tabindex="0" data-v-27d7d4fe data-v-e70ce59d><!--[--><span data-v-e70ce59d>Workflows</span><!--]--></a><!--]--><!--[--><a class="VPLink link vp-external-link-icon VPNavBarMenuLink" href="https://github.com/mrsimpson/responsible-vibe-mcp" target="_blank" rel="noreferrer" tabindex="0" data-v-27d7d4fe data-v-e70ce59d><!--[--><span data-v-e70ce59d>Github</span><!--]--></a><!--]--><!--]--></nav><!----><div class="VPNavBarAppearance appearance" data-v-37a0846a data-v-34a9cb79><button class="VPSwitch VPSwitchAppearance" type="button" role="switch" title aria-checked="false" data-v-34a9cb79 data-v-9e7dfa94 data-v-c055c202><span class="check" data-v-c055c202><span class="icon" data-v-c055c202><!--[--><span class="vpi-sun sun" data-v-9e7dfa94></span><span class="vpi-moon moon" data-v-9e7dfa94></span><!--]--></span></span></button></div><!----><div class="VPFlyout VPNavBarExtra extra" data-v-37a0846a data-v-abbdfbda data-v-8b861926><button type="button" class="button" aria-haspopup="true" aria-expanded="false" aria-label="extra navigation" data-v-8b861926><span class="vpi-more-horizontal icon" data-v-8b861926></span></button><div class="menu" data-v-8b861926><div class="VPMenu" data-v-8b861926 data-v-5713f977><!----><!--[--><!--[--><!----><div class="group" data-v-abbdfbda><div class="item appearance" data-v-abbdfbda><p class="label" data-v-abbdfbda>Appearance</p><div class="appearance-action" data-v-abbdfbda><button class="VPSwitch VPSwitchAppearance" type="button" role="switch" title aria-checked="false" data-v-abbdfbda data-v-9e7dfa94 data-v-c055c202><span class="check" data-v-c055c202><span class="icon" data-v-c055c202><!--[--><span class="vpi-sun sun" data-v-9e7dfa94></span><span class="vpi-moon moon" data-v-9e7dfa94></span><!--]--></span></span></button></div></div></div><!----><!--]--><!--]--></div></div></div><!--[--><!--]--><button type="button" class="VPNavBarHamburger hamburger" aria-label="mobile navigation" aria-expanded="false" aria-controls="VPNavScreen" data-v-37a0846a data-v-923ccc68><span class="container" data-v-923ccc68><span class="top" data-v-923ccc68></span><span class="middle" data-v-923ccc68></span><span class="bottom" data-v-923ccc68></span></span></button></div></div></div></div><div class="divider" data-v-37a0846a><div class="divider-line" data-v-37a0846a></div></div></div><!----></header><div class="VPLocalNav empty fixed" data-v-c1df4d5c data-v-d06e114f><div class="container" data-v-d06e114f><!----><div class="VPLocalNavOutlineDropdown" style="--vp-vh:0px;" data-v-d06e114f data-v-aab1d107><button data-v-aab1d107>Return to top</button><!----></div></div></div><!----><div class="VPContent" id="VPContent" data-v-c1df4d5c data-v-28fa4ed1><div class="VPDoc" data-v-28fa4ed1 data-v-cda1d691><!--[--><!--]--><div class="container" data-v-cda1d691><!----><div class="content" data-v-cda1d691><div class="content-container" data-v-cda1d691><!--[--><!--]--><main class="main" data-v-cda1d691><div style="position:relative;" class="vp-doc _responsible-vibe-mcp_workflows" data-v-cda1d691><div><div id="workflow-visualizer-app" class="" data-v-b5ec7de4><header class="app-header"><h1>Workflow Visualizer</h1><div class="workflow-controls"><select id="workflow-selector" class="workflow-selector"><option value="">Select a workflow...</option></select><input type="file" id="file-upload" accept=".yaml,.yml" class="file-upload"><label for="file-upload" class="file-upload-label">Upload YAML</label></div></header><main class="app-main"><div class="diagram-container"><div id="diagram-canvas" class="diagram-canvas"><div class="loading-message">Select a workflow to visualize</div></div></div><aside class="side-panel"><div class="side-panel-header"><h2>Details</h2></div><div class="side-panel-content"><div class="empty-state"> Click on a state or transition to see details </div></div></aside></main><div id="error-container" class="error-container hidden"><div class="error-message"><span class="error-text"></span><button class="error-close">×</button></div></div></div></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><a class="VPLink link pager-link prev" href="/responsible-vibe-mcp/user/custom-workflows.html" data-v-5253e96b><!--[--><span class="desc" data-v-5253e96b>Previous page</span><span class="title" data-v-5253e96b>Custom Workflows</span><!--]--></a></div><div class="pager" data-v-5253e96b><a class="VPLink link pager-link next" href="/responsible-vibe-mcp/user/crowd-mcp-integration.html" data-v-5253e96b><!--[--><span class="desc" data-v-5253e96b>Next page</span><span class="title" data-v-5253e96b>Crowd MCP Integration</span><!--]--></a></div></nav></footer><!--[--><!--]--></div></div></div><!--[--><!--]--></div></div><!----><!--[--><!--]--></div></div>
|
|
23
|
-
<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\":\"
|
|
23
|
+
<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>
|
|
24
24
|
|
|
25
25
|
</body>
|
|
26
26
|
</html>
|
|
@@ -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
|
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: application-design
|
|
3
|
-
description: General conventions when creating an application design
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
practices
|
|
7
|
-
|
|
8
|
-
# Application Design Conventions
|
|
9
|
-
|
|
10
|
-
**Organization:**
|
|
11
|
-
|
|
12
|
-
- Apply the Single Responsibility Principle
|
|
13
|
-
- Use packages with defined interfaces to apply open-close principle for components
|
|
14
|
-
|
|
15
|
-
**APIs:**
|
|
16
|
-
|
|
17
|
-
- Use RESTful conventions
|
|
18
|
-
- Handle 404s gracefully
|
|
19
|
-
|
|
20
|
-
**Validation:**
|
|
21
|
-
|
|
22
|
-
- Validate on client and server
|
|
23
|
-
- Provide immediate feedback
|
|
24
|
-
- Handle edge cases and malicious input
|
|
25
|
-
|
|
26
|
-
**Configurability**
|
|
27
|
-
|
|
28
|
-
- Only provide configurability if explicitly requested
|
|
29
|
-
- If needed, use the registry pattern
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: architecture
|
|
3
|
-
description: General practices to consider when setting up a new application or enhancing it structurally
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Architecture conventions
|
|
7
|
-
|
|
8
|
-
**Organization:**
|
|
9
|
-
|
|
10
|
-
- SRP, separation of concerns, dependency injection
|
|
11
|
-
- Fail fast with clear error messages
|
|
12
|
-
- Use packages with defined interfaces to apply open-close principle for components
|
|
13
|
-
- Start with simple, testable components
|
|
@@ -1,35 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: coding
|
|
3
|
-
description: General practices to consider when writing code
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Coding conventions
|
|
7
|
-
|
|
8
|
-
**Code Quality:**
|
|
9
|
-
|
|
10
|
-
- Write self-documenting code with clear names. Prefer verbose names over comments
|
|
11
|
-
- Comment the intend (why), do not describe the code (how)
|
|
12
|
-
- KISS
|
|
13
|
-
- DRY
|
|
14
|
-
- Prefer simplicity (understandability over elegance)
|
|
15
|
-
|
|
16
|
-
**Error Handling:**
|
|
17
|
-
|
|
18
|
-
- Handle errors explicitly
|
|
19
|
-
- Use explicit error types
|
|
20
|
-
- Provide context in messages
|
|
21
|
-
- Use structured logging and debugger over console.log
|
|
22
|
-
|
|
23
|
-
**Performance:**
|
|
24
|
-
|
|
25
|
-
- Avoid premature optimization
|
|
26
|
-
- Use appropriate data structures
|
|
27
|
-
- Consider memory usage
|
|
28
|
-
- Profile before optimizing
|
|
29
|
-
|
|
30
|
-
**Security:**
|
|
31
|
-
|
|
32
|
-
- Follow OWASP security guidelines and dependency scanning
|
|
33
|
-
- Validate and sanitize inputs
|
|
34
|
-
- Use parameterized queries
|
|
35
|
-
- Never hardcode secrets
|
|
@@ -1,23 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: starting-project
|
|
3
|
-
description: How to set-up the skeleton of a new application
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Starting Project conventions
|
|
7
|
-
|
|
8
|
-
**Check existing structure:**
|
|
9
|
-
|
|
10
|
-
- Look for README.md, package.json, or project files
|
|
11
|
-
- Identify tech stack
|
|
12
|
-
|
|
13
|
-
**Setup patterns:**
|
|
14
|
-
|
|
15
|
-
- Set up gitignore and linting tools
|
|
16
|
-
- Create basic test structure with common framework
|
|
17
|
-
- Add standard build scripts and CI/CD templates
|
|
18
|
-
- Document setup and contribution guidelines
|
|
19
|
-
|
|
20
|
-
**Mandatory user interaction:**
|
|
21
|
-
|
|
22
|
-
- Ask the user for preferences on starter templates
|
|
23
|
-
- Before you write any package or launch a generator, ALWAYS present it to the user and wait for confirmation!
|
|
@@ -1,19 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: task-handling
|
|
3
|
-
description: Important conventions on how to author and work on tasks
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
## Task Writing Methodology
|
|
7
|
-
|
|
8
|
-
**SMART Tasks:**
|
|
9
|
-
|
|
10
|
-
- Use task description for SMART criteria
|
|
11
|
-
- Include all context for new team members
|
|
12
|
-
- Include instructions to research known sources of knowledge
|
|
13
|
-
- Specify dependencies and prerequisites
|
|
14
|
-
|
|
15
|
-
**Task Completion:**
|
|
16
|
-
|
|
17
|
-
- Record results and key findings when completing
|
|
18
|
-
- Document "how it was done" - methods, approaches, decisions
|
|
19
|
-
- Update plan file with key results in addition
|
|
@@ -1,20 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: testing
|
|
3
|
-
description: General practices when writing and executing tests
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
## Testing Best Practices
|
|
7
|
-
|
|
8
|
-
**Test Authoring:**
|
|
9
|
-
|
|
10
|
-
- Test behavior, not implementation
|
|
11
|
-
- Use testing pyramid (many unit, some integration, few E2E)
|
|
12
|
-
- Test edge cases and error conditions
|
|
13
|
-
- Keep tests simple and fast
|
|
14
|
-
|
|
15
|
-
**Test Organization:**
|
|
16
|
-
|
|
17
|
-
- Group related tests
|
|
18
|
-
- Use descriptive test names
|
|
19
|
-
- Follow AAA pattern (Arrange, Act, Assert)
|
|
20
|
-
- Keep test data minimal
|
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: application-design
|
|
3
|
-
description: General conventions when creating an application design
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
practices
|
|
7
|
-
|
|
8
|
-
# Application Design Conventions
|
|
9
|
-
|
|
10
|
-
**Organization:**
|
|
11
|
-
|
|
12
|
-
- Apply the Single Responsibility Principle
|
|
13
|
-
- Use packages with defined interfaces to apply open-close principle for components
|
|
14
|
-
|
|
15
|
-
**APIs:**
|
|
16
|
-
|
|
17
|
-
- Use RESTful conventions
|
|
18
|
-
- Handle 404s gracefully
|
|
19
|
-
|
|
20
|
-
**Validation:**
|
|
21
|
-
|
|
22
|
-
- Validate on client and server
|
|
23
|
-
- Provide immediate feedback
|
|
24
|
-
- Handle edge cases and malicious input
|
|
25
|
-
|
|
26
|
-
**Configurability**
|
|
27
|
-
|
|
28
|
-
- Only provide configurability if explicitly requested
|
|
29
|
-
- If needed, use the registry pattern
|