skills.rest
TomazWang
TomazWangCOMMUNITY
Explore all skills by this author →
Website𝕏@tomazwangGitHub

block-b-spec-to-tdd

Generate tests, implementation plans, and task artifacts from spec changes.

Updated Feb 5, 2026
Search Tags:#automation#workflow#planning#tdd#generate#tests#spec-changes
One-click install
npx skills add https://github.com/TomazWang/agent-toolkit --skill block-b-spec-to-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: block-b-spec-to-tdd
Source: https://github.com/TomazWang/agent-toolkit/tree/main/plugins/workflow/skills/block-b-spec-to-tdd
Command: npx skills add https://github.com/TomazWang/agent-toolkit --skill block-b-spec-to-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Block B workflow converts spec changes into test cases and implements with a guided TDD cycle, accelerating how teams translate requirements into verifiable tests and code.

Core Features & Use Cases

  • Generate spec-change documents and test scenarios (unit, integration, acceptance)
  • Create a step-by-step implementation plan and TDD guidance
  • Integrate with task/workflow systems to track progress and validation with TDD cycles

Quick Start

Run the Block B workflow to convert a spec change into tests and an implementation plan, then guide the subsequent TDD cycle.

Frequently Asked Questions about block-b-spec-to-tdd

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

FAQPage Schema
How do I convert spec changes into test-driven development plans?▼

To convert spec changes into test-driven plans, this workflow translates structured specification inputs into unit, integration, and acceptance test scenarios while generating a step-by-step implementation plan aligned with a guided TDD cycle.

What is the best way to generate test cases from specification changes?▼

Generating test cases from specification changes involves translating structured spec inputs into comprehensive test scenarios, producing unit, integration, and acceptance tests alongside actionable task artifacts for verifiable code changes.

Can I integrate TDD workflows with existing task tracking systems?▼

Yes, you can integrate TDD workflows with existing task tracking systems. The workflow generates task artifacts and integration hooks designed to track progress and validation directly within standard software development cycles.

Do I need structured spec inputs to start the TDD cycle?▼

Yes, structured spec inputs are required to start the TDD cycle. The workflow relies on these structured inputs to accurately document spec changes and generate corresponding tests and implementation plans.

How does test-driven development handle specification changes without breaking existing tests?▼

Test-driven development handles specification changes by documenting the updates and generating new test scenarios, creating validation steps and implementation plans that align code modifications with the updated TDD cycle.

Related Skills

Explore More Software Engineering Skills→
rickardprickardp
2

blueprint:require

Convert raw requirement descriptions into structured FR or NFR specifications.

Community
Intermediate
jf3096jf3096

test-driven-development

Enforce the Red-Green-Refactor cycle for all code development.

Community
Advanced
mazhewittmazhewitt

openspec-apply-change

Automate OpenSpec change application by coordinating status checks, context loading, and task execution.

Community
Advanced
Agentic-Engineering-AgencyAgentic-Engineering-Agency
3

specsafe-test

Generate unit and integration tests from SpecSafe specifications.

Official
Basic