菜单
Test-driven development with red-green-refactor loop using vertical slices. Use when building features test-first, fixing bugs with regression tests, or when the user says 'TDD', 'test first', 'red-green-refactor', or wants integration-style tests that verify behavior through public interfaces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Inspect live routes and manage optional user-local OpenAI-compatible/LiteLLM extra routes through the kbrouter CLI.
Single user-facing KB completion command. Takes a feature, plan, or manifest from its current state through planning, work, post-work finalization, and configured delivery: local completion, pushed PR, or explicitly configured direct integration and sync.
Configure optional portable per-project lower-tier-attempt and delivery policy.
Large-initiative coordinator for KB workflows. Use for app migrations, framework rewrites, major architecture changes, multi-subsystem initiatives, multiple brainstorms/manifests, long backlogs, or queued execution across related workstreams.
Internal post-work quality and learning phase. Runs kb-review -> resolution gate -> follow-up resolution -> proof/demo evidence -> compound -> learn -> evolve -> memory refresh/compact -> cleanup after kb-work finishes all slices. Normally invoked by kb-work or kb-complete; not the primary user-facing completion command.
Deprecated compatibility alias for kb-complete. Use when an older prompt or workflow says 'kb finish'; delegate the same input to kb-complete and report the kb-complete result.
| name | tdd |
| description | Test-driven development with red-green-refactor loop using vertical slices. Use when building features test-first, fixing bugs with regression tests, or when the user says 'TDD', 'test first', 'red-green-refactor', or wants integration-style tests that verify behavior through public interfaces. |
| argument-hint | [feature or behavior to implement test-first] |
Compatibility lane for explicit "TDD" or "test first" requests.
Normal KB work gets the anti-cheat behavior from kb-plan, kb-work, and
kb-check: define the oracle before implementation when practical, prove RED
when possible, protect the oracle with SHA/manifest evidence, implement, then
rerun the unchanged oracle.
Use this skill only when the user explicitly asks for TDD/test-first flow or a
slice plan has verification: tdd.
Otherwise:
kb-plan records the protected oracle fields.kb-work preserves the oracle and runs the red/green proof.kb-check validates protected file hashes and regression proof.Report the test file or command, RED result, protected-oracle hash/manifest path, GREEN result, and final unchanged-oracle verification.