tdd-next

Coordinate TDD task orchestration from GitHub issue selection to PR completion.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/shiroinock/nv-atlas --skill tdd-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-next
Source: https://github.com/shiroinock/nv-atlas/tree/main/.claude/skills/tdd-next
Command: npx skills add https://github.com/shiroinock/nv-atlas --skill tdd-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Issues to PR pipeline coordination for implementing TDD-driven tasks, reducing manual handoffs and decision latency.

Core Features & Use Cases

  • End-to-end TDD workflow from issue selection to PR merge, including classification, test scaffolding, implementation, and CI verification.
  • Automated task orchestration across discovery, planning, execution, and validation, with clear guardrails and retry logic.
  • Use case: teams can consistently drive through a TDD cycle from issue intake to ready-for-PR status, ensuring compliant test coverage.

Quick Start

Issue番号を指定して実装パイプラインを起動してください。

Frequently Asked Questions about tdd-next

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

FAQPage Schema
How do I automate a TDD workflow from GitHub issue to pull request?

Automating a TDD workflow from issue to pull request involves coordinating test pattern classification, automated pipeline execution, and local CI tooling integration. This end-to-end orchestration reduces manual handoffs and ensures compliant test coverage before merging.

What is test pattern classification in a TDD pipeline?

Test pattern classification in a TDD pipeline categorizes project tasks using deterministic decision rules to determine scaffolding and execution paths. This classification outcome drives automated pipeline execution and ensures consistent test coverage guardrails.

Can I integrate local CI tooling with an automated TDD task orchestration pipeline?

You can integrate local CI tooling with an automated TDD orchestration pipeline by connecting GitHub and local CI environments. The pipeline coordinates execution and validation phases, applying retry logic and guardrails to verify implementation readiness.

How do I start a TDD cycle using a GitHub issue number?

To start a TDD cycle, specify the GitHub issue number to launch the implementation pipeline. The system orchestrates discovery, planning, execution, and validation to drive the task to a ready-for-PR status with compliant test coverage.

What are the limitations of automating TDD orchestration from issue intake to PR?

A limitation of automating TDD orchestration is its dependency on deterministic decision rules for task classification, which may require manual intervention for complex or ambiguous test patterns outside defined guardrails and retry logic.