Menu
Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
Use when starting any conversation - establishes skill selection and the local task-doc workflow
| name | analyzing-test-effectiveness |
| description | Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements |
<skill_overview> High coverage is not the goal. Tests must catch real failures and justify their maintenance cost. </skill_overview>
<rigidity_level> MEDIUM FREEDOM - Follow the audit flow strictly, but adapt the exact categories and examples to the codebase. </rigidity_level>
<quick_reference>
<when_to_use>
<the_process>
Look for:
For every weak area, say what real bug it would or would not catch.
Create or update a task directory that captures:
Use sre-task-refinement to harden the improvement plan before implementation.
</the_process>
