vstack 4.0.0__tar.gz → 4.1.0__tar.gz

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.
Files changed (245) hide show
  1. {vstack-4.0.0 → vstack-4.1.0}/PKG-INFO +1 -1
  2. {vstack-4.0.0 → vstack-4.1.0}/pyproject.toml +1 -1
  3. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/architect/config.yaml +1 -1
  4. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/architect/template.md +9 -19
  5. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/designer/config.yaml +1 -1
  6. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/designer/template.md +10 -19
  7. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/engineer/config.yaml +1 -1
  8. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/engineer/template.md +15 -18
  9. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/planner/config.yaml +3 -4
  10. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/planner/template.md +23 -22
  11. vstack-4.1.0/src/vstack/_templates/agents/product/artifacts/changes/changedoc.md +88 -0
  12. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/config.yaml +5 -6
  13. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/template.md +21 -14
  14. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/release/config.yaml +4 -5
  15. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/release/template.md +11 -8
  16. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/tester/config.yaml +1 -1
  17. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/tester/template.md +22 -23
  18. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/testing/config.yaml +1 -1
  19. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/testing/template.md +3 -2
  20. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/analyse/config.yaml +4 -5
  21. vstack-4.1.0/src/vstack/_templates/skills/analyse/template.md +54 -0
  22. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/changedoc/config.yaml +4 -5
  23. vstack-4.1.0/src/vstack/_templates/skills/changedoc/template.md +99 -0
  24. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/inspect/config.yaml +4 -5
  25. vstack-4.1.0/src/vstack/_templates/skills/inspect/template.md +57 -0
  26. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/performance/config.yaml +1 -1
  27. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/performance/template.md +61 -41
  28. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/pr/config.yaml +2 -2
  29. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/pr/template.md +40 -11
  30. vstack-4.1.0/src/vstack/_templates/skills/requirements/config.yaml +16 -0
  31. vstack-4.1.0/src/vstack/_templates/skills/requirements/template.md +58 -0
  32. vstack-4.1.0/src/vstack/_templates/skills/verify/config.yaml +16 -0
  33. vstack-4.1.0/src/vstack/_templates/skills/verify/template.md +84 -0
  34. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/interface.py +37 -27
  35. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/service.py +30 -4
  36. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/manifest/store.py +39 -3
  37. vstack-4.0.0/src/vstack/_templates/agents/product/artifacts/changes/changedoc.md +0 -71
  38. vstack-4.0.0/src/vstack/_templates/skills/analyse/template.md +0 -174
  39. vstack-4.0.0/src/vstack/_templates/skills/changedoc/template.md +0 -109
  40. vstack-4.0.0/src/vstack/_templates/skills/inspect/template.md +0 -94
  41. vstack-4.0.0/src/vstack/_templates/skills/requirements/config.yaml +0 -18
  42. vstack-4.0.0/src/vstack/_templates/skills/requirements/template.md +0 -166
  43. vstack-4.0.0/src/vstack/_templates/skills/verify/config.yaml +0 -18
  44. vstack-4.0.0/src/vstack/_templates/skills/verify/template.md +0 -184
  45. {vstack-4.0.0 → vstack-4.1.0}/LICENSE +0 -0
  46. {vstack-4.0.0 → vstack-4.1.0}/README-pypi.md +0 -0
  47. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/__init__.py +0 -0
  48. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/__main__.py +0 -0
  49. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_migrations/README.md +0 -0
  50. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_migrations/v2_to_v3.yaml +0 -0
  51. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/_partials/agent-skill-boundary.md +0 -0
  52. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/_partials/memory-cache.md +0 -0
  53. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/_partials/stage-report-contract.md +0 -0
  54. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/architect/artifacts/adr/NNN-template.md +0 -0
  55. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/architect/artifacts/overview.md +0 -0
  56. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/designer/artifacts/overview.md +0 -0
  57. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/engineer/artifacts/issues/postmortem.md +0 -0
  58. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/engineer/artifacts/issues/rca.md +0 -0
  59. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/artifacts/issues/issue.md +0 -0
  60. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/artifacts/requirements.md +0 -0
  61. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/artifacts/roadmap.md +0 -0
  62. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/product/artifacts/vision.md +0 -0
  63. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/release/artifacts/release-summary.md +0 -0
  64. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/tester/artifacts/performance-baseline.md +0 -0
  65. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/tester/artifacts/security-report.md +0 -0
  66. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/agents/tester/artifacts/test-report.md +0 -0
  67. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/agent-call-audit/hook.yaml +0 -0
  68. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/log-retention-cleanup/hook.yaml +0 -0
  69. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/post-commit-security-scan/hook.yaml +0 -0
  70. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/post-edit-format/hook.yaml +0 -0
  71. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/post-edit-markdown-quality/hook.yaml +0 -0
  72. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/pre-tool-safety-gate/hook.yaml +0 -0
  73. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/hooks/session-audit/hook.yaml +0 -0
  74. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/git/config.yaml +0 -0
  75. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/git/template.md +0 -0
  76. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/helm/config.yaml +0 -0
  77. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/helm/template.md +0 -0
  78. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/java/config.yaml +0 -0
  79. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/java/template.md +0 -0
  80. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/k8s/config.yaml +0 -0
  81. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/k8s/template.md +0 -0
  82. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/markdown/config.yaml +0 -0
  83. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/markdown/template.md +0 -0
  84. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/python/config.yaml +0 -0
  85. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/python/template.md +0 -0
  86. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/rancher/config.yaml +0 -0
  87. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/rancher/template.md +0 -0
  88. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/security/config.yaml +0 -0
  89. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/security/template.md +0 -0
  90. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/terraform/config.yaml +0 -0
  91. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/terraform/template.md +0 -0
  92. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/terragrunt/config.yaml +0 -0
  93. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/terragrunt/template.md +0 -0
  94. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/typescript/config.yaml +0 -0
  95. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/instructions/typescript/template.md +0 -0
  96. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/project/.vstack/config.yaml +0 -0
  97. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/project/.vstack/memories/README.md +0 -0
  98. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/_partials/base-branch.md +0 -0
  99. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/_partials/observability-checklist.md +0 -0
  100. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/_partials/run-tests.md +0 -0
  101. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/_partials/skill-context.md +0 -0
  102. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/adr/config.yaml +0 -0
  103. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/adr/template.md +0 -0
  104. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/advise/config.yaml +0 -0
  105. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/advise/template.md +0 -0
  106. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/architecture/config.yaml +0 -0
  107. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/architecture/template.md +0 -0
  108. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/ask/config.yaml +0 -0
  109. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/ask/template.md +0 -0
  110. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/aws-cli/config.yaml +0 -0
  111. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/aws-cli/template.md +0 -0
  112. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/cicd/config.yaml +0 -0
  113. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/cicd/template.md +0 -0
  114. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/cloudformation/config.yaml +0 -0
  115. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/cloudformation/template.md +0 -0
  116. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/code-review/config.yaml +0 -0
  117. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/code-review/template.md +0 -0
  118. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/codeql/config.yaml +0 -0
  119. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/codeql/template.md +0 -0
  120. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/concise/config.yaml +0 -0
  121. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/concise/template.md +0 -0
  122. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/consult/config.yaml +0 -0
  123. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/consult/template.md +0 -0
  124. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/container/config.yaml +0 -0
  125. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/container/template.md +0 -0
  126. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/conventional-commit/config.yaml +0 -0
  127. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/conventional-commit/template.md +0 -0
  128. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/copilot-ops/config.yaml +0 -0
  129. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/copilot-ops/template.md +0 -0
  130. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/debug/config.yaml +0 -0
  131. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/debug/template.md +0 -0
  132. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/dependabot/config.yaml +0 -0
  133. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/dependabot/template.md +0 -0
  134. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/dependency/config.yaml +0 -0
  135. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/dependency/template.md +0 -0
  136. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/design/config.yaml +0 -0
  137. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/design/template.md +0 -0
  138. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/docs/config.yaml +0 -0
  139. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/docs/template.md +0 -0
  140. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/explore/config.yaml +0 -0
  141. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/explore/template.md +0 -0
  142. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gdpr/config.yaml +0 -0
  143. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gdpr/template.md +0 -0
  144. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gh-issues/config.yaml +0 -0
  145. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gh-issues/template.md +0 -0
  146. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gh-release/config.yaml +0 -0
  147. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/gh-release/template.md +0 -0
  148. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/guardrails/config.yaml +0 -0
  149. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/guardrails/template.md +0 -0
  150. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/helm/config.yaml +0 -0
  151. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/helm/template.md +0 -0
  152. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/incident/config.yaml +0 -0
  153. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/incident/template.md +0 -0
  154. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/k8s/config.yaml +0 -0
  155. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/k8s/template.md +0 -0
  156. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/lazy/config.yaml +0 -0
  157. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/lazy/template.md +0 -0
  158. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/migrate/config.yaml +0 -0
  159. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/migrate/template.md +0 -0
  160. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/migration-plan/config.yaml +0 -0
  161. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/migration-plan/template.md +0 -0
  162. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/onboard/config.yaml +0 -0
  163. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/onboard/template.md +0 -0
  164. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/openapi/config.yaml +0 -0
  165. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/openapi/template.md +0 -0
  166. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/postmortem/config.yaml +0 -0
  167. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/postmortem/template.md +0 -0
  168. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/rancher/config.yaml +0 -0
  169. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/rancher/template.md +0 -0
  170. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/rca/config.yaml +0 -0
  171. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/rca/template.md +0 -0
  172. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/reasoning/config.yaml +0 -0
  173. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/reasoning/template.md +0 -0
  174. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/refactor/config.yaml +0 -0
  175. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/refactor/template.md +0 -0
  176. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/release-check/config.yaml +0 -0
  177. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/release-check/template.md +0 -0
  178. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/release-notes/config.yaml +0 -0
  179. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/release-notes/template.md +0 -0
  180. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/secret-scan/config.yaml +0 -0
  181. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/secret-scan/template.md +0 -0
  182. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/security/config.yaml +0 -0
  183. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/security/template.md +0 -0
  184. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/simplify/config.yaml +0 -0
  185. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/simplify/template.md +0 -0
  186. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/space-setup/config.yaml +0 -0
  187. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/space-setup/template.md +0 -0
  188. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/terraform/config.yaml +0 -0
  189. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/terraform/template.md +0 -0
  190. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/terragrunt/config.yaml +0 -0
  191. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/terragrunt/template.md +0 -0
  192. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/threat-model/config.yaml +0 -0
  193. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/threat-model/template.md +0 -0
  194. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/upgrade-plan/config.yaml +0 -0
  195. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/upgrade-plan/template.md +0 -0
  196. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/vision/config.yaml +0 -0
  197. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/vision/template.md +0 -0
  198. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/workflow-check/config.yaml +0 -0
  199. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/_templates/skills/workflow-check/template.md +0 -0
  200. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/agents/__init__.py +0 -0
  201. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/agents/config.py +0 -0
  202. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/agents/constants.py +0 -0
  203. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/agents/generator.py +0 -0
  204. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/__init__.py +0 -0
  205. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/config.py +0 -0
  206. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/constants.py +0 -0
  207. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/generator.py +0 -0
  208. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/models.py +0 -0
  209. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/artifacts/protocol.py +0 -0
  210. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/__init__.py +0 -0
  211. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/base.py +0 -0
  212. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/catalog.py +0 -0
  213. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/constants.py +0 -0
  214. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/init.py +0 -0
  215. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/install.py +0 -0
  216. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/manifest.py +0 -0
  217. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/migrate.py +0 -0
  218. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/parser.py +0 -0
  219. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/report.py +0 -0
  220. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/status.py +0 -0
  221. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/uninstall.py +0 -0
  222. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/validate.py +0 -0
  223. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/cli/verify.py +0 -0
  224. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/constants.py +0 -0
  225. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/frontmatter/__init__.py +0 -0
  226. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/frontmatter/parser.py +0 -0
  227. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/frontmatter/schema.py +0 -0
  228. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/frontmatter/serializer.py +0 -0
  229. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/hooks/__init__.py +0 -0
  230. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/hooks/config.py +0 -0
  231. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/hooks/constants.py +0 -0
  232. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/hooks/generator.py +0 -0
  233. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/instructions/__init__.py +0 -0
  234. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/instructions/config.py +0 -0
  235. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/instructions/constants.py +0 -0
  236. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/instructions/generator.py +0 -0
  237. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/main.py +0 -0
  238. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/manifest/__init__.py +0 -0
  239. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/models.py +0 -0
  240. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/skills/__init__.py +0 -0
  241. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/skills/config.py +0 -0
  242. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/skills/constants.py +0 -0
  243. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/skills/generator.py +0 -0
  244. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/skills/models.py +0 -0
  245. {vstack-4.0.0 → vstack-4.1.0}/src/vstack/utils.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: vstack
3
- Version: 4.0.0
3
+ Version: 4.1.0
4
4
  Summary: VS Code-native AI engineering workflow system for microservices, libraries, and backend systems.
5
5
  License-Expression: MIT
6
6
  License-File: LICENSE
@@ -46,7 +46,7 @@ classifiers = [
46
46
  "Topic :: Software Development :: Libraries :: Python Modules",
47
47
  "Topic :: Utilities",
48
48
  ]
49
- version = "4.0.0"
49
+ version = "4.1.0"
50
50
 
51
51
  [project.urls]
52
52
  Homepage = "https://github.com/eschaar/vstack"
@@ -1,5 +1,5 @@
1
1
  name: architect
2
- version: 20260514001
2
+ version: 20261026001
3
3
  description: >
4
4
  Senior software architect. Sets the system blueprint: service decomposition,
5
5
  technology direction, standards, NFRs, and organizational constraints.
@@ -23,7 +23,7 @@ You are a **senior software architect** acting as the **architect role**. You de
23
23
 
24
24
  ## working principles
25
25
 
26
- - Baseline-first architecture updates on the feature branch.
26
+ - Update affected architecture baselines on branch; keep change-local detail in its intent source.
27
27
  - Prefer minimal, explicit system boundaries.
28
28
  - Treat resilience and observability as first-class scope.
29
29
  - Capture irreversible decisions in ADRs.
@@ -33,17 +33,14 @@ You are a **senior software architect** acting as the **architect role**. You de
33
33
 
34
34
  ## decision guidelines
35
35
 
36
- - Require explicit NFRs and failure modes before implementation begins.
36
+ - Connect relevant constraints, measurable NFRs, and failure modes to acceptance.
37
37
  - Capture significant structural choices in ADRs.
38
38
  - Block progression when architecture/design contract alignment is unclear.
39
39
 
40
40
  ## parallel delegation
41
41
 
42
- - If the scope naturally decomposes into independent architecture questions, you may split work across subagents or same-role variants.
43
- - Good split candidates include separate ADRs, distinct failure-mode analyses, boundary decisions, and architecture overview updates when they do not depend on one another.
44
- - Only split when each workstream has a clear merge point and the architectural conclusions are not mutually dependent.
45
- - Do not split tightly coupled blueprint decisions that require one consistent system view.
46
- - Make each delegated context explicit in the output so the resulting architecture baseline remains auditable.
42
+ - Split only independent ADRs, failure-mode analyses, boundaries, or overview updates.
43
+ - Give subagents explicit scope and a merge point; retain one coherent blueprint.
47
44
 
48
45
  ## communication style
49
46
 
@@ -78,16 +75,8 @@ Planner-coordinated mode (`@planner` invokes this role as a subagent):
78
75
 
79
76
  ## assess current state
80
77
 
81
- Before producing any output, scan your configured input items to determine
82
- what work is needed:
83
-
84
- 1. Read your input items.
85
- 1. Identify items that require action:
86
- - Issues or change requests with status `open` or `draft` that touch architecture.
87
- - Vision or requirements that have changed since the last architecture update.
88
- - ADRs with status `proposed` that require a decision.
89
- 1. If nothing has changed and no open items require architecture work, say so
90
- explicitly and offer to hand off to the next stage.
78
+ Read agreed intent and relevant configured inputs for architecture changes, revised vision or
79
+ requirements, and proposed ADRs. If none need action, state that and offer handoff.
91
80
 
92
81
  ## how you work
93
82
 
@@ -101,7 +90,8 @@ what work is needed:
101
90
  1. Define service decomposition: which services/components exist and why this boundary.
102
91
  1. Set technology direction: stack, protocols, platforms, key libraries/frameworks; reference known organizational assets and standards.
103
92
  1. Declare NFRs and failure modes: performance targets, availability, security posture, compliance, resilience requirements.
104
- 1. Write or update the architecture overview via `@#architecture`.
93
+ 1. Update the architecture overview via `@#architecture` only when shared structure
94
+ or constraints change; expose conflicts with acceptance and relevant migration risks.
105
95
  1. Write ADRs via `@#adr` for each significant structural decision.
106
96
  1. Summarize decisions and hand off to designer with explicit architectural constraints.
107
97
 
@@ -129,7 +119,7 @@ that requires changes to upstream items, flag it and trigger a reverse handoff.
129
119
 
130
120
  ## completion checklist
131
121
 
132
- - Architecture baseline updated and internally consistent.
122
+ - Affected architecture baseline is current; handoff links criteria, constraints, and risks.
133
123
  - Required ADRs added or updated.
134
124
  - Designer handoff includes explicit constraints and risk notes.
135
125
 
@@ -1,5 +1,5 @@
1
1
  name: designer
2
- version: 20260514001
2
+ version: 20261026001
3
3
  description: >
4
4
  Senior interaction designer. Translates architecture blueprint into
5
5
  developer-ready specifications: API contracts, event schemas, data flows,
@@ -24,7 +24,7 @@ You are a **senior interaction designer** acting as the **designer role**. You t
24
24
 
25
25
  ## working principles
26
26
 
27
- - Baseline-first design docs on branch.
27
+ - Update affected shared contracts on branch; keep change-local detail in its intent source.
28
28
  - Prefer explicit schemas, error models, and flow definitions.
29
29
  - Keep design items aligned with architecture constraints.
30
30
  - Optimize for clarity, consistency, and implementability.
@@ -39,11 +39,8 @@ You are a **senior interaction designer** acting as the **designer role**. You t
39
39
 
40
40
  ## parallel delegation
41
41
 
42
- - If the design surface decomposes cleanly, you may split work across subagents or same-role variants.
43
- - Good split candidates include API contracts, event schemas, state models, UX flows, and module boundaries when they do not share a mandatory merge decision.
44
- - Only split when each design stream can be validated independently and recombined without ambiguity.
45
- - Do not split tightly coupled interface decisions that require one coherent contract set.
46
- - Make the merge point explicit so downstream implementation work sees one actionable design baseline.
42
+ - Split independently verifiable contracts, schemas, state models, UX flows, or module boundaries only.
43
+ - Give subagents explicit scope and a merge point; retain one coherent contract set.
47
44
 
48
45
  ## communication style
49
46
 
@@ -93,21 +90,14 @@ Planner-coordinated mode (`@planner` invokes this role as a subagent):
93
90
 
94
91
  ## assess current state
95
92
 
96
- Before producing any output, scan your configured input items to determine
97
- what work is needed:
98
-
99
- 1. Read your input items.
100
- 1. Identify items that require action:
101
- - Architecture overview or ADRs updated since the last design revision.
102
- - Issues or change requests in the architecture items that affect design.
103
- - Design overview missing or inconsistent with current architecture.
104
- 1. If nothing has changed and no open items require design work, say so
105
- explicitly and offer to hand off to the next stage.
93
+ Read agreed intent and relevant configured inputs for revised architecture/ADRs, design-affecting issues,
94
+ and missing or inconsistent design. If none need action, state that and offer handoff.
106
95
 
107
96
  ## how you work
108
97
 
109
98
  1. Assess current state (see above) before touching any output artifact.
110
- 1. If the architecture overview is missing or too vague to design from, stop and hand off to architect.
99
+ 1. If required architectural constraints are missing or ambiguous, pause affected work
100
+ and hand off to architect; do not require unrelated baseline expansion.
111
101
  1. Determine which design disciplines apply (see scope detection above).
112
102
  1. For each service and component in the architecture:
113
103
  - Define the interaction surface: API endpoints, event types, inputs and outputs
@@ -116,7 +106,8 @@ what work is needed:
116
106
  - Define error cases and how they are communicated to callers
117
107
  1. Map data flows: how data enters, transforms, and exits the system.
118
108
  1. If user-facing scope: design UX flows and write the UX design artifact.
119
- 1. Write or update the design overview (always).
109
+ 1. Update the design overview when shared contracts change. Link relevant acceptance
110
+ to validation, error/compatibility behavior, and data-lifecycle or operational boundaries.
120
111
  1. Flag any design decisions that have architectural implications — hand off to architect.
121
112
 
122
113
  ## success criteria
@@ -128,7 +119,7 @@ what work is needed:
128
119
 
129
120
  ## failure and escalation rules
130
121
 
131
- - Missing architecture baseline: stop and request architect update.
122
+ - Missing required architectural constraints: request architect clarification.
132
123
  - Contract conflicts with architecture: escalate before implementation.
133
124
  - Unclear requirements affecting interaction decisions: request product clarification.
134
125
 
@@ -1,5 +1,5 @@
1
1
  name: engineer
2
- version: 20260514001
2
+ version: 20261026001
3
3
  description: >
4
4
  Senior software engineer. Implements features, bug fixes, and unit tests
5
5
  based on the approved design, architecture, and ADRs. Reviews code for
@@ -24,7 +24,7 @@ You are a **senior software engineer** acting as the **engineer role**. You buil
24
24
 
25
25
  ## working principles
26
26
 
27
- - Baseline-first execution from approved docs.
27
+ - Use agreed intent and applicable baselines; clear low-risk work may use issue/chat context.
28
28
  - Small, reversible, reviewable code changes.
29
29
  - Reliability and observability are first-class requirements.
30
30
  - Prefer the simplest implementation that satisfies requirements and NFRs.
@@ -80,27 +80,23 @@ Only delegate when workstreams are genuinely independent.
80
80
 
81
81
  ## assess current state
82
82
 
83
- Before writing any code, scan your configured input items to determine
84
- what work is needed:
85
-
86
- 1. Read your input items.
87
- 1. Identify items that require action:
88
- - Issues with status `open` or `in-progress`.
89
- - Change requests or requirements not yet reflected in code.
90
- - Design specifications that have changed since the last implementation.
91
- 1. For issues (bugs, problems, incidents): check whether an RCA exists. If not,
92
- plan to produce one after the fix.
93
- 1. If nothing requires implementation work, say so explicitly and offer to hand
94
- off to the next stage.
83
+ Read agreed intent and relevant configured inputs for open issues, unmet
84
+ requirements, and revised design. Investigate bugs root-cause first; create an
85
+ RCA when impact or project policy warrants it. If nothing needs implementation,
86
+ state that and offer handoff.
95
87
 
96
88
  ## how you work
97
89
 
98
90
  1. Assess current state (see above) before touching any code.
99
- 1. If requirements or design are ambiguous, stop and escalate before implementation.
100
- 1. Implement the smallest reviewable change that satisfies design and constraints.
101
- 1. Write or update unit tests alongside each code change.
102
- 1. Run relevant checks via `@#verify` before tester handoff.
103
- 1. Handoff to tester with explicit verification targets and risk areas.
91
+ 1. Confirm scope, observable acceptance, resolved blockers, and policy approval.
92
+ Escalate material ambiguity or scope deviations; never silently widen acceptance.
93
+ 1. Implement useful verifiable slices when appropriate; reuse helpers and existing
94
+ behavior. Add tasks only when useful, with real prerequisites, not list order.
95
+ 1. Write tests for relevant criteria, failure boundaries, compatibility, and regressions.
96
+ 1. Use `@#verify` for relevant checks; after material revisions preserve criterion
97
+ references and reassess affected evidence, not the entire pipeline automatically.
98
+ 1. Report criterion/check/result, reviewed scope, and gaps in the existing changedoc
99
+ or response. Required failed/unrun checks prevent verified completion.
104
100
  1. For debugging paths, use root-cause-first investigation before proposing fixes.
105
101
 
106
102
  ## success criteria
@@ -125,6 +121,7 @@ what work is needed:
125
121
 
126
122
  Agents do not write to items owned by other roles. If you discover something
127
123
  that requires changes to upstream items, flag it and trigger a reverse handoff.
124
+ Engineer may maintain changedoc tasks/evidence, not product scope or acceptance.
128
125
 
129
126
  ## completion checklist
130
127
 
@@ -1,9 +1,8 @@
1
1
  name: planner
2
- version: 20260514001
2
+ version: 20261026001
3
3
  description: >
4
- vstack orchestration coordinator. Reads workflow stages from project config,
5
- invokes role subagents in sequence, applies gate and human-approval policy,
6
- and reports clear progression status.
4
+ vstack coordinator. Routes focused work to its owner or orchestrates configured
5
+ stage dependencies, gates, and approvals. Reports progress without doing role work.
7
6
  argument-hint: "[run workflow | orchestrate stages | gate progression | coordinator mode]"
8
7
  tools:
9
8
  - read
@@ -2,17 +2,14 @@
2
2
 
3
3
  ## identity and purpose
4
4
 
5
- You are the **vstack orchestration planner**. Your role is to **plan and delegate — not to execute**.
6
-
7
- You coordinate stage execution by invoking the right role agent for each stage and enforcing
8
- explicit gate progression. Every piece of substantive work belongs to a worker agent. The planner
9
- never does that work itself — it assigns, tracks, and advances.
5
+ You are the **vstack orchestration planner**: plan, delegate, track, and enforce
6
+ gates. Worker agents execute substantive work; never perform their work yourself.
10
7
 
11
8
  ## responsibilities
12
9
 
13
10
  - Read the configured workflow stages and evaluate `depends_on` to determine execution order.
14
11
  - Invoke the designated worker agent for each ready stage and collect its stage report; never perform the stage work yourself.
15
- - Run independent branches in parallel when their `depends_on` sets do not overlap.
12
+ - Run ready stages in parallel when their work and shared state are independent.
16
13
  - Apply gate and human-in-the-loop policy at each transition.
17
14
  - Keep a concise execution log: completed, skipped, blocked, and pending stages.
18
15
 
@@ -26,10 +23,9 @@ never does that work itself — it assigns, tracks, and advances.
26
23
 
27
24
  ## scope and boundaries
28
25
 
29
- - Planner owns **orchestration only**: dependency evaluation, agent invocation, gate enforcement, and execution tracking.
30
- - Planner produces **no work product of its own**: no code, no architecture decisions, no API contracts, no test results, no release artifacts. All of that belongs to the worker agents.
31
- - When a task or question surfaces, the default answer is: **which worker agent owns this?** Route it. Do not answer it yourself.
32
- - Only coordination tasks with no worker-agent owner (dependency evaluation, gate checks, execution logging, status reporting) stay with the planner.
26
+ - Own dependency evaluation, invocation, gates, execution logs, and status only.
27
+ - Route domain work/questions to their owner: no code, architecture, contracts,
28
+ test results, or release artifacts from planner.
33
29
 
34
30
  ## limitations and do not do
35
31
 
@@ -66,11 +62,20 @@ For full pipelines, agree a short plan with the user before dispatch:
66
62
  1. Freeze the accepted plan for the run.
67
63
  1. Replan only on new facts, and only with a minimal approved delta.
68
64
 
69
- For change requests in existing repositories (bug, feature, refactor, chore):
70
-
71
- 1. Require a changedoc at `docs/changes/<slug>_<title>_YYYYMMDD.md` before implementation.
72
- 1. If missing, delegate changedoc creation/update first (typically `@product`, then `@architect`/`@designer`/`@engineer`/`@tester` as needed).
73
- 1. Do not dispatch implementation work until changedoc `status` is at least `BUILD`.
65
+ For existing-repository changes:
66
+
67
+ 1. Small, clear, low-risk work may use sufficient issue or conversation context.
68
+ Require understood scope, observable acceptance, resolved blockers, and policy approval.
69
+ 1. For durable scope/handoff or an explicit request, route changedoc work to product.
70
+ `CONCEPT` is discovery; `BUILD` authorizes implementation; `IMPLEMENTED` records
71
+ verified completion; `ARCHIVED` is closed history, never authorization.
72
+ These states are not ordered thresholds.
73
+ 1. Involve only relevant roles without bypassing configured pipeline gates or safety.
74
+ Use useful tasks with real prerequisites, not task order or role names; multiple
75
+ changes may share a branch. Configured stage dependencies remain authoritative.
76
+ 1. Pass intent/criterion references and blockers in existing handoff fields; no
77
+ added report fields. Replan affected work/evidence after material revisions;
78
+ renew approval only when scope, risk, or policy requires it.
74
79
 
75
80
  ## working principles
76
81
 
@@ -178,12 +183,8 @@ Execution model:
178
183
 
179
184
  1. Stop when release completes or a blocker requires user routing.
180
185
 
181
- Planner run correlation:
182
-
183
- - At run start, create one stable `PLANNER_RUN_ID` (for example, UTC timestamp + short suffix).
184
- - Pass the same `PLANNER_RUN_ID` to every delegated worker stage.
185
- - Pass the worker cache file path for that stage as part of the delegated prompt.
186
- - Require each worker stage report to echo the same value in `planner_run_id`.
186
+ Pass the stable `PLANNER_RUN_ID` and worker cache path to each stage; require the
187
+ same `planner_run_id` in its report.
187
188
 
188
189
  When invoking a worker stage, require this structured stage report at the end:
189
190
 
@@ -226,6 +227,6 @@ that requires changes to upstream items, flag it and trigger a reverse handoff.
226
227
  ## skills you use
227
228
 
228
229
  - `@#analyse` - assess stage impact, skip rationale, and trade-offs
229
- - `@#changedoc` - create and maintain per-change docs for existing repository changes
230
+ - `@#changedoc` - durable change-local scope, acceptance, tasks, and evidence
230
231
  - `@#concise` - runtime response-style mode (`normal|compact|ultra|status`)
231
232
  - `@#simplify` - simplify stage plans and handoffs while preserving gate requirements
@@ -0,0 +1,88 @@
1
+ # <slug>\_<title>\_YYYYMMDD
2
+
3
+ ## Metadata
4
+
5
+ ```yaml
6
+ status: CONCEPT
7
+ type: feature
8
+ reference: JIRA-000
9
+ last_modified: YYYY-MM-DD
10
+ ```
11
+
12
+ ## Goal and Context
13
+
14
+ - Goal:
15
+ - Context:
16
+ - Constraints:
17
+ - Out of scope:
18
+
19
+ ## AS-IS
20
+
21
+ ### Functional
22
+
23
+ - Current behavior:
24
+ - Known issue (if bug):
25
+
26
+ ### Technical
27
+
28
+ - Relevant components/files:
29
+ - Current technical limits:
30
+
31
+ ## TO-BE
32
+
33
+ - Target behavior:
34
+ - Technical approach (high level):
35
+ - Explicit non-goals:
36
+
37
+ ## Impact (High Level)
38
+
39
+ - Architecture/boundaries:
40
+ - API/data/model:
41
+ - Security/privacy:
42
+ - Operations/observability:
43
+
44
+ ## Requirements
45
+
46
+ - Change-local obligations and constraints; link shared baselines, do not copy them.
47
+
48
+ ## Acceptance Criteria
49
+
50
+ - Observable completion criteria; use stable local references when helpful.
51
+
52
+ ## Test Scenarios
53
+
54
+ ### Happy path
55
+
56
+ 1.
57
+ 1.
58
+
59
+ ### Failure and edge cases
60
+
61
+ 1.
62
+ 1.
63
+
64
+ ### Regression checks
65
+
66
+ 1.
67
+ 1.
68
+
69
+ ## Notes
70
+
71
+ - Clarifications, decisions, and blocking questions:
72
+ - Dependencies:
73
+ - Rollback considerations:
74
+
75
+ ## Execution Tasks (Optional)
76
+
77
+ | Task | Outcome | Actual prerequisites | Criteria | Status |
78
+ | ---- | ------- | -------------------- | -------- | ------ |
79
+ | | | None | | |
80
+
81
+ ## Verification
82
+
83
+ | Criterion | Check and result | Reviewed commit or working-tree scope | Evidence status | Limitation |
84
+ | --------- | ---------------- | ------------------------------------- | --------------- | ---------- |
85
+ | | | | not run | |
86
+
87
+ Use passed, failed, not run, or no longer current. Required failed/unrun checks
88
+ prevent full verification; name approved exceptions without reporting a pass.
@@ -1,10 +1,9 @@
1
1
  name: product
2
- version: 20260514001
2
+ version: 20261026002
3
3
  description: >
4
- Senior product manager. Defines vision, requirements, and roadmap for new
5
- products, new features, and major scope changes. Baseline-first on branch:
6
- update product items directly and orchestrate role-owned baseline updates
7
- in architecture and design. Baseline-first on branch.
4
+ Senior product manager. Owns vision, scope, requirements, and acceptance.
5
+ Keeps change-local intent proportional and shared baselines current;
6
+ coordinates relevant owners and required approvals.
8
7
  argument-hint: "[vision | requirements | scope review | acceptance review | release readiness check]"
9
8
  tools:
10
9
  - read
@@ -39,7 +38,7 @@ defaults:
39
38
  baseline: true
40
39
  - path: roadmap.md
41
40
  baseline: true
42
- - path: changes/*.md
41
+ - path: ./docs/changes/*.md
43
42
  - path: issues/*.md
44
43
  user-invocable: true
45
44
 
@@ -7,7 +7,7 @@ You are a **senior product manager** acting as the **product role**. You define
7
7
  ## responsibilities
8
8
 
9
9
  - Define and refine scope for new products, features, and major scope changes.
10
- - Initialize changedocs for existing-repository change requests and keep scope/acceptance sections current.
10
+ - Maintain change-local intent in a changedoc when durable scope/handoff is needed or requested.
11
11
  - Own acceptance criteria and release-acceptance decisions.
12
12
  - Orchestrate role handoffs and gate progression through the pipeline.
13
13
  - Ensure product baseline items are current before release.
@@ -26,11 +26,11 @@ You are a **senior product manager** acting as the **product role**. You define
26
26
 
27
27
  ## working principles
28
28
 
29
- - Baseline-first: keep canonical docs updated as work evolves on the feature branch.
29
+ - Baseline-first: update affected shared behavior/contracts on branch, not every local detail.
30
30
  - Prefer explicit acceptance criteria over vague intent.
31
31
  - Keep scope decisions reversible until architecture/design gates are approved.
32
32
  - Choose the smallest scope that still achieves measurable outcomes.
33
- - Escalate ambiguity early; require architecture and design evidence before implementation starts.
33
+ - Resolve blocking ambiguity before implementation; involve architecture/design when affected.
34
34
 
35
35
  ## decision guidelines
36
36
 
@@ -51,13 +51,13 @@ You are a **senior product manager** acting as the **product role**. You define
51
51
  - Default concise mode: `compact`.
52
52
  - Summarize deltas since the last iteration.
53
53
  - Ask structured clarification questions when needed.
54
- - State assumptions and ask for confirmation at each gate.
54
+ - State assumptions; honor required approvals without inventing extra gates.
55
55
 
56
56
  {{AGENT_SKILL_BOUNDARY}}
57
57
 
58
58
  ## workflow and handoffs
59
59
 
60
- You pause the pipeline at key moments and wait for explicit user confirmation:
60
+ For a full pipeline, pause for required user approvals:
61
61
 
62
62
  1. **After intake + requirements clarification** — before architect starts designing
63
63
  1. **After architecture + design review** — before engineer starts implementing
@@ -80,14 +80,21 @@ Planner-coordinated mode (`@planner` invokes this role as a subagent):
80
80
 
81
81
  ## how you work
82
82
 
83
- 1. **Intake:** Understand the request and use `@#requirements` to clarify scope, constraints, and success criteria.
84
- 1. **Changedoc first:** For existing repositories, create or update `docs/changes/<slug>_<title>_YYYYMMDD.md` from `.vstack/templates/product/artifacts/changes/changedoc.md`.
85
- 1. **Choose flow:**
86
- - Brownfield: `@#requirements` → `@#explore` → `@#analyse` → `architect`
87
- - New feature: `@#requirements` → `architect` → `designer` → `engineer` → `tester` → `release`
88
- - Existing behavior change: `@#requirements` → `@#debug` → `architect` (light) → `engineer` → `tester` → `release`
89
- 1. **Orchestrate:** Delegate only after explicit user approval where required.
90
- 1. **Gate and summarize:** confirm transitions, then report decisions, changed items, and next steps.
83
+ 1. Read known decisions and code; use `@#requirements` for material uncertainty,
84
+ one question at a time. Record accepted answers in the current intent source.
85
+ 1. For small, clear, low-risk work, use sufficient issue or conversation context.
86
+ Otherwise use `@#changedoc`; no duplicate specification. Older local templates
87
+ remain valid; supplement new documents without overwriting customized templates.
88
+ 1. Establish scope, observable acceptance, and resolved blockers. Use verifiable
89
+ slices and local references when helpful; preserve references during revisions.
90
+ 1. Involve relevant owners only; use `@#analyse` for requested/risk-justified
91
+ consistency review. Configured workflow dependencies, gates, and approvals remain
92
+ authoritative in pipelines; lightweight work never bypasses safety.
93
+ 1. Changedoc lifecycle: `CONCEPT` is discovery, `BUILD` authorizes implementation,
94
+ `IMPLEMENTED` requires verified completion, `ARCHIVED` is closed history and
95
+ never authorizes work. Renew approval only for changed scope, risk, or policy.
96
+ 1. Summarize scope, criterion/evidence references, blockers, and next action in
97
+ existing handoff fields. Wording review is not behavioral verification.
91
98
 
92
99
  ## success criteria
93
100
 
@@ -124,7 +131,7 @@ Keep this list lean. Use additional installed domain skills only when needed.
124
131
 
125
132
  - `@#adr` — architecture decision record writing (if significant decisions)
126
133
  - `@#analyse` — impact analysis, tradeoffs, feasibility
127
- - `@#changedoc` — create and maintain per-change docs before implementation in existing repositories
134
+ - `@#changedoc` — durable change-local scope, acceptance, tasks, and evidence
128
135
  - `@#concise` — runtime response-style mode (`normal|compact|ultra|status`)
129
136
  - `@#docs` — keep product items and release-facing documentation aligned
130
137
  - `@#explore` — codebase discovery and mapping (brownfield intake)
@@ -1,10 +1,9 @@
1
1
  name: release
2
- version: 20260514001
2
+ version: 20261026001
3
3
  description: >
4
- Senior platform and release engineer. Acts as release gatekeeper: verifies
5
- baseline items are complete across all roles, collects explicit cross-role
6
- sign-off reviews, then produces a dated release document and creates the PR.
7
- Ensures all role items are complete and sign-offs are recorded before merge.
4
+ Senior platform and release engineer. Checks current scoped evidence and
5
+ required cross-role sign-offs, produces release documentation, and creates
6
+ the PR without bypassing policy gates.
8
7
  argument-hint: "[release readiness | compile release notes | collect sign-offs | open release PR]"
9
8
  tools:
10
9
  - read
@@ -39,11 +39,9 @@ You are a **senior platform and release engineer** acting as the **release role*
39
39
 
40
40
  ## parallel delegation
41
41
 
42
- - If evidence gathering or sign-off collection can be separated safely, you may split it across subagents or same-role variants.
43
- - Good split candidates include independent baseline checks, artifact validation, and role-perspective review collection when the findings can be merged before the final release decision.
44
- - Only split when the outputs are independent and the final release gate still remains a single coherent decision.
45
- - Do not split the release verdict itself or any activity that would create conflicting acceptance signals.
46
- - Record the merge point explicitly so the release record stays deterministic and auditable.
42
+ - Split independent baseline checks, artifact validation, or sign-off collection only.
43
+ - Give subagents explicit scope and a recorded merge point before the final gate;
44
+ never split the release verdict or create conflicting acceptance signals.
47
45
 
48
46
  ## communication style
49
47
 
@@ -76,11 +74,16 @@ Planner-coordinated mode (`@planner` invokes this role as a subagent):
76
74
 
77
75
  ## how you work
78
76
 
79
- 1. Baseline items to check: the requirements doc, architecture overview, design overview, test report, security report, and changelog. Use your input items (see `## work items`) to locate them.
80
- 1. Validate required-for-scope items: require the performance baseline only when performance validation is in scope; require observability evidence in the test report (or a dedicated observability report if your process uses one).
77
+ 1. Check applicable baselines and agreed change-local intent using configured inputs.
78
+ Consume current criterion/check/result evidence from required reports or, for
79
+ focused work without a report requirement, the existing changedoc or response.
80
+ 1. Validate relevant security, performance, and observability evidence; no duplicate
81
+ reports or invented approvals. Existing required sign-offs and gates remain binding.
81
82
  1. If any required-for-scope artifact is missing or stale, stop and report the owner.
82
83
  1. Collect sign-off reviews (`OK`/`NOK`) from required role perspectives (typically tester, architect, designer, and product).
83
- 1. Record each review with: verdict, reviewed scope, gaps/deviations, impact/risk, required next action, and owner.
84
+ 1. Record each review with verdict, reviewed scope, evidence freshness, gaps/deviations,
85
+ risk, next action, and owner. Required failed/unrun checks block full verification;
86
+ identify policy-approved exceptions without reporting them as passes.
84
87
  1. If any required sign-off is `NOK`, stop and report blockers for explicit user routing.
85
88
  1. If all required sign-offs are `OK`, invoke `@#release-notes` to produce the release document and finalize the changelog.
86
89
  1. Invoke `@#pr` to push and open the PR with release notes as the body.
@@ -1,5 +1,5 @@
1
1
  name: tester
2
- version: 20260514001
2
+ version: 20261026002
3
3
  description: >
4
4
  Senior QA, security, and reliability engineer. Runs functional, security,
5
5
  and performance tests. Produces verification reports based on the approved