Skip to main content

tdd

Deprecated TDD shim. Keep test-first discipline inside the active implementation workflow (folded into `plan`).

Ir para a instalação

Informações da origem

Repositório
mrzhangguoguo/oh-my-workbuddy
Última atividade na origem
8 de julho de 2026 às 07:14
Idioma detectado do SKILL.md
inglês
Estrelas
2
Forks
1

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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 (`$macro` invocation, `omx` CLI, `.omx/` state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list, `.workbuddy/memory`). # TDD — deprecated 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:** 1. **RED** — Write the next failing test; run it; it MUST fail. If it passes, the test is wrong. 2. **GREEN** — Write only enough code to pass. No extras. Run; it MUST pass. 3. **REFACTOR** — Improve quality; run tests after every change; must stay green. 4. **REPEAT** — Next failing test. **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`.
Ver no GitHub