Menu
Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result
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 | fixing-bugs |
| description | Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result |
<codex_compat> This skill was ported from Claude Code. In Codex:
SKILL.md from disk.spawn_agent (dispatch in parallel when needed).<skill_overview> Bug work is still planned work. Capture the reproduction, find the root cause, write the failing test, then fix and verify. </skill_overview>
<rigidity_level> LOW FREEDOM - Follow the workflow exactly: reproduce, document, debug, write the failing test, implement the smallest fix, verify, then update the task docs. </rigidity_level>
<quick_reference>
| Step | Action |
|---|---|
| 1 | Create or resume a task directory for the bug |
| 2 | Record reproduction in plan.md or context.md |
| 3 | Use debugging tools to find the root cause |
| 4 | Write a failing regression test |
| 5 | Implement the smallest fix |
| 6 | Verify and update tasks.md / context.md |
| </quick_reference> |
<when_to_use>
<the_process>
Use a dedicated task directory or a clearly scoped bug slice in the current active directory.
Capture:
Use debugging-with-tools and root-cause-tracing as needed.
Do not patch symptoms first.
Reproduce the bug in an automated test before the fix.
Fix the root cause, not the visible symptom.
Run the regression test and any broader checks. Update:
context.md with root cause and fix notestasks.md with the completed bug slice
</the_process>