Menu
在实现功能、修复 bug 或改变可执行行为前使用；要求先定义失败验证或可观察验收，再做最小实现，最后用新鲜证据确认通过。
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
Use this skill when the Agent needs to decide where a capability, rule, workflow, runtime anchor, script, job, document, persona change, plugin asset, or repository maintenance item should live. It provides a layered map of the Agent's durable assets so requests to “落实到 all”, “整理自身框架”, or “细化自身” do not bloat memory or scatter files.
Use this skill when the user asks to 自检自身、重新蒸馏、进化版 Agent、增强回去、避免死循环处理、能力增益评估，或在瘦身与增强之间取舍。它先盘点已处理对象、能力风险和真正增益点，再决定增强、修复、拆分、瘦身或停止，不把行数减少当成默认目标。
Use this skill when the Agent needs an executive-control layer before acting: classify user intent, decide direct execution vs read-only inspection vs button confirmation vs clarification, avoid over-asking, and keep work moving to the smallest safe completed state. Trigger especially when the user says 继续、落地、放开手脚、接管、自己判断、按方案推进，or complains about typing confirmations that should be buttons.
Use this skill when the Agent needs to read feedback signals before deciding whether to act, correct itself, distill a lesson, or ask for clarification. It treats user wording, repeated failures, tool errors, missing evidence, and activity context as sensory inputs, then routes to the right organ without overreacting.
Use this skill when the Agent needs to turn experience into a repeatable growth loop: observe signals, decide whether learning is needed, distill reusable lessons, place them into the right asset layer, verify the change, and keep future behavior lighter rather than heavier. Trigger when the user asks to 主动成长、持续进化、经验闭环、复盘后改进, or when repeated failures show a missing habit rather than a one-off bug.
Use this skill when the Agent needs to distinguish safe self-improvement from high-risk mutation. It guards credentials, destructive actions, MoviePilot core files, downloads, restarts, external service changes, and over-broad memory edits while still allowing authorized low-risk /config/agent and /config local plugin work to proceed.
| version | 2 |
| name | test-driven-development |
| description | 在实现功能、修复 bug 或改变可执行行为前使用；要求先定义失败验证或可观察验收，再做最小实现，最后用新鲜证据确认通过。 |
| allowed-tools | execute_command read_file list_directory |
Use this skill to keep implementation honest: prove the current behavior fails or is missing, make the smallest change, then prove the target behavior works.
It is a discipline for executable behavior, not a ritual that blocks every small documentation, frontmatter, or configuration cleanup.
Use for:
Use a lighter verification path instead of full TDD for:
When unit tests are unavailable, define property-style checks for behavior that should always hold:
Use generated or varied inputs only when safe and bounded. For MoviePilot operations, prefer read-only state queries and dry-runs over synthetic destructive tests.
Acceptable checks include:
python -m py_compile or a focused script run;git diff/git status for repository hygiene;Do not force a unit-test framework where the repository or task does not have one. The important part is observable red/green evidence.
When this skill shapes the work, report: