Menu
Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation
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 | sre-task-refinement |
| description | Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation |
<skill_overview> Refinement is where vague plans become safe to execute. Tighten the spec and the next work slices before coding. </skill_overview>
<rigidity_level> HIGH FREEDOM - Apply deep scrutiny to the current spec and task docs, but keep the output concrete and immediately actionable. </rigidity_level>
<quick_reference>
plan.md, context.md, and tasks.md<when_to_use>
<the_process>
Look for:
Update the relevant task docs with:
No placeholders, no “figure it out later,” no giant tasks hiding multiple risks. </the_process>