Trellis Implement TDD Zh
在 Trellis 子任务进入实现阶段时,用严格 TDD(红→绿→重构)逐条把验收标准落成代码。用于 Codex / Claude Code 等在 trellis-zero-to-mvp-zh 或 trellis-mvp-to-delivery-zh 生成主子任务后,按依赖顺序实现某个子任务,尤其当执行模型是 qwen3.6 35b 这类小参数本地模型时——把"理解并实现需求"转成"让这条失败测试变绿"的机械循环,每步都有客观信号。
Install
npx skills add coldwateryi/trellis-skills --skill trellis-implement-tdd-zhgit clone --depth 1 https://github.com/coldwateryi/trellis-skills.git /tmp/trellis-skills
mkdir -p ~/.claude/skills
cp -r /tmp/trellis-skills/trellis-implement-tdd-zh ~/.claude/skills/trellis-implement-tdd-zhPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Trellis TDD 落地(红绿重构) ## 概览 把一个已规划好的 Trellis 子任务,按其 `prd.md` 的验收标准(AC)逐条用 TDD 实现:先写失败测试看到红,再写最小代码看到绿,跑自检确认没弄坏别的,执行最小实现收敛,记录进度,进入下一条 AC。 本技能由**编排会话(主会话,通常强模型)调用**,去驱动**实现执行体(可为 qwen3.6 35b 小模型)**。流程由本技能"夹着走",执行体只做有客观信号的机械步骤,不需要自己判断"做完没有"——**测试变绿就是做完**。 输入:一个 `status` 为进行中、依赖已满足的子任务目录(含 `prd.md`,可能含 `design.md`、`implement.md`、`implement.jsonl`、`check.jsonl`)。产出:通过测试的代码改动 + 回写到 `<task-dir>/tdd-progress.md` 的进度,**不执行 git commit**(Trellis 实现执行体禁止 commit/push/merge)。 ## 约束 - **不要在没有失败测试之前写实现代码**。每条 AC 的第一步永远是写一个会失败的测试。 - **一次只处理一条 AC**。当前 AC 未绿,不开始下一条。 - **不要判断"需求是什么"**。需求已由 `prd.md` 的验收标准、决策表、契约定死;执行体只负责让对应测试变绿。 - **落点已定死**。新代码放哪由 `prd.md` 文件清单 + `design.md` 的编排-计算分层决定;不要自行决定放哪个文件。 - **不要改文件清单 / 禁止事项之外的文件**。需要动别的文件时,停下来报告,不要自行扩散。 - **不执行 `git commit` / `git push` / `git merge`**。完成一条 AC 后只做暂存/记录。 - **红绿信号是唯一完成判据**。测试没看到红,说明测试没写对,停下来修测试,不要写实现去"凑绿"。 - **绿灯后必须收敛复杂度**。测试全绿不等于可以保留无用抽象、重复实现、新依赖或未来扩展点;按 `references/minimal-implementation-pass.md` 删除不必要复杂度。 - **不要为了最小化削掉安全和验证**。输入校验、错误处理、安全、可访问性、已声明边界和回归保护不能被简化掉。 - 测试该绿却仍红、或自检命令失败时,**改用 `trellis-debug-systematic-zh`**,不要在本循环里乱试。 - 若 `prd.md` 缺少可执行的测试定义或自检命令(违反规划期质量门槛),停止并回报,要求先补规划产物,不要硬上。 ## 工作流 ### 1. 载入任务上下文(编辑前必读) 按顺序读取,只读"编辑前必须读"的稳定上下文,控制小模型上下文占用: 1. 子任务 `prd.md`:重点读 `验收标准`、`自动化测试要求`、`参考实现`、`文件清单`、`决策表`、`行为约束`、`自检命令`、`禁止事项`。 2. 若存在 `implement.jsonl`:逐条预加载其中列出的稳定上下文(spec / 契约 / 调研)。 3. 若存在 `design.md`:读`编排-计算分离`与`挂载点清单`两节,确认每个新代码的落点。 4. 若存在 `.trellis/spec/<相关层>`:读与本任务直接相关的规范。
Details
- Skill name
trellis-implement-tdd-zh- Repository
- coldwateryi/trellis-skills
- Path
trellis-implement-tdd-zh/SKILL.md- License
- MIT
- Repo updated
- 3 July 2026
FAQ
What does the Trellis Implement TDD Zh skill do?
在 Trellis 子任务进入实现阶段时,用严格 TDD(红→绿→重构)逐条把验收标准落成代码。用于 Codex / Claude Code 等在 trellis-zero-to-mvp-zh 或 trellis-mvp-to-delivery-zh 生成主子任务后,按依赖顺序实现某个子任务,尤其当执行模型是 qwen3.6 35b 这类小参数本地模型时——把"理解并实现需求"转成"让这条失败测试变绿"的机械循环,每步都有客观信号。
How do I install the Trellis Implement TDD Zh skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add coldwateryi/trellis-skills --skill trellis-implement-tdd-zh. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Trellis Implement TDD Zh popular?
It lives in coldwateryi/trellis-skills, which has 44 GitHub stars and 1 forks.
Related skills
Trellis Debug Systematic
44coldwateryi/trellis-skills
When a test should be green but stays red, or a self-check command fails during Trellis subtask implementation/verification, use this non-deviable rigid script for systematic root-cause pinpointing and minimal fix. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—small models quickly spiral out of control when debugging freely; this skill uses "one change at a time, must re-run after change, no guessing" iron rules to lock it on a narrow path with defensive regression checks.
Trellis Debug Systematic Zh
44coldwateryi/trellis-skills
当 Trellis 子任务实现/验证过程中测试该绿不绿、或自检命令失败时,用一段不可偏离的刚性脚本做系统化根因定位与最小修复。用于 Codex / Claude Code 等驱动 qwen3.6 35b 这类小参数模型调试时——小模型一旦自由发挥就会到处乱改,本技能用"一次只改一处、改完必重跑、禁止猜"的铁律把它锁在窄路径上,并带防御性回归检查。
Trellis Delivery Controller
44coldwateryi/trellis-skills
Trellis requirements-to-delivery entrypoint and workflow controller. Use when the user wants to invoke one Trellis skill that detects the current stage and routes work across requirements analysis, MVP task planning, post-MVP gap audit, delivery loop, TDD implementation, systematic debugging, two-stage review, and final acceptance. Coordinates trellis-zero-to-mvp, trellis-mvp-to-delivery, trellis-implement-tdd, trellis-debug-systematic, and trellis-review-twostage while enforcing safety gates.
Trellis Mvp to Delivery
44coldwateryi/trellis-skills
Audit an existing MVP against a source requirements document and run a sustainable Trellis delivery loop. Use when Codex is asked to continue after an MVP, complete remaining requirements, perform a first full gap audit, maintain a Requirements Traceability Matrix, classify DONE/PARTIAL/MISSING/UNTESTED/UNCLEAR items, initialize or update .trellis/delivery-state.md, choose full/delta/early-exit audit scope, plan bounded gap-closing batches, require worktree + verifier gates, design automated test coverage, classify discovered bugs, or run final acceptance before delivery.
Trellis Implement TDD
44coldwateryi/trellis-skills
Implement a Trellis subtask using strict TDD (RED→GREEN→REFACTOR), turning acceptance criteria into code one by one. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—transforms "understand and implement requirements" into a mechanical "make this failing test green" loop with objective signals at every step.
Engineering Grill
43rohitg00/agentbrain
Use when an engineering plan needs pressure-testing for architecture, complexity, data, risk, and operability.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.