Agent Skill Tdd
TDD + requirements workflow skill for AI coding agents (Claude Code, Codex, Antigravity, Cursor, Windsurf, etc.). Part of the Shelpuk agentic suite alongside Serena, Kindly Web…
Install
git clone https://github.com/Shelpuk-AI-Technology-Consulting/agent-skill-tddInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Improve AI-generated code quality by 20%
TDD Skill is a part of the Shelpuk AI Technology Consulting agentic suite – a set of tools that together improve the code quality produced by AI coding agents by 15–20%. Read more on Claude Code generation quality improvement.
Works with Claude Code, Codex, Antigravity, Cursor, Windsurf, and any agent that supports skills or MCP servers.
| Component | Role |
|---|---|
| tdd ← you are here | Enforces TDD, requirements discipline, and peer review for every coding task |
| Serena | Semantic code navigation + persistent project memory |
| Kindly Web Search | Up-to-date API and package documentation via web search |
| Lad MCP Server | Project-aware AI design and code review |
If you like what we're building, please ⭐ star this repo – it's a huge motivation for us to keep going!
How to use the suite
1. Install three MCP servers and one skill:
2. Use the skill when requesting a feature:
Prompt your favorite AI coding agent (Claude Code, Codex, Cursor, etc.) as usual. Then just add Follow $tdd in the end.
> Build [your feature description]. Follow $tdd.
TDD Skill
Why enforce TDD with a skill?
Picture this: Your AI coding agent just finished a new feature. The code looks clean, the agent is confident – but there's no record of what the feature was supposed to do, the edge cases were never discussed, and when you ask the agent about its design decisions next week, it has no idea what you're referring to. A month later you discover it silently broke an integration that was agreed on in a conversation the agent never saw.
This isn't a bug in the code. It's a bug in the process.
The "No Process" Problem
AI coding agents are stateless by default. Each session starts fresh. Without a structured workflow, even the best models routinely:
- Jump straight to implementation without understanding requirements
- Skip tests or write them after the fact as an afterthought
- Make design decisions without checking current API documentation
- Review their own code and miss "bad token" self-reinforcing mistakes
- Lose all decisions and reasoning the moment the session ends
The result? Technically coherent code that solves the wrong problem – and no paper trail to figure out how you got there.
What This Skill Does Differently
We built this skill at Shelpuk AI Technology Consulting because we needed our AI coding agents to work the way disciplined engineers work: clarify before building, document before coding, test before shipping, and get a second opinion before merging.
✅ Investigate first, code second – agents understand the current state before proposing any changes
✅ Explicit requirements confirmation – no requirement changes without human sign-off, no silent interpretation
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…