Implement Feature Tdd

Name: Implement Feature Tdd
Author: uxname

ASecurity

Use this workflow to implement ANY new feature following Test-Driven Development strictly.

30 stars
0 votes
0 copies
2 views
Added June 8, 2026

developmentapi

Works with

Security analysis

A100/100

Scanned June 8, 2026

npx -y skills add uxname/liteend --skill implement-feature-tdd --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement Feature Tdd?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement Feature Tdd

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/uxname-implement-feature-tdd/badge)](https://www.skillsdirectory.com/skills/uxname-implement-feature-tdd)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: implement-feature-tdd
description: Use this workflow to implement ANY new feature following Test-Driven Development strictly.
---

## Workflow Steps

1. **Write failing E2E tests FIRST (RED)**:
   - Write E2E test for API boundaries (Controller/Resolver) using `/add-e2e-test` skill.
   - Run `npm run test:e2e` to verify it FAILS.
2. **Write unit tests (RED)**:
   - Use the `/add-tests` skill to write failing unit tests for the Services and Resolvers/Controllers.
   - Run `npm run test` to verify they FAIL.
3. **Write implementation (GREEN)**:
   - Implement the minimum code required in the Controller/Resolver and Service to make both E2E and unit tests pass.
   - Run tests until they PASS.
4. **Refactor and Check (REFACTOR)**:
   - Run `npm run check` to fix linting and types.
   - Run `npm run test:cov` to ensure test coverage remains above 80%.

Do not write production code before writing the test assertions.