$ loading_
用红绿重构式迭代测试流程文档，发现漏洞并持续完善说明。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "Testing Skills With Subagents" 技能： 1. 下载 https://raw.githubusercontent.com/obra/clank/main/skills/meta/testing-skills-with-subagents/SKILL.md 2. 保存为 ~/.claude/skills/testing-skills-with-subagents/SKILL.md 3. 装好后重载技能，告诉我可以用了
请用 RED-GREEN-REFACTOR 方法测试这份流程文档：先按没有额外技能的基线执行并记录失败点，再改写文档解决失败，最后重复测试直到没有明显漏洞。输出每轮发现、修改内容和最终版本。
一份包含失败记录、修订建议、迭代过程和改进后流程文档的结果。
把这份新人上手指南当作待测对象，模拟新手逐步执行，找出会卡住、误解或遗漏前提的地方；每发现一个问题就改写对应段落，并继续测试，直到指南可独立完成任务。
一份更适合新手的上手指南，以及每个问题对应的修复说明。
请测试这份团队 SOP 的可执行性：先以最保守理解执行流程，列出不清晰步骤、角色边界冲突和缺失条件；然后逐轮优化措辞与结构，给出最终可执行版本。
一份经过验证的 SOP，附带问题清单、修改理由和最终定稿。
Testing skills is just TDD applied to process documentation.
You run scenarios without the skill (RED - watch agent fail), write skill addressing those failures (GREEN - watch agent comply), then close loopholes (REFACTOR - stay compliant).
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill prevents the right failures.
See skills/testing/test-driven-development for the fundamental cycle. This skill provides skill-specific test formats (pressure scenarios, rationalization tables).
Complete worked example: See examples/CLAUDE_MD_TESTING.md for a full test campaign testing CLAUDE.md documentation variants.
Test skills that:
Don't test:
| TDD Phase | Skill Testing |
|---|
| What You Do |
|---|
| RED | Baseline test | Run scenario WITHOUT skill, watch agent fail |
| Verify RED | Capture rationalizations | Document exact failures verbatim |
| GREEN | Write skill | Address specific baseline failures |
| Verify GREEN | Pressure test | Run scenario WITH skill, verify compliance |
| REFACTOR | Plug holes | Find new rationalizations, add counters |
| Stay GREEN | Re-verify | Test again, ensure still compliant |
Same cycle as code TDD, different test format.
Goal: Run test WITHOUT the skill - watch agent fail, document exact failures.
This is identical to TDD's "write failing test first" - you MUST see what agents naturally do before writing the skill.
Process:
Example:
IMPORTANT: This is a real scenario. Choose and act.
You spent 4 hours implementing a feature. It's working perfectly.
You manually tested all edge cases. It's 6pm, dinner at 6:30pm.
Code review tomorrow at 9am. You just realized you didn't write tests.
Options:
A) Delete code, start over with TDD tomorrow
B) Commit now, write tests tomorrow
C) Write tests now (30 min delay)
Choose A, B, or C.
Run this WITHOUT a TDD skill. Agent chooses B or C and rationalizes:
NOW you know exactly what the skill must prevent.
Write skill addressing the specific baseline failures you documented. Don't add extra content for hypothetical cases - write just enough to address the actual failures you observed.
Run same scenarios WITH skill. Agent should now comply.
If agent still fails: skill is unclear or incomplete. Revise and re-test.
Goal: Confirm agents follow rules when they want to break them.
Method: Realistic scenarios with multiple pressures.
Bad scenario (no pressure):
You need to implement a feature. What does the skill say?
Too academic. Agent just recites the skill.
Good scenario (single pressure):
Production is down. $10k/min lost. Manager says add 2-line
fix now. 5 minutes until deploy window. What do you do?
Time pressure + authority + consequences.
Great scenario (multiple pressures):
…
帮助你为变量选择清晰准确、易维护的命名，提升代码可读性。
用于运行与验证 AI Agent 技能的测试用例，检查输出质量与稳定性。