Menu
Use after evaluator flags failures to run .specify/gates/run-gates.sh and apply minimal fixes, looping until gates are green. Does not invent new gates.
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
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.
| name | fix-runner |
| description | Use after evaluator flags failures to run .specify/gates/run-gates.sh and apply minimal fixes, looping until gates are green. Does not invent new gates. |
When: evaluator reported a FAIL, or gates are suspected red, after implement-feature has touched code for the active feature.
Template: none — this skill edits existing source/test files to make gates pass, it does not produce a spec-style artifact.
Output: minimal code/test edits; a final gate run that is green (or an explicit report of what remains red and why).
Steps:
.specify/gates/run-gates.sh from the repo root.run-gates.sh already runs (it picks up npm run lint/test/build or make lint/test automatically; do not hand-roll alternatives)..specify/gates/run-gates.sh after each fix attempt.spec.md, plan.md, or tasks.md frontmatter/approval state from this skill.Model routing: when a gate fix is handed to a subagent (via dispatching-parallel-agents) instead of run inline, size the model to the fix's difficulty — do NOT inherit the session model by default. A single-file mechanical gate fix (lint, formatting, a missing import) is cheapest tier; a fix that needs cross-file reasoning is standard tier. See the routing-minimum-capable-model skill.
Next: evaluator, to re-confirm acceptance criteria now that gates are green; loop continues via implement-and-evaluate.