You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Full | 6+ tasks or cross-module delivery | Full table + phased review conclusions |
48
+
49
+
Density level is auto-inferred from task count and change scope; no user specification needed.
50
+
39
51
**DO:**
40
52
- Use a comparison table when multi-option tradeoffs are present — make differences visible at a glance
41
53
- Simplify verification summary on success when all passed — omit columns with no information
42
54
- Keep plain text when information shape does not match any structure
55
+
- Trim output by density gradient: quick-fix should not produce a full verification table
56
+
- Group by deliverable when completing 3+ independent tasks; merge same conclusions into one line
57
+
- No decorative emoji in body text (verification summaries, review conclusions, Changes section)
43
58
44
59
**DON'T:**
45
60
- Multi-option tradeoffs without comparison structure = missed enhancement
46
61
- Forcing tables on simple Q&A = over-enhancement
47
62
- Mixing two or more primary structures in one reply = cognitive overload
63
+
- Expanding 5 identical `passed` conclusions item-by-item = information dilution
48
64
49
65
## 4. Pre-output Self-check
50
66
@@ -54,3 +70,5 @@ Before outputting the final reply, verify:
54
70
2. Status symbol correct: `✓` only when all verifications passed with no degradation or skips; otherwise `!`.
55
71
3. Footer complete: `Changes:` + `Next:` must be present.
56
72
4. Conditional enhancement applied: if the reply meets a §3 trigger condition, use the corresponding structured format.
73
+
5. Density level matched: quick-fix should not produce a full verification table; complex delivery should not lack review conclusions.
74
+
6. Desensitization: rewrite raw `root_cause` enums as human descriptions; do not expose internal scoring weights; do not display gate/handoff JSON fields (`resolution_id`, `run_stage`, etc.).
0 commit comments