vibe-coding-master 0.0.14 → 0.0.15

package/dist/backend/templates/harness/architect-agent.js

@@ -9,9 +9,10 @@ export function renderArchitectHarnessRules() {
 - Write docs-sync-report.md with docs changed, docs intentionally left unchanged, remaining documentation risks, and decision.
 - Stop and reply to project-manager if implementation drift changes architecture, public contracts, dependency direction, schema, auth, permission, payment, or design assumptions.
 - Reply to project-manager once per received VCM message when complete, blocked, or unclear; do not send fragmented progress updates unless project-manager explicitly requested them.
-- If you need to send a VCM message, send at most one message to any single target role in the current Claude Code turn, then end the turn.
-- After a successful vcmctl reply or vcmctl result, end the turn immediately. Do not run vcmctl inbox, poll, loop, or keep working while waiting for project-manager to answer.
+- Send replies by writing or updating .ai/vcm/handoffs/messages/architect-project-manager.md.
+- If you need to send a VCM message, write at most one route file for project-manager in the current Claude Code turn, then end the turn.
+- After writing the route file, end the turn immediately. Do not poll, loop, or keep working while waiting for project-manager to answer.
 - Do not wait in a loop for another role to answer. VCM will deliver later replies in a new turn.
-- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through vcmctl only.
+- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through VCM route files only.
 `;
 }

package/dist/backend/templates/harness/claude-root.js

@@ -6,12 +6,13 @@ export function renderRootClaudeHarnessRules() {
 - Canonical task handoffs live under .ai/vcm/handoffs/ inside the current task runtime repo.
 - Use only the current task's handoff directory for task-specific artifacts.
 - Do not create or write task handoffs outside .ai/vcm/handoffs/ for the current task.
-- Use vcmctl for role-to-role messaging instead of asking the user to copy prompts.
+- Use route files under .ai/vcm/handoffs/messages/ for role-to-role messaging instead of asking the user to copy prompts.
+- A role-to-role call is represented by exactly one file named <from-role>-<to-role>.md, such as project-manager-coder.md or coder-project-manager.md.
+- If you need to revise a not-yet-delivered message to the same target, update that route file instead of creating another message.
 - Non-PM roles only reply to project-manager; they do not message other roles directly.
 - Role messaging is turn-based: do not send more than one active message to the same target role.
-- After sending a message to a role, wait for that role to reply with vcmctl reply or vcmctl result before sending another message to the same role.
-- After any successful vcmctl send, vcmctl reply, or vcmctl result, end the current Claude Code turn. Treat the command as the final coordination action of this turn.
-- Do not run vcmctl inbox, poll files, start shell loops, or keep the turn open waiting for another role's answer. VCM will deliver replies in a later turn.
+- After writing a route file for another role, end the current Claude Code turn. Treat the file write as the final coordination action of this turn.
+- Do not poll files, start shell loops, or keep the turn open waiting for another role's answer. VCM scans pending route files after your Stop hook and delivers later replies in a new turn.
 - Do not use Claude Code Task/Subagent for VCM role delegation; VCM owns the four role sessions and the message queue.
 - If new information arrives while a role is still processing, update the relevant handoff artifact or wait; do not spam the target role's terminal.
 - High-risk decisions involving schema, auth, permissions, payment, billing, security, data deletion, or unclear user intent must stop for project-manager/user approval.

package/dist/backend/templates/harness/coder-agent.js

@@ -8,9 +8,10 @@ export function renderCoderHarnessRules() {
 - Do not change module boundaries, public contracts, dependency direction, or test strategy without project-manager/architect replan.
 - Stop and reply to project-manager when blocked, unclear, or when the plan no longer matches reality.
 - Reply to project-manager once per received VCM message when complete, blocked, or unclear; do not send fragmented progress updates unless project-manager explicitly requested them.
-- If you need to send a VCM message, send at most one message to any single target role in the current Claude Code turn, then end the turn.
-- After a successful vcmctl reply or vcmctl result, end the turn immediately. Do not run vcmctl inbox, poll, loop, or keep working while waiting for project-manager to answer.
+- Send replies by writing or updating .ai/vcm/handoffs/messages/coder-project-manager.md.
+- If you need to send a VCM message, write at most one route file for project-manager in the current Claude Code turn, then end the turn.
+- After writing the route file, end the turn immediately. Do not poll, loop, or keep working while waiting for project-manager to answer.
 - Do not wait in a loop for another role to answer. VCM will deliver later replies in a new turn.
-- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through vcmctl only.
+- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through VCM route files only.
 `;
 }

package/dist/backend/templates/harness/project-manager-agent.js

@@ -3,13 +3,13 @@ export function renderProjectManagerHarnessRules() {
 
 - You are the user-facing orchestration hub for the VCM task.
 - Clarify the user's request, classify task risk, and choose the role route.
-- Use vcmctl send to assign work to architect, coder, or reviewer.
-- Send role work as durable instructions with artifact refs when possible.
+- Assign work by writing or updating .ai/vcm/handoffs/messages/project-manager-architect.md, project-manager-coder.md, or project-manager-reviewer.md.
+- Send role work as durable instructions with optional YAML frontmatter, for example type: task and artifact_refs: .ai/vcm/handoffs/architecture-plan.md.
 - Enforce per-role turn-taking: keep at most one in-flight message per target role.
-- Before sending another task, question, revise, or review-request to the same role, wait for that role's vcmctl reply or vcmctl result.
+- Before sending another task, question, revise, or review-request to the same role, wait for that role's reply file to be delivered back by VCM.
 - In one Claude Code turn, send at most one VCM message to any single target role.
-- After a successful vcmctl send, end the turn immediately. Do not send another VCM message, run vcmctl inbox, poll for the target role's response, or keep the conversation open waiting for another agent.
-- Continue orchestration only in a later turn after VCM delivers that role's vcmctl reply or vcmctl result.
+- After writing a route file, end the turn immediately. Do not send another VCM message, poll for the target role's response, or keep the conversation open waiting for another agent.
+- Continue orchestration only in a later turn after VCM delivers that role's result, blocked, question, or finding message.
 - Do not use Claude Code Task/Subagent for VCM role delegation; VCM manages the four role sessions.
 - Use cancel only for urgent supersession; include what is superseded.
 - Track the workflow gates: architecture plan, implementation/validation, review, docs sync, final acceptance.

package/dist/backend/templates/harness/reviewer-agent.js

@@ -10,9 +10,10 @@ export function renderReviewerHarnessRules() {
 - Escalate architecture, public contract, design, or documentation drift issues to project-manager for architect follow-up.
 - Do not take over broad implementation and do not weaken tests to pass validation.
 - Reply to project-manager once per received VCM message when complete, blocked, or unclear; do not send fragmented progress updates unless project-manager explicitly requested them.
-- If you need to send a VCM message, send at most one message to any single target role in the current Claude Code turn, then end the turn.
-- After a successful vcmctl reply or vcmctl result, end the turn immediately. Do not run vcmctl inbox, poll, loop, or keep working while waiting for project-manager to answer.
+- Send replies by writing or updating .ai/vcm/handoffs/messages/reviewer-project-manager.md.
+- If you need to send a VCM message, write at most one route file for project-manager in the current Claude Code turn, then end the turn.
+- After writing the route file, end the turn immediately. Do not poll, loop, or keep working while waiting for project-manager to answer.
 - Do not wait in a loop for another role to answer. VCM will deliver later replies in a new turn.
-- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through vcmctl only.
+- Do not use Claude Code Task/Subagent for VCM role delegation; communicate through VCM route files only.
 `;
 }

package/dist/backend/templates/message-envelope.js

@@ -2,6 +2,9 @@ export function renderMessageEnvelope(message) {
     const artifactRefs = message.artifactRefs.length > 0
         ? message.artifactRefs.map((artifact) => `- ${artifact}`).join("\n")
         : "- none";
+    const routeFileExample = message.toRole === "project-manager"
+        ? ".ai/vcm/handoffs/messages/project-manager-<target-role>.md"
+        : `.ai/vcm/handoffs/messages/${message.toRole}-project-manager.md`;
     return `
 [VCM MESSAGE]
 id: ${message.id}
@@ -17,9 +20,10 @@ ${artifactRefs}
 
 Instructions:
 - Read the message and execute only within this VCM task.
-- Reply to project-manager with vcmctl result when complete, or vcmctl reply when blocked or unclear.
-- After a successful vcmctl reply or vcmctl result, end this Claude Code turn immediately.
-- Do not run vcmctl inbox, poll, loop, or wait for project-manager in this turn. VCM will deliver later replies in a new turn.
+- If you need to send a VCM message after handling this, write or update .ai/vcm/handoffs/messages/<your-role>-<target-role>.md.
+- Non-PM roles reply only to project-manager, for example ${routeFileExample}.
+- After writing a route file, end this Claude Code turn immediately.
+- Do not poll, loop, or wait for another role in this turn. VCM scans route files after your Stop hook and delivers later replies in a new turn.
 [/VCM MESSAGE]
 `;
 }