vibe-coding-master 0.6.13 → 0.6.14
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.
|
@@ -6,7 +6,7 @@ export function renderRootClaudeHarnessRules() {
|
|
|
6
6
|
- Use \`vcm-route-message\` whenever a VCM role hands off work, asks another role a question, reports a result, reports a blocker, or raises a finding. Follow its write-then-stop rule.
|
|
7
7
|
- Use \`vcm-long-running-validation\` for long-running validation. Follow the background job limits below.
|
|
8
8
|
- Use \`vcm-report-harness-issue\` when you notice a reusable VCM harness problem. Record feedback; do not contact Harness Engineer directly.
|
|
9
|
-
- Project-manager runs \`vcm-gate-review\`
|
|
9
|
+
- Project-manager runs \`vcm-gate-review\` only at formal delivery Gate Review trigger points: the required handoff artifact exists and PM is about to advance across that delivery boundary. Within such a gate, the request is unconditional and the tool reports the authoritative enable state.
|
|
10
10
|
|
|
11
11
|
## VCM Harness Scope
|
|
12
12
|
|
|
@@ -84,10 +84,15 @@ PM may lightly rewrite the user's words to:
|
|
|
84
84
|
|
|
85
85
|
### Gate Review Gates
|
|
86
86
|
|
|
87
|
-
- Gate Review
|
|
87
|
+
- Gate Review is artifact-gated and transition-gated. Request it only when the current formal handoff artifact exists and PM is about to advance across that delivery boundary.
|
|
88
|
+
- Within a confirmed delivery gate, the request is mandatory and unconditional: use the \`vcm-gate-review\` skill to run \`.ai/tools/request-gate-review --gate <gate>\` without judging whether Gate Review is enabled. The tool is the source of truth.
|
|
89
|
+
- Trigger points:
|
|
90
|
+
- \`architecture-plan\`: current \`.ai/vcm/handoffs/architecture-plan.md\` exists and PM is about to dispatch Coder.
|
|
91
|
+
- \`validation-adequacy\`: current \`.ai/vcm/handoffs/review-report.md\` exists and PM is about to start docs sync or final acceptance.
|
|
92
|
+
- \`final-diff\`: current final acceptance evidence exists and PM is about to prepare PR or close the task.
|
|
93
|
+
- Questions, clarifications, role consultations, explanations, status replies, and user-directed role Q&A do not trigger Gate Review.
|
|
88
94
|
- The tool's first output line decides the next step: \`disabled\`, \`not_required\`, or \`already_approved\` continue the normal VCM flow; \`started\` or \`running\` stop the turn and wait for the VCM callback; \`failed_to_start\` is a hard stop — report it to the user and do not silently proceed past the gate.
|
|
89
|
-
-
|
|
90
|
-
- On a callback, accept only \`approve\` or \`request_changes\`. On \`request_changes\`, route \`architecture-plan\`/\`final-diff\` reports to architect (Debug Mode or Replan assessment) and \`validation-adequacy\` reports to reviewer.
|
|
95
|
+
- On a callback, accept only \`approve\` or \`request_changes\`. On \`request_changes\`, route \`architecture-plan\`/\`final-diff\` reports to architect and \`validation-adequacy\` reports to reviewer.
|
|
91
96
|
- Do not ask Gate Reviewer to choose owners, fixes, Replan, or user-intervention needs.
|
|
92
97
|
- Record gate decision, report path, and any skip or override reason.
|
|
93
98
|
|