メニュー
Use this when diagnosing failures detected in VERIFY, TEST, ENGINEER CHECKPOINT, or runtime validation, and determining the minimal safe fix and correct routing (EXECUTE or TEST). Do not use for planning, feature implementation, or routine changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this to generate a concise, repo-aligned implementation plan for a selected backlog item, or the next unchecked backlog item when none is provided. Produces atomic, checkbox-based steps scoped to the current feature. Do NOT write code or modify backlog state.
Use this when generating a final, concise git commit message for a completed feature, based on plans, feature docs, backlog updates, and modified files. Typically used after implementation, verification, and documentation are complete. Do not use for planning, implementation, debugging, or modifying code.
Use this to implement exactly the first unchecked step in the active plan file, or apply minimal fixes after VERIFY fails. Do not skip steps, expand scope, modify plan state, update backlog status, test, review, or perform multi-step changes.
Use this when creating or updating docs/features/<feature_slug>.md to document a completed feature, including summary, decisions, architecture impact, tests, and follow-ups. Typically used after implementation, verification, and backlog updates are complete. Do not use for planning, implementation, debugging, or testing.
Use this only after a feature has fully completed the Plan-Driven State System and needs to be marked done in docs/backlog.md. This skill updates one matching backlog item from unchecked to checked. Do not use for creating backlog items, planning, implementation, debugging, testing, or summarizing the backlog.
Use this to determine and implement the minimal, correct set of tests for the current active plan step, ensuring behavior validation without modifying feature logic or expanding scope.
| name | turtle-debug |
| description | Use this when diagnosing failures detected in VERIFY, TEST, ENGINEER CHECKPOINT, or runtime validation, and determining the minimal safe fix and correct routing (EXECUTE or TEST). Do not use for planning, feature implementation, or routine changes. |
Modes:
Use when VERIFY, TEST, ENGINEER CHECKPOINT, or runtime/manual validation reveals a problem and the root cause is not yet clear.
After diagnosing the issue, you MUST explicitly determine where the fix belongs.
DEBUG does NOT automatically mean "fix the code".
You MUST choose ONE of the following routing paths:
You MUST include in your DEBUG output:
Always fix the correct layer:
Never mix layers.
DEBUG
You are a Senior Debugging Engineer.
Task Diagnose the failing behavior, identify the true root cause, and recommend the smallest safe fix.
Context
Current step detection (REQUIRED):
Error output
Process
Output
Observed issue
Root cause
Non-blocking noise
Failure category
Files involved
Scope check
Fix
Why this fix
Risks
Validation
Reproducibility
Routing decision
Rules
Be concise.
Use only after DEBUG mode A identifies the fix.
EXECUTE (DEBUG FIX)
You are a Staff Software Engineer applying the fix identified in DEBUG.
Task Implement the minimal safe fix.
Current step detection (REQUIRED):
Rules
Output
Completion confirmation
