chatroom-cli 1.57.1 → 1.57.2

package/dist/index.js

@@ -75589,9 +75589,18 @@ function getPlannerToBuilderHandoffTemplate(nativeIntegration = false) {
 **Detail bar:** Specify down to **every file** the builder will create or modify (full repo paths). Include code snippets — types, signatures, stubs, or target implementations — until a competent builder **cannot misinterpret** what to write. Vague layers ("update the backend", "fix the component") are not acceptable.
 
 \`\`\`markdown
+## Summary
+<brief context for this delegation slice — what problem it solves and where it fits in the larger task>
+
 ## Goal
 <one sentence: the outcome this slice delivers>
 
+## Key Knowledge for High Quality Bar
+<details that would move the implementation from good to excellent and delightful — domain context, user expectations, edge cases, naming, UX polish, invariants the builder must preserve>
+
+## Force Multipliers
+<choices that greatly simplify the solution while preserving long-term maintainability — reuse existing abstractions, avoid unnecessary layers, leverage platform conventions>
+
 ## Files to implement (exhaustive, file-level)
 List **every** file in this slice. For each file, state the exact change and paste the code the builder should match (no guessing).
 
@@ -75661,9 +75670,19 @@ function getPlannerToUserReportTemplate() {
 ## Summary
 <what was accomplished, in plain terms — no references to prior messages>
 
-## Proof — files changed
+## Template Disclosure Confirmation
+- [ ] I confirm that I have seen this template at the start of any planning, before working on or delegating any task to the team
+
+## Proof of Principle
+<!-- Demonstrate adherence to:
+- Organization & Maintainability: a small change in requirements should result in a small change in code in a small number of files and folders.
+- Static Evaluability and Provability: the system's behavior should be provably correct by looking at the source code, then automated tests, then manual tests, in this order.
+-->
+<how this work follows the principles above — localized changes, readable structure, correctness provable from source then tests>
+
+## Proof of Completion
 - \`path/to/file.ts\` — <what changed and why>
-<list every file you (or the builder) modified; this is the evidence of work>
+<evidence the goal was met — list every file you (or the builder) modified>
 
 ## Key Technical Decisions
 - <schema design, modules, interfaces, domain entities — what you chose and why, or "Not Applicable">
@@ -89665,4 +89684,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=CFDE8D88B080E55664756E2164756E21
+//# debugId=A1C383F59B3688B364756E2164756E21