dev

Automate the TDD workflow by implementing TODO items with tests and requirement IDs.

2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/aleksandrov/instructions --skill dev-aleksandrov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/aleksandrov/instructions/tree/main/.claude/skills/dev
Command: npx skills add https://github.com/aleksandrov/instructions --skill dev-aleksandrov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the full TDD development cycle by automatically selecting the next item from TODO.md, then implementing it with tests, generating requirement IDs, and verifying coverage.

Core Features & Use Cases

  • Automatic identification of the next TODO item from TODO.md and deterministic implementation with tests.
  • Generation and attachment of requirement IDs to code and tests to ensure traceability.
  • Coverage verification to confirm tests exercise the new implementation and report gaps.

Quick Start

Run the full TDD development cycle on the next item from TODO.md.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I automate the TDD cycle for TODO items in my development workflow?

You can automate the TDD cycle by selecting the first TODO item from TODO.md, implementing it with tests, generating requirement IDs, and verifying coverage. This ensures traceability between requirements, code, and tests throughout development.

What is traceability in test-driven development and why does it matter?

Traceability in TDD links requirement IDs to specific tests and code implementations. It ensures every TODO item has verified coverage, making it easier to track which requirements are fulfilled and where gaps exist in the test suite.

How do I run a full TDD workflow from a TODO list automatically?

Run the full TDD workflow by automatically identifying the next TODO item, implementing the code with associated tests, attaching requirement IDs, and validating that the tests exercise the new implementation with deterministic execution.

Can I verify test coverage and requirement traceability for TODO items without manual setup?

Yes, the TDD workflow verifies coverage automatically by confirming tests exercise the new implementation and reporting any gaps. It attaches requirement IDs to code and tests to maintain traceability without manual intervention.

Does TDD automation work without external dependencies for requirement tracking?

The TDD automation operates with no external dependencies, handling requirement tracking internally by generating and attaching requirement IDs directly to code and tests, ensuring deterministic execution of the development cycle.

What's the best way to ensure deterministic execution of the TDD development cycle?

The best way to ensure deterministic TDD execution is to automate item selection from TODO.md and follow a structured workflow of implementation, testing, and coverage verification, reporting gaps and documenting requirements consistently.