tdd
Implement a feature or bug fix test-first when the user asks for red-green development or the change needs a regression seam.
Skill by Rafcin
Chalk Labs
Need help deploying tdd?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/rafcin-tdd
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/tdd
What's inside
- Skill name
tdd- Description
- Implement a feature or bug fix test-first when the user asks for red-green development or the change needs a regression seam.
- License
- MIT
- Instructions
- 21 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Test-Driven Development ## Entry conditions Use for an observable behavior change, regression, or approved behavior seam. Work in small vertical slices through the public seam. Before production code, write one focused test whose expected value comes from the requirement, known-good example, or reproduced bug. Confirm its red result is missing behavior, not a typo, import error, or unrelated baseline failure. ## Scope limit Implement only enough to make that test pass, rerun focused and neighboring tests, and refactor only while green. Do not test private helpers, duplicate implementation logic in expected values, use broad snapshots without a stable contract, or add speculative behavior. A fake belongs only at a genuine external boundary. For a bug, minimize the reported symptom into the regression test. For configuration or generated artifacts, test the observable consumer contract. ## Exit evidence Record red evidence, green evidence, focused and baseline checks, and a clean diff with no behavior beyond the tested requirement. ## Next gate Hand the completed slice to `implement` for its route-level report, then `verification`; use changed-file anti-slop before review when OMCS requires it.
From Rafcin/oh-my-codex-slim, MIT.
More from Rafcin/oh-my-codex-slim
- 0.526score
codemap
Rafcin
Build or refresh a concise repository map when a codebase's modules, entry points, and dependency boundaries must be understood.
SkillBFreshness: BClaude Code +9 - 0.526score
deepwork
Rafcin
Execute an already-approved, multi-step implementation plan with sustained focus, explicit ownership, and continuous verification.
SkillBFreshness: BClaude Code +9 - 0.524score
omcs
Rafcin
Use when a substantial engineering task needs OMCS risk-gated orchestration, including when the user says use OMCS to solve this issue.
SkillBFreshness: BClaude Code +9 - 0.524score
codebase-design
Rafcin
Use when a module boundary, interface, domain model, or architecture change needs a durable design decision before implementation.
SkillBFreshness: BClaude Code +9 - 0.523score
context
Rafcin
Use when a material product or engineering decision remains unclear after repository evidence has been inspected.
SkillBFreshness: BClaude Code +9 - 0.523score
omcs-orchestrate
Rafcin
Use when an existing workflow invokes the legacy OMCS orchestration skill name for a substantial engineering task.
SkillBFreshness: BClaude Code +9 - 0.523score
implement
Rafcin
Use when a bounded implementation task has settled requirements, declared ownership, and a credible behavior seam.
SkillBFreshness: BClaude Code +9 - 0.521score
verification
Rafcin
Prove a completed change against explicit acceptance criteria before claiming completion, release readiness, or runtime success.
SkillBFreshness: BClaude Code +9 - 0.521score
deep-interview
Rafcin
Clarify an underspecified product or engineering request through one focused question at a time before planning or implementation.
SkillBFreshness: BClaude Code +9 - 0.521score
diagnose
Rafcin
Diagnose a reproducible bug or performance regression by building a tight feedback loop and testing ranked hypotheses before proposing a fix.
SkillBFreshness: BClaude Code +9 - 0.521score
plan
Rafcin
Turn settled requirements into an implementation plan with exact files, interfaces, tests, verification, and safe commit boundaries.
SkillBFreshness: BClaude Code +9 - 0.521score
simplify
Rafcin
Reduce accidental complexity in working code when behavior must remain unchanged and the user wants a smaller, clearer implementation.
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 26, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/Rafcin/oh-my-codex-slim
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from Rafcin
- 0.526score
deepwork
Rafcin
Execute an already-approved, multi-step implementation plan with sustained focus, explicit ownership, and continuous verification.
SkillBFreshness: BClaude Code +9 - 0.526score
codemap
Rafcin
Build or refresh a concise repository map when a codebase's modules, entry points, and dependency boundaries must be understood.
SkillBFreshness: BClaude Code +9 - 0.524score
codebase-design
Rafcin
Use when a module boundary, interface, domain model, or architecture change needs a durable design decision before implementation.
SkillBFreshness: BClaude Code +9 - 0.524score
omcs
Rafcin
Use when a substantial engineering task needs OMCS risk-gated orchestration, including when the user says use OMCS to solve this issue.
SkillBFreshness: BClaude Code +9 - 0.523score
implement
Rafcin
Use when a bounded implementation task has settled requirements, declared ownership, and a credible behavior seam.
SkillBFreshness: BClaude Code +9 - 0.523score
context
Rafcin
Use when a material product or engineering decision remains unclear after repository evidence has been inspected.
SkillBFreshness: BClaude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get tdd running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
tdd skill. Agent Mart. https://agentmart.dev/skills/rafcin-tdd (last updated 2026-10-24)