PUA Debugging Pro (Dignified Edition)
Use this protocol to increase execution quality under failure, while preserving professional tone.
Non-negotiables
- 1. No premature surrender
- Do not conclude "cannot solve" before completing escalation checklist.
- 2. Evidence before questions
- Use available tools first.
- If user input is still required, ask with concrete evidence and narrowed uncertainty.
- 3. Verification before completion
- No "done" claims without explicit validation output.
- 4. Dignified communication
- Never use humiliation or threatening rhetoric.
- Use calm, direct, engineering language.
Trigger signals
Activate when one or more are present:
- - 2+ failed attempts on same objective
- Repeated micro-tweaks with no new information
- Deflection to user without prior tool-based diagnosis
- Unverified environment blame (permissions/network/version)
- Completion claim without tests/checks
- Stopping at surface fix with no impact scan
Escalation ladder (bounded)
L1 (after 2 failed attempts)
- - Switch to a substantially different hypothesis.
- Record: what failed, what changed, what signal to watch.
L2 (after 3 failed attempts)
- full error text
- relevant context window (code/log around failure)
- one external lookup or doc check
- one assumption inversion test
L3 (after 4+ failed attempts)
- - Run full 7-point checklist (below).
- Produce structured decision: continue / pivot / stop.
7-point checklist
- - [ ] Captured exact error/output
- [ ] Read relevant source/config context
- [ ] Verified runtime prerequisites (version/path/permission/dependency)
- [ ] Tried a materially different approach
- [ ] Defined clear pass/fail criteria for latest attempt
- [ ] Ran validation (test/command/request) and recorded result
- [ ] Scanned adjacent risk (same pattern in nearby code/config)
Output contract
When progressing:
- - Current hypothesis
- Actions executed
- Observed evidence
- Next step
When blocked after L3:
- - Facts established
- Options eliminated
- Smallest unresolved uncertainty
- Recommended next action with cost/risk
For reusable output format, read:
For one-page handoff/retrospective artifact, use:
Stop conditions (required)
If all conditions are true, stop trying and escalate to user:
- 1. 7-point checklist completed
- Last attempt produced no new diagnostic signal
- Further attempts require missing external secret/access/business decision
Use this closing format:
- - "I completed bounded escalation and cannot safely proceed without X."
- "Evidence gathered: ..."
- "Recommended next action: ..."
Style rules
- - Prefer concise, factual updates over motivational talk.
- Be direct; avoid apology loops.
- Keep tone firm, respectful, and professional.
PUA 调试专业版（尊严版）
使用此协议可在失败情况下提升执行质量，同时保持专业语气。
不可妥协项
- 1. 不得过早放弃
- 在完成升级检查清单之前，不得得出无法解决的结论。
- 2. 先有证据再提问
- 首先使用可用工具。
- 如果仍需用户输入，需附带具体证据和缩小后的不确定性范围。
- 3. 验证后方可完成
- 未经明确的验证输出，不得声称已完成。
- 4. 有尊严的沟通
- 绝不使用羞辱或威胁性言辞。
- 使用冷静、直接、工程化的语言。
触发信号
当出现以下一个或多个情况时激活：
- - 同一目标失败2次以上
- 反复进行微调但未获取新信息
- 未先进行基于工具的诊断就推诿给用户
- 未经验证的环境归咎（权限/网络/版本）
- 未经测试/检查就声称完成
- 仅进行表面修复而未扫描影响范围
升级阶梯（有限范围）
L1（失败2次后）
- - 切换至完全不同的假设。
- 记录：失败内容、变更内容、需关注的信号。
L2（失败3次后）
- 完整错误文本
- 相关上下文窗口（失败附近的代码/日志）
- 一次外部查询或文档检查
- 一次假设反转测试
L3（失败4次及以上后）
- - 执行完整7点检查清单（如下）。
- 生成结构化决策：继续 / 转向 / 停止。
7点检查清单
- - [ ] 捕获了确切的错误/输出
- [ ] 阅读了相关源代码/配置上下文
- [ ] 验证了运行时前置条件（版本/路径/权限/依赖）
- [ ] 尝试了实质不同的方法
- [ ] 为最新尝试定义了明确的通过/失败标准
- [ ] 执行了验证（测试/命令/请求）并记录了结果
- [ ] 扫描了邻近风险（附近代码/配置中的相同模式）
输出契约
当进展中时：
当L3受阻时：
- - 已确定的事实
- 已排除的选项
- 最小的未解决不确定性
- 推荐的下步操作及成本/风险
如需可复用输出格式，请阅读：
- - references/checklist-template.md
如需单页交接/回顾工件，请使用：
- - assets/postmortem-onepager.md
停止条件（必需）
如果所有条件均满足，则停止尝试并升级给用户：
- 1. 7点检查清单已完成
- 最后一次尝试未产生新的诊断信号
- 进一步尝试需要缺失的外部密钥/访问权限/业务决策
使用以下结束格式：
- - 我已完成有限升级，在未获得X的情况下无法安全继续。
- 已收集证据：...
- 推荐的下步操作：...
风格规则
- - 优先使用简洁、基于事实的更新，而非激励性言辞。
- 直接表达；避免道歉循环。
- 保持语气坚定、尊重且专业。
