菜单
TDD workflow discipline — red→green→refactor cycle for any new feature, bugfix, or behavior change. Use when implementing any feature or fixing any bug before writing production code. Proactively apply when user says "add feature", "implement", "fix bug", or "build X".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | test-driven-development |
| description | TDD workflow discipline — red→green→refactor cycle for any new feature, bugfix, or behavior change. Use when implementing any feature or fixing any bug before writing production code. Proactively apply when user says "add feature", "implement", "fix bug", or "build X". |
On-demand loading: Read this skill only when the task clearly matches the description above. Do not load for unrelated work.
Write the test first. Watch it fail. Write minimal code to pass. Repeat.
Core law: No production code without a failing test first. No exceptions without explicit user permission.
Exceptions (ask user first): throwaway prototypes, generated/config files, pure UI styling.
Full cycle detail, bug-fix pattern, red flags, checklist, and rationalizations: references/red-green-refactor.md
testing-strategy skill (test design patterns and what to test)debugging skill (when a failing test reveals a non-obvious bug)self-validate (final checklist before declaring done)ship-feature as the implementation discipline within it| File | Contents |
|---|---|
references/red-green-refactor.md | Complete RED/GREEN/REFACTOR steps, bug-fix pattern, red flags, completion checklist, rationalizations |
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to the knowledge-synthesizer subagent. Use when asked to mine prior chats, maintain AGENTS.md, update learned preferences, or run the continual-learning loop.
Security-focused review of code diffs and PRs with surface classification and Semgrep on changed files. Use when reviewing pull requests, branch diffs, or validating security regressions before merge.
Live Notion session log (L4b) — create, incremental updates during work, finalize on CLOSE. Works on any Cursor project workspace.
Bootstrap a new project with Cursor-ready configuration: AGENTS.md, per-project .cursor/rules/project-conventions.mdc, and optional memory_bank/ scaffold. Use at project initialization, when starting a new repo, or when the user says "set up Cursor for this project" / "bootstrap this project" / "init project config".
Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation.
Validates phase outputs before advancing the SDLC. Defines expected artifacts per phase (intake, scout, plan, critic, build, test, review, document, close) and produces a clear PASS / CONDITIONAL / BLOCK verdict with gaps. Use at orchestrator or command phase boundaries, before expensive work, or when the user asks to verify a gate or "are we ready to proceed".