メニュー
Deprecated TDD shim. Keep test-first discipline inside the active implementation workflow (folded into `plan`).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a regression-tests-first, smell-by-smell deslop/refactor workflow that preserves behavior and raises signal quality. Use when the user asks to "cleanup", "refactor", "deslop", or when follow-up code has duplicates, dead code, weak boundaries, or fallback-like slop.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says "analyze", "investigate", "why does", "what's causing", or needs grounded cross-file explanation before any changes are proposed.
Deprecated compatibility shim for Claude advisor requests. Use `ask` with the claude backend instead.
Deprecated compatibility shim for Gemini advisor requests. Use `ask` with the gemini backend instead.
Ask a locally installed external advisor CLI (Claude or Gemini) for focused questions, reviews, brainstorming, or second opinions, and capture a reusable artifact. Use when the user wants a Claude/Gemini second opinion, "ask claude", or "ask gemini".
Strict autonomous delivery loop that runs deep-interview, ralplan, ultragoal, code-review, and ultraqa in order with automatic re-planning when gates are not clean. Use on "autopilot", "autonomous", "build me", "create me", "make me", "full auto", "handle it all", or "I want a/an…".
| name | tdd |
| category | build |
| status | deprecated |
| description | Deprecated TDD shim. Keep test-first discipline inside the active implementation workflow (folded into `plan`). |
| agent_created | true |
| triggers | ["tdd","test driven development","test first"] |
Ported from oh-my-codex
tdd. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Hard-deprecated as a standalone skill. Do not invoke or route this skill.
Keep test-first discipline inside the active implementation workflow (the plan skill and normal implementation flow). The discipline is the value; here it is for reference:
The Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Write code before the test? Delete it and start over.
Red-Green-Refactor cycle:
Enforcement: code-before-test → stop and write the test; test-passes-first → fix it to fail; multiple features per cycle → one test, one feature; skipping refactor → go back and clean up.
For durable multi-goal execution that should keep this discipline, use ultragoal; for the implementation workflow itself, use plan.
