القائمة
Use after implement-feature to score the current implementation against the active feature's spec.md Criterios de Aceitacao, emitting a pass/fail list. Read-only — makes no code changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | evaluator |
| description | Use after implement-feature to score the current implementation against the active feature's spec.md Criterios de Aceitacao, emitting a pass/fail list. Read-only — makes no code changes. |
When: right after implement-feature finishes a task (or a batch of tasks), before deciding whether to loop back for fixes or move on. Re-run any time the implementation changes.
Template: none — this skill is purely evaluative, it does not fill or produce a template-based artifact.
Output: a pass/fail list reported inline to the user (one line per Critérios de Aceitação scenario) — no new file is mandated, no existing file is edited.
Steps:
.specify/state (fallback: newest dir under specs/).specs/<active-feature>/spec.md, focusing on Critérios de Aceitação (the Given/When/Then scenarios).tasks.md checkboxes alone.PASS or FAIL plus a short reason. Also flag any scenario that has no corresponding test at all.Next: fix-runner if any scenario fails or gates are red; otherwise hand control back to implement-and-evaluate to continue with the next task or proceed to code-review.
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.