sdlc-tdd

Writes feature tests in an integration worktree before implementation within the Agentic SDLC workflow.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-tdd-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-tdd
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-tdd
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-tdd-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often implement features before defining what success looks like, leading to untested acceptance criteria and regressions. This Skill enforces a test-first phase inside the Agentic SDLC workflow by writing tests that prove planned feature behavior before any production code exists. ## Core Features & Use Cases - Test-First Authoring: Maps locked acceptance criteria to unit, integration, component, contract, or regression tests in the registered integration worktree. - Worktree Safety: Re-verifies the integration worktree's Git root, branch, HEAD, and cleanliness before writing, failing with WORKTREE_CONFLICT on drift so the project checkout stays unchanged. - Failure Routing: Classifies blockers and routes back to requirements, design, or plan skills when criteria are untestable or test seams are missing. - Use Case: After a feature plan is locked and execution is prepared, invoke this Skill to create failing tests covering the planned end-to-end slice, record the expected red state, and hand off to implementation. ## Quick Start Ask the Agentic SDLC coordinator to run the TDD phase for the current feature so tests are written in the integration worktree before implementation begins.

Frequently Asked Questions about sdlc-tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write tests before implementation in an agentic workflow?

Use this Skill after the plan is locked and execution is prepared. It maps acceptance criteria to the smallest useful test level, writes failing tests in the integration worktree, runs them, and records the expected red state as evidence.

What is test-driven development in an SDLC pipeline?

TDD in this SDLC pipeline means defining success first: tests proving planned feature behavior are created before any production code. Implementation later seals the TDD base and makes those tests pass, with evidence tracked in run state.

Can I invoke sdlc-tdd standalone outside the coordinator?

No. The Skill requires verified workflow context from the active Agentic SDLC coordinator, including the selected project, active run, and phase. Without that evidence it returns without mutation, and it is hidden from the public command menu in Claude Code.

What happens if acceptance criteria are not testable?

The Skill classifies the failure and routes backward instead of forcing weak tests. Untestable criteria route to requirements authoring, missing test seams route to design, and an untestable planned slice routes to plan or design updates.

Does this Skill modify the main project checkout?

No. All tests are written in the registered integration worktree after re-verifying its Git root, branch, HEAD, and cleanliness. Drift triggers a WORKTREE_CONFLICT failure, and the project checkout must remain clean and unchanged.