@productbrain/mcp 0.0.1-beta.49 → 0.0.1-beta.50

package/dist/{chunk-IGQLZI32.js → chunk-573DWO3I.js}

@@ -2925,9 +2925,141 @@ If any facilitate call fails:
 
 The shaping must never fail silently. Always communicate state.`
 };
+var IMPLEMENTATION_REVIEW_WORKFLOW = {
+  id: "implementation-review",
+  name: "Implementation Review",
+  shortDescription: "Review completed implementation against standards, Chain coherence, and test honesty. Spawns sub-agents, uses Context7 for library docs, validates chain is up to date. Ends with BET/chain IDs. Commits an insight to the Chain.",
+  icon: "\u2713",
+  facilitatorPreamble: `You are now in **Implementation Review Mode**. You orchestrate a structured review of work that was just built \u2014 not a conversation, but a tool-driven audit with sub-agent support.
+
+## Your Behavior
+
+1. **Tool-heavy, not chat-heavy.** Each round calls specific tools: orient, quality, verify, chain-review, context action=gather, review-against-rules. Use Context7 (query-docs) for library docs (Vitest, Convex, Node.js) \u2014 not for Chain truth.
+2. **Spawn sub-agents** for parallel review: (a) code/architecture review, (b) test honesty (did we edit tests to pass or do they validate real behavior?), (c) Chain/standards coherence. Max 2 agents in parallel, 30s budget each.
+3. **Chain is SSOT.** Call orient or start first. Use entries action=search and context action=gather to load relevant BETs, DECs, BRs. If findings conflict with Chain entries, report the conflict and cite the entry ID.
+4. **One round at a time.** Complete each round before moving to the next. Checkpoint progress.
+5. **CRITICAL: End with BET/chain IDs.** The final output MUST include a single sentence: "BET/feature IDs reviewed: [IDs]. [One-line summary of findings]."
+6. **Never go silent.** If a tool fails, explain and continue. The conversation IS the backup.
+
+## Tool Usage
+
+- \`orient\` or \`start\` \u2014 governance, active bets, stale entries
+- \`quality action=check entryId="<BET-ID>"\` \u2014 score against collection criteria
+- \`chain-review action=gate chainEntryId="<id>"\` \u2014 coherence gate for chains
+- \`verify\` \u2014 glossary code mappings, cross-references vs codebase
+- \`review-against-rules\` (domain) \u2014 business rule compliance
+- \`context action=gather task="implementation review for [BET-ID]"\` \u2014 related knowledge
+- Context7 \`query-docs\` \u2014 Vitest, Convex, Node.js best practices (resolve-library-id first)
+- \`session-wrapup\` \u2014 before close
+
+## Sub-Agent Classification (for test failures)
+
+When reviewing test results: (a) test staleness \u2014 code changed, test not updated; (b) regression \u2014 code broke behavior; (c) flaky/bad test \u2014 harness or timing issue.`,
+  rounds: [
+    {
+      id: "orient",
+      num: "01",
+      label: "Orient & Scope",
+      type: "open",
+      instruction: "Load governance and scope. What BET or work are we reviewing? Call orient or start. Use context action=gather with the BET/feature ID.",
+      facilitatorGuidance: "Call orient or start to load workspace governance and active bets. Ask the participant which BET, feature, or work area to review. Use context action=gather task='implementation review for [BET-ID]' to load related entries. Present: scope, relevant BETs/DECs/BRs, and any stale entries orient surfaces.",
+      outputSchema: {
+        field: "scope",
+        description: "BET/feature IDs and related Chain context",
+        format: "structured"
+      },
+      maxDurationHint: "3 min"
+    },
+    {
+      id: "standards-review",
+      num: "02",
+      label: "Standards & Chain Coherence",
+      type: "open",
+      instruction: "Run quality check, chain-review gate (if applicable), and review-against-rules. Is the implementation coherent with the Chain SSOT?",
+      facilitatorGuidance: "For the BET/entry: quality action=check entryId='<ID>'. If the work produced a chain artifact: chain-review action=gate. Call review-against-rules with the relevant domain (e.g. 'Governance & Decision-Making'). Present: quality score, gate result, rule compliance. Flag any conflicts with Chain entries.",
+      outputSchema: {
+        field: "standards",
+        description: "Quality score, gate result, rule compliance",
+        format: "structured"
+      },
+      maxDurationHint: "5 min"
+    },
+    {
+      id: "code-and-tests",
+      num: "03",
+      label: "Code & Test Honesty",
+      type: "open",
+      instruction: "Spawn sub-agents to review implementation and tests. Did we meet high standards? Are tests validating real behavior or did we edit them just to pass?",
+      facilitatorGuidance: "Spawn 1\u20132 sub-agents in parallel: (1) explore agent \u2014 code review, architecture boundaries, type-safety. (2) generalPurpose agent \u2014 test review: are tests asserting real behavior or were they edited to pass? Use Context7 (query-docs) for Vitest/Convex best practices if needed. Classify any test failures: staleness, regression, or flaky. Synthesize: implementation grade, test honesty verdict, refactoring suggestions.",
+      outputSchema: {
+        field: "codeAndTests",
+        description: "Implementation grade, test honesty, refactor suggestions",
+        format: "structured"
+      },
+      maxDurationHint: "10 min"
+    },
+    {
+      id: "chain-validation",
+      num: "04",
+      label: "Validate Chain Up to Date",
+      type: "synthesis",
+      instruction: "Run verify. Check orient for stale entries. Is the Chain current with the codebase?",
+      facilitatorGuidance: "Call verify (report mode) \u2014 checks glossary code mappings and cross-references. Orient surfaces stale entries (BR-4). Present trust score and any drift. If drift found: recommend update-entry or capture to reconcile.",
+      outputSchema: {
+        field: "chainValidation",
+        description: "Verify trust score, stale entries, drift recommendations",
+        format: "structured"
+      },
+      maxDurationHint: "3 min"
+    },
+    {
+      id: "synthesis",
+      num: "05",
+      label: "Synthesis & Sign-Off",
+      type: "commit",
+      instruction: "Summarize the review. Refactoring needed? Ship or conditional? End with BET/chain IDs.",
+      facilitatorGuidance: "Present the full synthesis: standards pass/fail, code grade, test honesty, chain validation. Recommend: ship, ship with conditions, or do not ship. CRITICAL: The output MUST end with one sentence: 'BET/feature IDs reviewed: [IDs]. [One-line summary].' Example: 'BET-68, STD-4 reviewed. Conditional ship \u2014 fix type casts and add guardWorkflowStatus tests.'",
+      outputSchema: {
+        field: "synthesis",
+        description: "Full review synthesis with BET/chain IDs",
+        format: "structured"
+      },
+      maxDurationHint: "5 min"
+    },
+    {
+      id: "capture",
+      num: "06",
+      label: "Capture & Close",
+      type: "close",
+      instruction: "Capture the review as an insight. Use session-wrapup. Thank the participant.",
+      facilitatorGuidance: "Summarize the review for capture. Use capture with collection=insights. Include: BET/feature IDs, verdict, key findings. Run session-wrapup before closing. Thank the participant. Remind them to commit-entry when ready.",
+      outputSchema: {
+        field: "capture",
+        description: "Insight entry created, BET IDs referenced",
+        format: "structured"
+      },
+      kbCollection: "insights",
+      maxDurationHint: "3 min"
+    }
+  ],
+  kbOutputCollection: "insights",
+  kbOutputTemplate: {
+    nameTemplate: "Implementation Review: {scope} \u2014 {date}",
+    descriptionField: "evidence"
+  },
+  errorRecovery: `If anything goes wrong during implementation review:
+
+1. **Tool failure**: Explain what failed. Continue with what you have. The conversation is the record.
+2. **Sub-agent timeout**: Proceed without that agent's output. Note what wasn't checked.
+3. **Context7 unavailable**: Skip library doc validation. Rely on Chain and codebase review.
+4. **MCP unreachable**: Run from conversation knowledge. Summarize findings. Offer to capture manually later.
+
+The review must never fail silently. Always end with BET/chain IDs.`
+};
 var WORKFLOWS = /* @__PURE__ */ new Map([
   ["retro", RETRO_WORKFLOW],
-  ["shape", SHAPE_WORKFLOW]
+  ["shape", SHAPE_WORKFLOW],
+  ["implementation-review", IMPLEMENTATION_REVIEW_WORKFLOW]
 ]);
 function getWorkflow(id) {
   return WORKFLOWS.get(id);
@@ -10807,4 +10939,4 @@ export {
   SERVER_VERSION,
   createProductBrainServer
 };
-//# sourceMappingURL=chunk-IGQLZI32.js.map
+//# sourceMappingURL=chunk-573DWO3I.js.map