Simple Tdd
Test-driven development methodology — write the failing test first, then the minimum code to pass it
Install
$ agentstack add skill-sylphai-inc-atskills-simple-tdd ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sylphai-inc-atskills-simple-tdd) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Simple TDD Workflow
Follow test-driven development strictly for the task at hand. Do not write implementation code before a failing test exists for it.
Steps
- Understand the requirement. Restate what behavior is being added or fixed, in one or two sentences, before touching any file.
- Write a failing test first.
- Add a test that exercises the new/changed behavior.
- Run the test suite and confirm the new test fails (and fails for the expected reason — a wrong assertion or a crash from unimplemented code, not an unrelated error).
- If it doesn't fail, the test isn't testing anything new — fix the test before proceeding.
- Write the minimum code to make it pass.
- Implement just enough to make the failing test green. Resist the urge to add extra functionality, generalization, or "while I'm here" cleanup at this stage.
- Run the full test suite. All tests — the new one and every existing one — must pass.
- Refactor only when green.
- With all tests passing, look for duplication, unclear naming, or structural issues introduced by the minimal implementation.
- Refactor in small steps, re-running the test suite after each change to confirm nothing broke.
- Do not add new behavior during this step — refactoring changes structure, not behavior.
- Repeat. For the next requirement or edge case, go back to step 2.
Rules
- Never write production code without a failing test that requires it.
- Never write more test code than is sufficient to fail.
- Never write more production code than is sufficient to pass the currently failing test.
- If you find yourself writing several tests before making any of them pass, stop — return to one test at a time.
When to Deviate
For pure exploration/spike work (throwaway prototyping to understand a problem), it's acceptable to skip strict TDD — but say so explicitly, and any code from the spike should be rewritten test-first before it ships.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: SylphAI-Inc
- Source: SylphAI-Inc/atskills
- License: MIT
- Homepage: https://atskills.one
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.