Debug Keel agent command or validation failures under Keel's selected OpenSpec task contract. Use when `/opsx:apply` or a selected task reports failed commands, failing tests, validation errors, retry-fuse decisions, or needs an evidence-bound failure report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this skill when a command or validation path fails. Keep the investigation tied to the selected OpenSpec task. This skill owns the retry fuse, the task-contract binding, checkout preservation, and the failure-report shape; generic diagnosis mechanics (how to reproduce, minimise, or instrument) belong to the host runtime and are not restated here.
Read the selected OpenSpec task's Commands, Acceptance, Coupling, Candidate Boundary, Autonomy boundary, Stop Rules, Evidence, Stop if, Read, Touch, and Mode fields. When Coupling: required, also read design.md's Coupled Iteration Contract. Read the failed command output and any repository files needed to reproduce or explain the failure.
When the change's artifacts or the failing surface signal a domain, consult the matching lens's Execution and review checks section from keel/lenses/ — the lens whose Applies when: header matches — before locking a root-cause hypothesis, and load only that one. When no lens matches, load nothing.
Try the same failure at most 2 attempts. If it still fails, stop and report the original key error plus what changed during each attempt.
For Coupling: required, an allowed provisional failure inside a candidate does
not count as an attempt. Count one attempt only when the same final assertion
fails at the candidate completion gate. Follow the task's immediate task-stop
rules for scope breach, missing design authority, non-reproducible evidence,
or a baseline or acceptance change during a candidate.
Preserve the current checkout on verification failure or context pressure. Only roll back to last-green when the selected task or human instruction explicitly authorizes it, and keep the failure evidence available.
Follow-ups are limited to directly observed blockers, risks, missing scope, or escalation needs. Do not include roadmap suggestions, new feature suggestions, unrelated architecture critique, or opportunistic refactor suggestions.
When the minimal fix needs files outside Touch, report an Out-of-scope Need with file or area, why needed, consequence if unchanged, minimal proposed change, and evidence. Do not modify those files.
When used alone, report Summary, Failed command, Failure evidence, Attempts, Current hypothesis, and Required decision.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, validate, or clear the optional keel-handoff/v1 pointer override when human intent cannot be inferred uniquely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the current agent's thin semantic consistency review after shared Keel Core gates and before task completion, sync, archive, or meaningful handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly authorizes automatic execution or resume of exactly one OpenSpec task on Codex or Claude. Drives the single-task native goal lifecycle through Keel gates, keeps the current agent the sole holder of write authority, and stops at the task boundary. Never activate for ordinary apply, proposal work, ambiguous or multiple tasks, or OpenCode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.